- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi everybody,
I came through a disturbing trick from Memtool.
I noticed that when I was flashing a binary file (generated with ADS and Tasking compiler) to my TC322, Memtool was adding a few bytes (~12) at the starting address defined in my lsl file.
The original binary file has its first data at starting address + 0x20. A memory dump after reflashing shows that there are those additional bytes coming from no where.
I noticed that while developping a bootloader. If I don't add those bytes to my Application bin file, the bootloader won't jump properly to the application.
Does anybody know what those bytes are exactly and if there is something to do (in the lsl file?) to have them properly included at bluid time?
Regards,
Benoit
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning,
I solved my problem, and it was completely due to my mistake.
The hex file generated by the linker had some data in the 0x80000000 address range. When you import the file in Memtool, those data are automatically translated to the 0xA0000000 range.
When I noticed those "missing bytes", I looked for them in the hex file in the 0x80000000 range. I failed to notice a small quantity of data at the end of the file that where in the 0xA0000000 range.
So now my bootloader copies both ranges, and it works just fine.
Thanks for the help.
Regards,
Benoit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi benoit,
Could you please share the .lsl file? Thanks.
dw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning,
I solved my problem, and it was completely due to my mistake.
The hex file generated by the linker had some data in the 0x80000000 address range. When you import the file in Memtool, those data are automatically translated to the 0xA0000000 range.
When I noticed those "missing bytes", I looked for them in the hex file in the 0x80000000 range. I failed to notice a small quantity of data at the end of the file that where in the 0xA0000000 range.
So now my bootloader copies both ranges, and it works just fine.
Thanks for the help.
Regards,
Benoit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
What version of the memtool are you using? I rememeber I had some issue at the beginning of my aurix experience (:-D) because memtool was returning a blocking error if my map was referred to the 0x80000000 address
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm using Memtool 5 v2021.05
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great. You are welcome.