Re: nrf52840_pca10059 startup
Chettimada, Vinayak Kariappa
toggle quoted messageShow quoted text
I may have introduced a regression (bisected to) in 26d22b0075cf5a71f13958ec1f2727ac7167eca4
I notice that hci_usb sample fails to enumerate the bluetooth class device.
Will get back when I have something. Meanwhile, revert the above mentioned commit and do let me know if your application functions as expected.
On 26 Aug 2018, at 19:18, Henrik Brix Andersen <henrik@...
am flashing the board using an Atmel-ICE debugger (using pyOCD 0.11.2) connected to a 10-pin debug connector soldered to the P1 footprint on the bottom of the board.
am using the same configuration for several NRF52832 boards without issues.
On 26 Aug 2018, at 19.01, Cufi, Carles <Carles.Cufi@...> wrote:
Can you tell us how you're flashing the board? Another Nordic Devkit, or a separate debug IC?
Also copying Emanuele who's doing most of the work on this board.
On 26/08/2018, 18:07, "devel@... on behalf of Henrik Brix Andersen" <devel@... on behalf of
I have just acquired an NRF52840 Dongle (nrf52840_pca10059) and I am facing some difficulties with board startup.
When I flash a zephyr binary to the board (e.g. samples/basic/blinky) the board starts up fine and starts the application.
But when I disconnect the board from USB power and reconnect it, the application no longer starts (and the internal DC-DC converter does not seem to start-up either).
If I run no-op pyOCD command (e.g. pyocd-flashtool -t nrf52840) the application springs to life (e.g. for blinky, the LED starts to blink).
I am not using mcuboot or any other bootloader; just the bare-bone sample application.
What am I missing here?
Henrik Brix Andersen
Join email@example.com to automatically receive all group messages.