DA14580
SDK 5.0.3
Basic Development Kit
SmartSnippets v3.9
Hello again Dialog,
Backgound info:
We're bringing up a custom board using a DA14580 with an external EEPROM (M24M02). The EEPROM is used as a boot memory and for data storage. We are using a tag connect jtag programming setup as described in your "User Guide for Programming Reference Designs". The EEPROM firmware for SmartSnippets was updated to accommodate the larger EEPROM and has allowed us successfully erase the entire EEPROM..
***********************
我们遇到困难编程EEPROM via SmartSnippets, especially if the EEPROM has already been previously programmed. I think part of the problem is that we're using extended sleep mode in our program. Am I correct in thinking that extended sleep mode will disconnect the jtag link? If so, is there a way to prevent this?
Right now we have a hacked board where we can disconnect power to the EEPROM and prevent booting from it. Once we're connected in SmartSnippets, we reapply power to the EEPROM to reprogram it. This is very undesirable and while this works for now (sometimes), it's not going to work in the final product. I'm thinking I may be able to launch a program to erase the EEPROM boot area via a BLE command when connected and by so doing prevent booting from the EERPOM and allow reprogramming it. Let me know if you have some better advice to work around this.
Thanks again, Max
Hi Max44,
Yes, you consideration is correct, when the device is in sleep mode the debugger module is shut down and detached from the device, in order to reprogram the EEPROM again you have to issue a reset on the board and hit the connect button in order to catch the device during the start up procedure while it is still awake. What i dont understand is why you need to reprogram the EEPROM in the final product, i mean are you customers going to use Smart Snippets to reprogram the device ?
Thanks MT_dialog
MT,
Thanks for the info on reprogramming.
My device is a development project with the 1st rev of custom hardware. I anticipate lots of firmware changes and different versions that target different applications, as well as my own test and diagnostic routines. I also see changes as development of an Android app proceeds to uncover new requirements.
I certainly wouldn't want an end user reprogramming, but an OTA update is a future possibility.
So far we've been happy with programming EEPROM via SmartSnippets and booting from EEPROM .... other than the sleep disconnect difficulties.
Best Regards, Max