Question: With the ControlCARD,
I cannot download the SCI Flash Kernel to RAM in SCI Boot, what steps should I take
to do so?
Answer:
Check the revision for the
controlCard. Only Revision A has the ability to use the SCI Flash Kernel project
as the SCIRX/SCITX communication lines are properly connected to GPIO28/29 for
SCI Autobaud. Versions below Revision A will not work with the project. For more
details, see the Warnings/Notes/Errata section of [13].
The FTDI Chip interface for the
device by default uses GPIO12/13 for SCI communication. The controlCARD requires
that option 5 of SCI Boot be used in order for it to work on the device.
Next, set the S1 position 1 to ON
on the controlCARD. This allows the emulator to be connected. Set the Boot mode
to SCI by setting S3 Position 1 to 0, and SW1 Position 2 to 1.
After that, make sure that S1
position 2 is also ON. GPIO28 (and pin 76 of the 180-pin controlCARD connector)
will be coupled to the FTDI’s USB-to-Serial adapter. This allows UART
communication to a computer via the FTDI chip.
After this, connect the emulator
via CCS. Launch the target configuration file for the controlCard and connect to
CPU1. Open up a Memory Window (View > Memory Window) and look up the location
0xD00 in memory. In order to use Alternate GPIOs (28, 29) for SCI Boot mode, we
need to set the EMU-BOOTDEF-LOW field (bits 15:0) or Z1-OTP-BOOTDEF-LOW (0x7800C
which is in User configurable DCSM OTP) to 0xA1. Change the following values at
their respective register locations: 0xFFFF at 0xD00, 0x5AFF at 0xD01, 0x00A1 at
0xD04.
If you wish to run CPU2 as well,
connect to it in CCS. Click "Reset CPU", followed by "Resume". The program will
hit ESTOP. Click "Resume" again.
In CCS, for CPU1, click "Reset
CPU", followed by "Resume" (F8).
Now, run the command
serial_flash_programmer.exe with the appropriate command. The kernel will be
downloaded to RAM. When the menu pops up, select the desired operation to
proceed.
Question: With the LaunchPad, I
cannot download the SCI Flash Kernel to RAM in SCI Boot, what steps should I take to
do so?
Answer:
The FTDI Chip interface for the
device by default uses GPIO12/13 for SCI communication. The LaunchPad requires
that option 3 of SCI Boot be used in order for it to work on the device. Within
the device header file for the SCI Flash Kernel project, there is a symbol for
utilizing the LaunchPad (_LAUNCHXL_F28P65X) that must be added to the
list of predefined symbols under project properties. Also within the project
make sure that the boot mode value given to sciGetFunction within the
main source file is set to SCI_BOOT_ALT3. Rebuild the project for the
changes to take place.
Next, set the S2 position 1 to
OFF on the LaunchPad. This allows UART communication to a computer via the FTDI
Chip. Set the Boot mode to SCI by setting S3 Position 1 to 0, and S3 Position 2
to 1.
After this, connect the emulator
via CCS. Launch the target configuration file for the controlCard and connect to
CPU1. Open up a Memory Window (View > Memory Window) and look up the location
0xD00 in memory. In order to use Alternate GPIOs (42, 43) for SCI Boot mode, we
need to set the EMU-BOOTDEF-LOW field (bits 15:0) or Z1-OTP-BOOTDEF-LOW (0x7800C
which is in User configurable DCSM OTP) to 0x61. Change the following values at
their respective register locations: 0xFFFF at 0xD00, 0x5AFF at 0xD01, 0x0061 at
0xD04.
If you wish to run CPU2 as well,
connect to it in CCS. Click "Reset CPU", followed by "Resume". The program will
hit ESTOP. Click "Resume" again. In CCS, for CPU1, click "Reset CPU", followed
by "Resume" (F8).Now, run the command serial_flash_programmer.exe with the
appropriate command. The kernel will be downloaded to RAM. When the menu pops
up, select the desired operation to proceed.