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,
We are using SysConfig editor in Code Composer for our product, however for our device, TMS320F28379D, we can't set the codestart address as we wish under LINKER COMMAND FILE CONFIGURATION section, currently its either 0x080000 ( Boot from Flash ) or 0x000000 (Boot from RAMM).
We would like to build firmware that would have codestart from different flash sectors, e.g. FLASHH, with address 0x0A0000
Currently we achieve this goal by patching the SDK, by editing the file:
C2000Ware_5_01_00_00\utilities\cmd_tool\cmd_syscfg\source\.meta\f2837xd_memoryInfo.js,
We change
codeStartLocations : [
{displayName : "Boot from RAMM", name : "0x000000"},
{displayName : "Boot from Flash", name : "0x080000"},
],
to
codeStartLocations : [
{displayName : "Boot from RAMM", name : "0x000000"},
{displayName : "Boot from FlashA", name : "0x080000"},
{displayName : "Boot from FlashE", name : "0x088000"},
{displayName : "Boot from FlashH", name : "0x0A0000"},
],
Could the option to select more codestart addresses for f2837xd f2837xd be added to future SDK release?
Thanks,
Alvar
Hi Alvar,
I am looking into this now and will provide an update tomorrow.
Kind regards,
Skyler
Hi,
The device only supports those 2 entry points.
Is there a specific reason you want to place that at that specific address.
Regards,
Veena
The table describes, where the ROM-code can jump to, depending on the bootmodes set mainly by pins.
An obvious example, is when you have some kind of bootloader, that will jump to the main SW.
Usually the main purpose of a bootloader is to facilitate update of the main SW, and to boot that SW.
This means that the bootloader will be placed, with an entry point reachable from boot-ROM, usually the "Flash" entry from your table.
It also means that you want to build the bootloader and the main SW, as separate independent projects.
Such a bootloader will not be limited to only "Ram" and "Flash" like the ROM-code. So to build the Main SW the linker needs to be configured to different entry points.
Hi Martin,
The tool was not built for bootloaders and assumes bootROM directly branches to the application. Currently, there are no future plans to update the SysConfig tool to add more addresses. There are many features of a linker cmd file that are not feasible to be included in SysConfig. For the more advanced users, we recommend creating the linker cmd file separately.
Kind regards,
Skyler
The tool was not built for bootloaders and assumes bootROM directly branches to the application
No surprise there. And that is the same reason why we filled a feature request, and not a bug report....
Shall I read this reply as a lazy rejection of feature requests?
Hi Martin,
The feature request has been noted and a corresponding ticket has been created.
Kind regards,
Skyler
Hi Martin,
I am working on creating external tracking information for you. I hope to have it configured early next week.
Kind regards,
Skyler
Hi Martin
I apologize for the delay, our team that manages external ticket tracking is working to provide this information. I will update you with the link once it is live.
Kind regards,
Skyler
Hi Martin,
Here is a link to track the ticket: https://sir.ext.ti.com/jira/browse/EXT_EP-11741
I will be closing the thread now.
Kind regards,
Skyler
That was the solution i was looking for, thankyou. :-)
As I was not the original author, I cannot mark the reply as solution Alvar Udras