Part Number: TUSB9261
Hi Donald,
What errors do you see when trying to compile in version 7.3? How did you decide to use this version? Is it possible to use an older version like one of the V4.X versions?
By chance, are the issues you are seeing similar to issues seen in this E2E thread: https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/589834/ccs-codecomposer-tusb9261---can-t-create-hex-file?tisearch=e2e-sitesearch&keymatch=TUSB9261%2525252525252520AND%2525252525252520Code%2525252525252520Composer#
Thanks,
Ryan
Ryan...thanks for the response. Could I also add our engineer whom has been working directly on this program into this communjication.
His email address is ockert@phence.me. I forward the message below through rregular email so we will be back with our response tomorow.
...Thanks...Don
Hi Donald,
Yes, that should be okay. Since this is a public E2E thread, they should be able to look at and respond to this thread. Please have them create a MyTI account so they can communicate here.
Thanks,
Ryan
Hi Donald,
Our software support is currently limited for this device, I can look into whether I can try to recreate this in CCS.
I did find another E2E thread about getting CCS3.3 running in Windows 11, I would recommend trying these steps if possible: https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1675559/f28377d-sep-ccs-3-3-on-windows-11/6460114?tisearch=e2e-sitesearch&keymatch=Windows%2011%20AND%20CCS#
Thanks,
Ryan
Thanks Ryan, we tried it, still could not get it to run. However, we have the project running successfully on CCS 7.3, and it compiles without errors. So we believe that we are nearly there, probably some small option or setting that we have wrong. We can see that the vector table is missing in the .hex file, so obviously the chip will not work. Is there maybe someone at your side who can just load our project, and look at our settings? Would be greatly appreciated.
Thanks...Don
Hi Don,
I will look into whether there is anything we can do on our side, if you or your team could send what settings you're using for CCS7.3 that may help on my side for trying to replicate.
When you say the vector table is missing in the .hex file, what exactly are you looking for? How does the .hex you are generating compare to say the .hex file provided on TI.com?
Thanks,
Ryan
Thanks Ryan. The .hex file supplied by TI (TUSB926x_FW_v1.06.hex) shows the first page (first 256 bytes) containing vector addresses, and then the assembler instructions starting from address 0100H (256). When looking at our generated .hex file as included in the project we sent you, you can see that the file does not contain any vector addresses in the first 256 bytes, but instead starts at address 256 directly with assembler code.
When you import our project into CCS, it should import our settings as used. You can then view them by right clicking on the project name in the left hand window, and then selecting Properties. There you can see everything, e.g. the compiler we are using, the compile settings, etc..
Regards.
Don
Hi Don,
Understood. I'll give this a look and try to have a response for you by EOD Monday.
Thanks,
Ryan
Hi Ryan,
Just following up, did you maybe have a look at that project of ours?
If you need additional info, we will gladly supply it.
Holding thumbs this side that you spot the problem.
Regards.
Don
Hi Don,
I've been trying to get the properties to show me what compiler your team is using on this project, but so far I haven't been able to get much info:

Your team is using ti-cgt-arm_5.2.9 as the compiler, correct? I see in the link.cmd file the compiler is set for ti-cgt-arm_5.2.5, so it could be that difference is affecting it. Otherwise, I'm still looking to see if I can find anything that could be the issue.
Thanks,
Ryan
Hi Ryan, yes we are using ti-cgt-arm_5.2.9. Not sure why the link.cmd would say 5.2.5, maybe the linker did it for a reason?
Hi Don,
Potentially. I don’t know if it’s possible off the top of my head but if it is, I would recommend either switching to 5.2.5, or updating the .cmd file to switch to the compiler your team is using.
Thanks,
Ryan