Reply by Jefferson Smith●December 13, 20042004-12-13
I get the error "S-records out of range" when I use "-lp"
but the
s-records are not within the range 0x4000..0xffff. "-lp" means
remap
those ranges to corresponding addresses for loading into banked flash
memory.
Sometimes I need to run sreccvt on a file that is already addressed to
banked flash. In this case I don't use -lp but need sreccvt because it
insures an even number of bytes in each s-record.
--- In , "WadeA & RebeccaM Smith" <warm38@j...>
wrote: >
> I was able to successfully wipe out the original bootloader code, but
> it wont let me load another in its place. I get "S-records out of
> range" or "bad hex data". I even used a line of S-record
that comes
> with the source code of the Dbug12 for the D256, just to see if it
> could do it -- same results.
>
> Unless I totally missed it (very possible), I did not find a
> procedure in the docs to load a new bootloader.
>
> We will be getting blank D64 chips and loading bootloader and working
> code, so we need to get this working. Or do we need to get
> something "better" than the TA BDM12SX? (P&E cyclone is a
budget
> killer.)
>
> Suggestions related to this?
>
> wade
Reply by zeta_alpha2002●December 13, 20042004-12-13
>I get "S-records out of
> range" or "bad hex data". I even used a line of S-record
that comes
> with the source code of the Dbug12 for the D256, just to see if it
> could do it -- same results.
It seems that S-record needs to be formatted to bring into the correct
address range. The SrecCVT program can be downloaded from Freescale
website inside the zip file
Where yourfile.s19 is to be converted and out.s19 to be uploaded to
FLASH.
S>Fload or
S>Fload ;b
Fload is linear S2 record
Fload ;b is Bank S2 (formatted), Linear S1
If you did try both then it means the S-record needs to be formatted
by SrecCVT.
Exequiel
--- In , "WadeA & RebeccaM Smith" <warm38@j...>
wrote: >
> I was able to successfully wipe out the original bootloader code, but
> it wont let me load another in its place. I get "S-records out of
> range" or "bad hex data". I even used a line of S-record
that comes
> with the source code of the Dbug12 for the D256, just to see if it
> could do it -- same results.
>
> Unless I totally missed it (very possible), I did not find a
> procedure in the docs to load a new bootloader.
>
> We will be getting blank D64 chips and loading bootloader and working
> code, so we need to get this working. Or do we need to get
> something "better" than the TA BDM12SX? (P&E cyclone is a
budget
> killer.)
>
> Suggestions related to this?
>
> wade
Reply by WadeA & RebeccaM Smith●December 13, 20042004-12-13
I was able to successfully wipe out the original bootloader code, but
it wont let me load another in its place. I get "S-records out of
range" or "bad hex data". I even used a line of S-record that
comes
with the source code of the Dbug12 for the D256, just to see if it
could do it -- same results.
Unless I totally missed it (very possible), I did not find a
procedure in the docs to load a new bootloader.
We will be getting blank D64 chips and loading bootloader and working
code, so we need to get this working. Or do we need to get
something "better" than the TA BDM12SX? (P&E cyclone is a budget
killer.)