This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello!
I am doing my way with Ethernet boot of C6670. I am following steps described for 'simple' example in MCSDK. Makefile there performs following steps:
Source code of bconvert64x utility explains that it performs endian conversion on boot table. I want to ask, can we obtain same result, if specify '-order M' option to hex6x?
And one more question. In produced boot table file there are two initial lines. The first one contains nonprintable character with value of 0x02 (looks like smiling face). Second line looks like
$A0400,
bconvert64xutility does skip these lines. What is their meaning?
Thank you.
It seems to me, that hex conversion utility produces right boot table with -order L option. The first two rows were STX character and address field. I wrote primitive utility to skip those two lines and convert to binary rest of file. It does boot the DSP. It seems to me, that bconvert64x and botpacket utilities were performing double endian conversion. At least in my case I succeeded to produce boot table with hex6x, then literally wrote it as binary and booted to DSP.
I wonder, what I am missing without those two utilities...
Hello,
bconvert64x does the endian conversion.
Bootpacket is not doing any endian conversion. It simply assumes the data is in big endian format already. You can check the source code of bootpakcet.c and there is no endian conversion there.
Regards,
David
Ok, got it.
What I want to know, whether I can make boot table without endian conversion. hex6x utility has an option about output endianness. Is that enough? May I skip bconvert64 step if I use proper output from hex6x? Thanks.