Is it possible for you to post your hex-files here, both application and bootloader, so I can check for any inconsistencies? Related to your previous comment, Stian, here you can find the hex-files Application, Bootloader and, just to check, Bootloader-Settings :.
Site Search User. Attachments 0. Nordic Case Info. Case ID: Einar Thorsrud. Hi, I don't have an explanation at this point, but it seems strange. Is there no activity for all those idle seconds in the initial phase?
Could there be some issue with the UART lines causing unstable communication? Can you make sure to request the HF clock so that we know that the issue is not caused by an inaccurate clock in the nRF the high-frequency RC oscillator has a too high tolerance for UART, so it could cause communication problems if you are unlucky.
There is no UART activity during the first 35 seconds. Looking at the UART signals with a scope, they look fine. If your app requires the softdevice but you haven't flashed the softdevice you won't be able to run the app.
You need to flash the softdevice when you flash the bootloader. The app is what is generated as an output hex file from Segger IDE. It is my understanding that the hex file does not have the softdevice merged with the Blinky app. So, from my understanding the softdevice is not merged with my app.
Hi Peter, I'm sorry for late reply I was on vacation last week. If you have the bootloader in your flash, it's not possible to use Segger IDE to flash your application directly to the chip. State Not Answered Replies 8 replies Subscribers 26 subscribers Views views Users 0 members are here development software nrf52 nrf s dfu. Attachments 0. Nordic Case Info. Case ID: Share More Cancel. Marta L. All help is welcome Thanks in advance, Marta.
Reply Cancel Cancel. Hung Bui. Nordic Case Info. Case ID: Share More Cancel. SDK
0コメント