Production Programmer

Chris Maxwell83026

Other Parts Discussed in Thread: TMS320F28035, UNIFLASH

Hi all,

Can anybody recommend a USB controlled production programmer that can take a .out file and program it onto a TMS320F28035?

We have JTAG connections suitable for a Blackhawk USB2000 emulator. We currently program through that; but that requires Code Composer. The boards will be programmed at the contract manufacturer who doesn't currently have Code Composer.

If I'm missing something really obvious here...as in...Blackhawk already provides a way to program a .out file without Code Composer, I apologize in advance.

Thanks

over 14 years ago

0 Kris Parrent over 14 years ago

TI__Genius 15260 points

Chris,

I think this is the same answer you were looking for in the other post of your I just answered (using Debug Server Scripting)

http://processors.wiki.ti.com/index.php/Debug_Server_Scripting

Let's choose one thread and use it for both questions since I believe they are very similar. If I'm misunderstanding please let me know.

Kris

0 Chris Maxwell83026 over 14 years ago in reply to Kris Parrent

Prodigy 190 points

Yes, same question. I reposted because my internet firewall had a hiccup after the first post and didn't give me a verify. So, I reposted. Then I got the email confirmation later.

I'm looking more for a hardware solution....i.e. a self contained black box...but that may not be possible.

If the solution requires CCS, then we'll have to provide it to our contract manufacturer, which really isn't a big deal cost-wise. It just seems a waste of a programming/debug environment to just put the .out file on the chip.

0 Kris Parrent over 14 years ago in reply to Chris Maxwell83026

TI__Genius 15260 points

I'm not aware of any other solutions, but that isn't to say they don't exist. This is definitely the easiest as it uses your target configurations and GEL files and everything that you have already setup in CCS. This makes getting through any device security you have configured much simpler (and less visible to whoever may be programming it). It basically goes through everything you do in the debug environment from a scripting standpoint, so once you have the program working in CCS, you know it will be loaded the exact same way.