- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software:
Hi
I am facing some issue using CCS for TMS570LS0914 IC(we are use customize bootloader). I have generated(using TI Compiler) bin and hex file with 0x00020000 address of Vector and Flash in .cmd file.(I use this file as application file). When hex file is flash through our proprietary tool then its stuck somewhere but when we use BIN file of same code(generated same time) which is converted into hex using HEXVIEW tool and flash through our proprietary tool. Its working fine.
I have to check another possibility also - If i generated hex file with address 0x00020000 in .cmd file. and flash hex file through UNIFLASH tool its also working fine.
If we assume its application code issue but HEX file generated through HEXVIEW tool its working so I couldn't understand its setting issue in CCS or any other .
Please assist in this issues.
Hi Rahul,
I am suspecting this:
The bin file doesn't have addresses information, it just consists of the data.
For example refer below picture, here i am generating output files with 0x20020 address, and when i viewed .bin file in HexView then it is showing like the data is start at 0x00000000
Even if i try to program this .bin file through UniFlash also, we should mention the start address for the binary manually.
And on other hand, hex file consists of the address information also in the file:
For example see the .hex for same code:
The first two rows indicating that the data is starting at 0x20020 in intel hex format.
So, hex file doesn't require any address to mention in the UniFlash as well:
Based on above information, when you programmed hex directly then it didn't work because the application is at some other address like 0x20020 in my case. So here bootloader should be present, and bootloader should call the application properly then only it will work, maybe it is missing here.
However, you said it worked when you converted binary into hex, because in this case the starting address of the application might be 0x00000000, so maybe it overwritten the bootloader and now the application might directly call after reset, that might be the reason for working here.
Think in this point of view once.
--
Thanks & regards,
Jagadish.
Hi sir
I have check following possibility
I have use Customize bootloader which address at 0x0000000 and application address at 0x00020000
Generated BIN and Hex file at address 0x00020000
I have to check following possibility Scenarios.
1. When i have convert bin file into hex file using HEXVIEW (In this process i am adding start address 0x00020000) and flash through bootloader - It's working fine
2. When i have direct generated hex file through CCS (address at 0x00020000) and flash through bootloader - It's not working (Main issue)
In both cases all setting of CCS compiler are same. ( Bin and hex file generated at same time. Using HEXVIEW we add address 0x00020000 and generated hex file)
3. When i have direct generated hex file through CCS (address at 0x00000000) with same compiler setting and Flash through UNIFLASH - It's working fine.
So, 2nd Scenario Not working,
I was comparing both HEX file of 1st and 2nd scenario from line 8873 data getting different.
HEXView Generated HEX file data Direct Generated HEX file data
Can you give me solution?
Hi Rahul,
Can you try one thing,
Can you take a new line at 8874 line of direct generated hex file:
And include the following line:
:045464000000000044
I am suggesting this because both hex files almost same except that in direct generated hex file the 4 locations from 5464 address is not filling with all zeros but this is happening in the converted file.
If you include the above suggested line, then this might make both hex files same and will see what happen in the execution.
--
Thanks & regards,
Jagadish.
