Delta Tau TURBO UMAC 사용자 설명서
UMAC Turbo CPU/Communications Board Hardware Manual
Upgrading Communications Firmware
30
UPGRADING COMMUNICATIONS FIRMWARE
The UMAC Turbo CPU/Communications Board can have its communications firmware upgraded via its
USB port. This is useful for getting the latest firmware to take advantage of bug fixes and new features.
USB port. This is useful for getting the latest firmware to take advantage of bug fixes and new features.
Upgrading Ethernet or USB Firmware
Caution:
Do not stop the firmware upgrade in the middle of its loading. Do not load application
firmware into the boot loader. Do not load boot loader firmware in the application
firmware. Doing any of these will result in the customer having to return the card to the
factory for repair.
firmware into the boot loader. Do not load boot loader firmware in the application
firmware. Doing any of these will result in the customer having to return the card to the
factory for repair.
Upgrading the application firmware can be done with the Store F/W button in the same fashion as the
boot loader firmware. Probably at some time, this firmware will need an upgrade. This firmware
contains all of the code that performs USB and Ethernet communications. To upgrade the firmware, click
the Store F/W button. An Open File dialog box displays. Select the version of firmware that will be
loaded into the UMAC Turbo CPU/Communications Board.
boot loader firmware. Probably at some time, this firmware will need an upgrade. This firmware
contains all of the code that performs USB and Ethernet communications. To upgrade the firmware, click
the Store F/W button. An Open File dialog box displays. Select the version of firmware that will be
loaded into the UMAC Turbo CPU/Communications Board.
UMAC-Turbo Memory Mapping
When using the UMAC Turbo CPU/Communications Board, all of the BUS communication functions are
available. In addition, there are a couple of DPRAM commands available. Using either PTALK DT or
PCOMM 32, a program can be written to interface to the UMAC through the following functions:
available. In addition, there are a couple of DPRAM commands available. Using either PTALK DT or
PCOMM 32, a program can be written to interface to the UMAC through the following functions:
PVOID CALLBACK PmacDPRGetMem(DWORD dwDevice,DWORD offset,
size_t count,PVOID val )
PVOID CALLBACK PmacDPRSetMem( DWORD dwDevice, DWORD offset, size_t count,
PVOID val )
size_t count,PVOID val )
PVOID CALLBACK PmacDPRSetMem( DWORD dwDevice, DWORD offset, size_t count,
PVOID val )
Using the USB DPRAM
The UMAC Turbo CPU/Communications Board can write to any DPRAM memory location. Use M-
Variables that point to an area in the $60000 - $60FFF address range. However, unpredictable
results will occur if writing to the areas that used for the DPRAM automatic reporting features (i.e., the
ASCII communications buffer ranging from $603A7-$60410). The automatic reporting features memory
area can be determined from the Turbo Software Reference Manual by examining the address in the
$60000 - $60FFF; however, when using UMAC Turbo CPU/Communications Board, this range is
from $60000 - $60FFF. Start variables at the $60D60; this address is well outside the range of the
automatic reporting features. Below is an example of pointing to a series of DPRAM locations on the
USB card and the count:
Variables that point to an area in the $60000 - $60FFF address range. However, unpredictable
results will occur if writing to the areas that used for the DPRAM automatic reporting features (i.e., the
ASCII communications buffer ranging from $603A7-$60410). The automatic reporting features memory
area can be determined from the Turbo Software Reference Manual by examining the address in the
$60000 - $60FFF; however, when using UMAC Turbo CPU/Communications Board, this range is
from $60000 - $60FFF. Start variables at the $60D60; this address is well outside the range of the
automatic reporting features. Below is an example of pointing to a series of DPRAM locations on the
USB card and the count:
M1000->DP:$60D60
PmacDprGetMem(0,0x3580,4,&dwData)
M1001->Y:$60D61
PmacDprGetMem(0,0x3584,2,&wData1)
M1002->X:$60D61
PmacDprGetMem(0,0x3586,2,&wData2)
M1003->F:$60D62
PmacDprGetMem(0,0x3586,4,&fData)
The parameters passed to the PmacDPRGetMem function are:
The device number for the case of multiple devices
The DPRAM offset
The number of bytes to retrieve
The location to place the retrieved bytes