Is it reasonable to use only JTAG/SWD for development and production? | Dialog Semiconductor customer support

5 posts / 0 new

Last post

Thu, 2018-06-14 21:42

jfolsom

Offline

Last seen:2 years 1 month ago

加入:2014-11-03 18:47

Is it reasonable to use only JTAG/SWD for development and production?

I am designing a custom PCB with a DA14580 and another ARM microcontroller which drives the entire system. I've been looking at many solutions for programming, debugging, production testing, etc. I am confused by all the options!

我看到总体发展模式扫描rnal SPI/UART/I2C devices, then downloads code from one of these devices into RAM, then runs the code. If no external devices are present, it switches into JTAG/SWD mode.

1. Once it is in SWD mode, can I then connect with an SWD header, push code to the device's RAM, and then debug that way?
2. Is there anything I lose by using SWD instead of, for example, SPI?

Then, when ready for production, it looks like I can use SmartSnippets to program the OTP via SWD.

3. Is this true? (can I program OTP via SWD?)

I would write my own test/programming routine (which would use SmartSnippets CLI) and include it along with other unrelated system test routines.

4. Can I do this, or is it required to use prodtest.exe (discussed in AN-B-020) or equivalent?
5. Can I skip the XTAL Trimming step if I choose high-tolerance (10ppm) crystals?

Finally, say that everything I'm suggesting here is possible:

6. Does this mean that I don't need to break out any UART pins, at all?

Thank you for your time.

Keywords:

JTAG SWD programming production

Device:

DA14580

Fri, 2018-06-15 16:04

MT_dialog

Offline

Last seen:1 month 2 weeks ago

加入:2015-06-08 11:34

Hi jfolsom,

Yes, this is how you can debug the code, Keil is using the SWD in order to download code into the sysram.
I am not sure i get the question, which interface you are going to use it depends on your implementation, if you would like to debug the code on the 580 the SWD is the only option, if you would like to boot an image from an external device then the SPI is an option but the SWD is not.
Yes, you can program the OTP either via SWD or via UART.
It depends on what you would like to do, the prod_test.exe has also a CLI interface and is for testing the device while the CLI of Smart Snippets is for burning the code in the device or in the flash or eeprom, OTP etc.
It is recommended to trim the XTALs that you are about to use on the PCB that you about to use it, since the tollerance of the XTAL is affected by the capacitance of the board. Theoretically the trimming itself might be skipped but there should be a a proper default trim value that should be applied in order to be in the 10ppm range.
I dont quite get the question, do you mean if you dont have to use the UART interface at all, the production test is using UART as an interface, so if you plan to run tests from the production test fw you are going to need UART access to the UART pins of the production test fw.

Thanks MT_dialog

Fri, 2018-06-15 17:53

(Reply to #2) #3

jfolsom

Offline

Last seen:2 years 1 month ago

加入:2014-11-03 18:47

Thank you MT_dialog, I've

Thank you MT_dialog, I've learned a lot from your posts, both here and elsewhere :)

I hope to use SWD for both debugging and then programming the OTP. So it sounds like I don't need the UART interface except for the production tests via prod_test.exe.

Can prod_test.exe use any interface other than the UART?

Thank you,
Jon

Mon, 2018-06-18 16:09

(Reply to #3) #4

MT_dialog

Offline

Last seen:1 month 2 weeks ago

加入:2015-06-08 11:34

Hi jfolsom,

No, the production test tool is using only the UART interface, no other interface is available. If you found the above post helpfull, please mark it as accepted.

Thanks MT_dialog

Mon, 2018-06-18 19:02

jfolsom

Offline

Last seen:2 years 1 month ago

加入:2014-11-03 18:47

Thanks again :)