TMS320F28035: TMS320F28035 Firmware compatibility with TMS320F28034

Hello Madhu,

It is always best practice to update your project to specifically target the F28034. My feedback is below:

1. Yes, you can use the same code since you are not using CLA. F28034 is a variant of the F28035- these devices are designed to be pin-compatible and share the same core features except for the CLA. Still, it is highly recommended to rebuild the project for F28034. 

2. The F28034 and F28035 memory maps are the same (excluding CLA). However, it's still recommended to use the correct device selection in Uniflash. Please allow another day for me confirm this as well.

Best Regards,

Allison

Hello Allison,

Thanks for responding.

The current firmware is already in production and actively running in the field. Given this, we do not want to maintain separate firmware versions for different Controllers as there will be SW updates.

could you please advise on the levels of testing that should be performed to confirm that the new controller is functioning correctly and without issues?

Please find below the relevant snippet of CLA usage found in the existing project.

Thanks & regards,

Madhu P

Hi Madhu,

Please note that although this should work since the memory map is the same, best practice would still be to use the correct device configuration. 

The biggest concern is a reference to the CLA registers or an attempt to allocate code/data to the CLA memory. You need to ensure there is no use of CLA symbols in your code, and the linker cmd file should not have CLA regions as these don't exist on F28034. 

In regards to testing, any functional testing would be application specific and hence up to you to decide. There are general checks you can do (e.g. check that the device boots normally, check if there are any unexpected illegal ISR traps/NMI/resets, test peripheral functionality, etc. Much of which can be done with something as simple as toggling a GPIO in your program or running a PWM and scoping to ensure the waveform is expected, or sending a communication out at key points). 

Best Regards,

Allison

Hello Allison,

Thank you for your inputs.

In the snippet I shared regarding the usage of the CLA, it is neither defined nor configured, even in the .cmd file. However, after flashing and testing it on the $28034$ controller, it is working fine.

For the upcoming production, we can plan to use the $28034$-configured project hex file. However, for the field units that are currently running with the $28035$ controller, the software update will be performed using the $28034$ compiled file. I hope this approach will not create any issues.

Regards,

Madhu P

Hi Madhu,

Please allow another day for me to compile my response. Appreciate your patience.

Best Regards,

Allison

Hi Madhu, 

Just replying to confirm what I mentioned before - there is no issue as long as you are not using anything the F28034 doesn't have (e.g. CLA). The only other input that came up was that Uniflash may do a check for the device number, but I will let a uniflash expert comment on this. 

Best Regards,

Allison

Hi Madhu,

UniFlash should be able to handle the compile for F28034 devices on F28035 devices as well.

Thanks and regards,

Charles

Hi Madhu,

Marking this thread as resolved since it's been some time.

Thanks and regards,

Charles