Hi,

I have a problem concerning the c5509 bootloader.
I try to boot from a 24bit addressed SPI Flash
and I´ve already written a programm that writes the data
to be run into the flash.
When i have a look at the SPI-Signals after the DSP comes
out of reset i can see that the data, the dsp reads, is correct.

My question now is, how to compile the rigth data for booting.
I took the .out file, Code Composer built, und converted it
by using hex55

hex55.exe -boot -v5510:2 -serial8 -reg_config 0x1c00,0x2180 -delay 0x100 -a -o fileout.io
filein.out

Is that rigth oder did i understand something wrong?

Thanks for your help,

Christoph

Christoph-

> I have a problem concerning the c5509 bootloader.
> I try to boot from a 24bit addressed SPI Flash
> and I´ve already written a programm that writes the data
> to be run into the flash.
> When i have a look at the SPI-Signals after the DSP comes
> out of reset i can see that the data, the dsp reads, is correct.
>
> My question now is, how to compile the rigth data for booting.
> I took the .out file, Code Composer built, und converted it
> by using hex55
>
> hex55.exe -boot -v5510:2 -serial8 -reg_config 0x1c00,0x2180 -delay 0x100 -a -o fileout.io
filein.out
>
> Is that rigth oder did i understand something wrong?

It seems like it could be Ok, but I don't see the "entry point" parameter.  Where do
you want the bootloader to jump
to after code is loaded?  The bootloader doesn't have access to symbol information, so it
doesn't know where _c_int00
(or other) address is located in your code.

-Jeff

On page 13-30 spru280u, it states "execution starts at the default entry point
specified by the linker and contained in the COFF file". I might want to think -e isn't
necessary if you boot from _c_int00.

I don't see the format option such as -m2 in your hex55 command. I think that's important.

Hi,
>
>I have a problem concerning the c5509 bootloader.
>I try to boot from a 24bit addressed SPI Flash
>and I�ve already written a programm that writes the data
>to be run into the flash.
>When i have a look at the SPI-Signals after the DSP comes
>out of reset i can see that the data, the dsp reads, is correct.
>
>My question now is, how to compile the rigth data for booting.
>I took the .out file, Code Composer built, und converted it
>by using hex55
>
>hex55.exe -boot -v5510:2 -serial8 -reg_config 0x1c00,0x2180 -delay 0x100 -a -o fileout.io
filein.out
>
>Is that rigth oder did i understand something wrong?
>
>Thanks for your help,
>
>Christoph

Li Wei-

> On page 13-30 spru280u, it states "execution starts at the default entry
> point specified by the linker and contained in the COFF file". I might want
> to think -e isn't necessary if you boot from _c_int00.

Probably that's Ok.

> I don't see the format option such as -m2 in your hex55 command. I think
> that's important.

-x (Tektronix format) is the default.  One advantage to Tektronix format is that it
handles extended addressing.  TI-tagged format is limited to 16-bit.  I'm not sure
what bit-width the Motorola formats (including -m2) handle for addressing.

My suggestion would be to stick with -x (or default, no entry).

-Jeff

> >I have a problem concerning the c5509 bootloader.
> >I try to boot from a 24bit addressed SPI Flash
> >and I�ve already written a programm that writes the data
> >to be run into the flash.
> >When i have a look at the SPI-Signals after the DSP comes
> >out of reset i can see that the data, the dsp reads, is correct.
> >
> >My question now is, how to compile the rigth data for booting.
> >I took the .out file, Code Composer built, und converted it
> >by using hex55
> >
> >hex55.exe -boot -v5510:2 -serial8 -reg_config 0x1c00,0x2180 -delay 0x100 -a -o
fileout.io filein.out
> >
> >Is that rigth oder did i understand something wrong?
> >
> >Thanks for your help,
> >
> >Christoph