Oups!
Sorry for not having read all the words.
In production this is mainly defined by your existing
production methods.
Some methods :
a) Mass production system usually use JTAG based test bench that test the
board on the factory line and use this to flash the system using a JTAG
compliant flash.
a') If you do not want to use JTAG compliant flash, you can still use JTAG
to download a flasher to the ARM. But this requires to contact TI to
have DaVinci JTAG specs so the test bench can be programmed.
b) Have the flash preprogrammed before board population, at least
not with the final software but with Uboot or another customer
software to flash the final boot/kernel/filesystem
c) use the serial boot mode to download a flasher, then finalize flashing
through serial or ethernet
d) CCS + JTAG
Hope this helps,
Regards,
Jean-Michel.
----- Original Message -----
From: "Lloyd Sargent" <[EMAIL PROTECTED]>
To: <[email protected]>; "Jean-Michel Mercier"
<[EMAIL PROTECTED]>
Cc: "Heath Holcomb" <[EMAIL PROTECTED]>
Sent: Wednesday, December 13, 2006 4:59 PM
Subject: Re: JTAG Programing
Actually, I think his question was more for PRODUCTION not development as
we
are a small company.
Cheers,
Lloyd
On Wednesday 13 December 2006 03:19, Jean-Michel Mercier wrote:
So IMHO if you want to do serious DSP coding, you should get for CCS
and a JTAG probe. That's the best way to do unitary tests on DSP-side
and also integration debug.
I know the following probes to work on DaVinci:
- SpectrumDigital XDS510 USB
- BlackHawk XDS560 USB (both separate power and bus-powered versions)
- TI XDS560 PCI
This does not mean that other probes do not work. This is just
my personnal experience. Others list readers may add to the
list.
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
