Hello,
I tried to get the DA14531 module in hibernation with theda14531_configuring_da14531_hibernation_modeexample code. This example was not working properly, because I measured a current consumption of 10uA, both on the power profiler and a multimeter. After trying to flash a different example, I couldn't get the module to connect on the pro devkit. I've had similar problems before, but when I flashed the module via UART it worked fine again. Now, the module isn't responding to SWD, 1-wire UART, 2-wire UART, and SPI.
Is there a way to recover the module from its hibernation?
Thanks,
Martin
Keywords:
Device:
Hi innovativepower,
Thanks for your question and for your interest in our DA14531 Module BLE solution.
Please let me check it in detailed and I’ll get back to you as soon as possible.
Thanks, PM_Dialog
Hi Martin,
Apologies for my delay response. Can I ask what is the SDK version that you are using?
Please try to boot with a different from 1-wire UART on P05 which a prior step than booting from the external SPI Slave in the booting sequence. Please see section 6 Booting from 1-wire UART from the following application note.
//www.wsdof.com/sites/default/files/an-b-072-da14531_booting_options_v1.4.pdf
Once the device booted, then try to connect to the SPI flash and erase it.
Thanks, PM_Dialog
Hi,
我试着引导从机的UART,但module is not responding to a reset.
I'm using SDK 6.0.14.1114
Thanks,
Martin
Hi Martin,
Could you please indicate if you are using the Pro-DK or a custom board? In case of Pro-DKm please check if you are using the correct jumper configuration. See 5.9.1 Single wire UART, JTAG, RESET inUM-B-141: DA14531 SMARTBOND TINY™ MODULE Development Kit Pro Hardware User Manual.
Thanks, PM_Dialog
Hi,
I'm using the Pro-DK and I followed the instructions in the manual with the correct jumper settings.
Thanks,
Martin
Hi Martin,
I am able to boot form 1-wire UART in my side. Can you please check if the P0_5, P0_5, 115200 Bd is selected in the Board Setup?
Please see Figure 20 Single UART communication.
http://lpccs-docs.dialog-semiconductor.com/UM-B-083/tools/Board_Setup.html
Thanks, PM_Dialog
Hi,
Yes, P05 is selected and it still doesn't connect. The problem seems to be that the module is not resetting, with the button on the mother board as well as the button on the daughter board.
Thanks,
Martin
Hi Martin,
Can you please send a log file from the SmartSnippets Toolbox? Additionally can you please probe the P00? A high signal on P00 will generate a reset.
Thanks, PM_Dialog
Hi,
I tried probing the pin with a logic analyser, and P00 stays low all the time. On P05 a message is sent prior to resetting the module: {0x00, 0x01, 0x49, 0x66, 0x2D, 0x3D, 0xC0}. The voltage on P00 is about 40mV when pressing the button, so it may be held low by a GPIO pin? When I forced the pin high for a very short time, it didn't have any effect.
This is the log file when attempting to flash:
Thanks,
Martin
Hi Martin,
Please probe the P05 using a logic analyzer. Once the reset button is pressed and the chip reboots, you should see the 0x02 on the P05. Can you verify this one?
Thanks, PM_Dialog
Hi,
When I tried to capture the sequence with a logic analyser, I accidentally discovered a fix. When the chip booted, there was no way of resetting it, because the chip held the reset pin low. Forcing the reset pin high did not help.
I accidentally left the logic analyser running while power cycling the pro dk(re-plugging the USB). On the log I saw P00(reset) going high and P05 responded with the 0x02 you mentioned. So, the module does respond to a reset prior to booting.
I was able to flash the board again by power cycling the module while trying to connect to it via the smartsnippet toolbox. This can be done by unplugging the daughter board from the main board, and then plugging it back in when the log asks you to reset the module. Then the reset is detected, because the module hasn't booted yet, after which I flashed the module.
Thanks for your time,
Martin
Hi Martin,
高兴你找到你的问题。如果你有any follow-up question, please raise a new forum post.
Thanks, PM_Dialog