Hi,

I am trying to get UART serial boot to work on a C5502, I have set the DSP GPIO for Uart boot
and see GPIO4 go high then low as expected, I send my bootloader at the required baud rate and
get an exact match echoed back but then nothing happens. 

If I look at DARAM in code composer after loading it doesn't look right and I have tried
various Hex55 combinations without any luck.

Some Hex55 config attempts

"b.out" -v5510:2 -serial8 -b -boot -map b.map  -e _c_int00 -memwidth 8 -romwidth 16
-o b.bin

and 

"b.out" -v5510:2 -serial8 -a -boot -e 5bd3h -memwidth 16 -romwidth 16 -o b.asc

my map file has 
 BOOT LOADER PARAMETERS
   Table Type:		  SERIAL PORT (McBSP 8 bit Mode)
   Entry Point:		  0x00005bd3  (_c_int00)

Does anybody have any suggestions? Many thanks in advance.

Craig-

> I am trying to get UART serial boot to work on a C5502, I have set the
> DSP GPIO for Uart boot and see GPIO4 go high then low as expected, I
> send my bootloader at the required baud rate and get an exact match
> echoed back but then nothing happens.
> 
> If I look at DARAM in code composer after loading it doesn't look
> right and I have tried various Hex55 combinations without any luck.
> 
> Some Hex55 config attempts
> 
> "b.out" -v5510:2 -serial8 -b -boot -map b.map  -e _c_int00
> -memwidth 8 -romwidth 16 -o b.bin
> 
> and
> 
> "b.out" -v5510:2 -serial8 -a -boot -e 5bd3h -memwidth 16 -romwidth
> 16 -o b.asc
> 
> my map file has
>  BOOT LOADER PARAMETERS
>    Table Type:            SERIAL PORT (McBSP 8 bit Mode)
>    Entry Point:           0x00005bd3  (_c_int00)
> 
> Does anybody have any suggestions? Many thanks in advance.

Suggest to modify your resulting hex file so the first few data values are some
recognizable pattern (e.g. 0x1234, 0x55aa, etc) then watch what's happening with a
dig scope.  The first step is to verify valid data into the McBSP.

Another suggestion is to locate the 5502 bootloader document, which includes code the
bootloader runs, so you can see how values are interpreted and what the bootloader
expects, especially the first few values.  You might even be able to single-step that
code with JTAG emulator, which combined with the scope would highlight the problem in
about 30 min.

-Jeff