Dear Sirs.
我有三个问题。
Q1. Which is better to use UART or J-Link for writing OTP memory?
Is there a document which I can see the advantages and the disadvantages of both?
（If there is no difference, I may use UART.)
Q2. The document mentioned that writing OTP must use "CLI of Smart Snippets".
According to the document, "OTPheader hex file" includes BD_ADDR and unique ID.
Required for mass production, I want to standardize hex flie, just change BD_ADDR and uniqueID.
Is there any way to do that?
Q3. The document mentioned that writing OTP must use "CLI of Smart Snippets".
but I worry about producing module speed.
Is there any method which is faster than "CLI of Smart Snippets"?
Best Regards.
Device:
Hi Coral0310,
1. I am not aware if there is any tradeoff between choosing to program you board using the UART or the Jtag interface, therefore there is no document that analyses the drawbacks of the two interfaces. Perhaps the JTAG interface would give you a more stable and fast connection since it has a faster clock source than UART when using Smart Snippets.
2. I dont understand the question, to which document are you refering to and what do you mean you want to standarize the .hex file? You want to burn a different bd_address/unique_id on each device and you would like the .hex which will be burned to the OTP to be generated automatically ? In case this is your question the PLT tool has this capability of automatically generate and burn bd_addresses but at the current software only the bd_addresses/Device unique ID field (the device unique id field is used as the db_address of the device).
3. Currently the only available ways of burning the OTP would be through the CLI and Smart Snippets only, if you use the PLT tool then there a seperate software for burning 16 DUT's in parallel.
Perhaps you would like to have a look at the PLT tool if you have concerns about the production time, please check the production line tool in the reference design section.
Thanks MT_dialog