|
We are trying to get a bootload system up running for the vc5402. The source code is entered using the serial port 0. The length of the data is 16 bit. We are using the hex500 utility. We are using the S2 setting. We have received a copy of the bootloader code from Texas. The problem is that the file content generated by the hex500 does not seem to match what the bootload source code from Texas expect. When only using the "-a" file type (ASCII), the first bytes are: 02 0D 0A 3030 20 3830 20 3030 20 3635 20 4630 20 ... The first three bytes we don't know what are used for. The next words are really 0080 which is the start address for our code. The next 0065 we don't know what are used for and the next bytes seems to reflect the code at address 0080 and below. The Texas code seems to require a 10AAh for the first word. We are not able to get this when we use hex500. What is wrong? regards, Torgeir Jakobsen |
|
|
Major confusion trying to bootload vc5402
Started by ●October 29, 1999
Reply by ●October 29, 19991999-10-29
|
This problem is caused by a lacking processor option in the code composer project setup. The Assembler and C-compiler should use the v548 option as processor type. This is done in the code composer Build Options Compiler Code Gen (II) page. (You should use "548" since code composer adds the "v" to the compiler option). The 0065 is the segment length. ====================================== Helge Minken http://login.eunet.no/~helgemi ----- Original Message ----- From: <> To: <> Sent: 29. oktober 1999 16:04 Subject: [c54x] Major confusion trying to bootload vc5402 > We are trying to get a bootload system up running for the vc5402. The > source code is entered using the serial port 0. The length of the data > is 16 bit. > > We are using the hex500 utility. We are using the S2 setting. We have > received a copy of the bootloader code from Texas. The problem is that > the file content generated by the hex500 does not seem to match what > the bootload source code from Texas expect. > > When only using the "-a" file type (ASCII), the first bytes are: > > 02 0D 0A 3030 20 3830 20 3030 20 3635 20 4630 20 ... > > The first three bytes we don't know what are used for. The next words > are really 0080 which is the start address for our code. The next 0065 > we don't know what are used for and the next bytes seems to reflect the > code at address 0080 and below. > > The Texas code seems to require a 10AAh for the first word. We are not > able to get this when we use hex500. What is wrong? > > regards, > Torgeir Jakobsen > > > > |
