Nordic PCA10059 support without additional Segger debugger

[larsgk]

A collection of pull requests (and issues) related to PCA10059 (Dongle) suport:

• Add add nrf52840_pca10059 board support ( boards: arm: add nrf52840_pca10059 #8812 )
• drivers: usb: nrfx: fixes for USB dfu pawelzadrozniak/zephyr#1 to be merged to drivers: usb: Add nRF52840 USBD driver #8787 .
• DNM Add nRF52840 USBD driver ( drivers: usb: Add nRF52840 USBD driver #8787 )
• MCUboot Erase flash pages progressively (Erase flash pages progressively mcu-tools/mcuboot#323)
• MCUboot nrf52840_pca10059 support ( zephyr: nrf52840_pca10059 support mcu-tools/mcuboot#318 )
• Document how to use nrfutil to flash (doc: boards: pca10059: add bootloader documentation #11002)

/cc @lemrey @nvlsianpu

[carlescufi]

@larsgk thanks for creating this.

[carlescufi]

cc @jhedberg

[postlund]

I'm stuck with a few of these dongles that I want to flash with zephyr, but I don't have an external debugger (yet). If I understand it correctly, once this is done, I can flash without an additional debugger but I would still need one in the first place to place mcu_boot on the target, right? Using DFU-flash is not sufficient?

[carlescufi]

@postlund there is an issue with the current USB driver that @pawelzadrozniak is looking into. I think then that @lemrey needs to update the documentation on the board in order to describe how to use Zephyr without an external debugger.

[postlund]

Perfect, thank you!

[carlescufi]

@postlund @larsgk can you retry with current master? a fix was just merged #10934

[carlescufi]

@lemrey it looks like all the features are in place for this now. We just need to document how to transition from the built-in bootloader to MCUboot in order for people to be able to use this without a debugger.

[larsgk]

I can try when I get home

…

On Tue, Oct 30, 2018, 18:24 Carles Cufí ***@***.***> wrote: @lemrey <https://github.com/lemrey> it looks like all the features are in place for this now. We just need to document how to transition from the built-in bootloader to MCUboot in order for people to be able to use this without a debugger. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9055 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA97lm1Io2xGx8xXt1Km82Z5qMjla8zDks5uqItSgaJpZM4VYCnH> .

[tugstugi]

Is there now a documentation how to replace the stock bootloader without jlink?

[carlescufi]

@tugstugi not yet, @lemrey is working on it and will report soon

[Xenoamor]

Any idea why I can't get the hci_usb sample to work on this board? It appears to fail in the same way on both windows and linux. I'm uploading to the board via j-link and the blinky example works via this method

[lemrey]

Hi @Xenoamor, on this board the default peripheral used for HCI over UART is a UARTE peripheral. At the moment we are fixing an issue in the UARTE driver which is preventing the hci_uart sample to work as intented. Could you please check if it works any better with this patch #11475 ?

[Xenoamor]

Thanks, I'll give it a try when I'm back in the office tomorrow! Just to clarify that this is an issue I'm seeing with hci_usb and not hci_uart though

[carlescufi]

@Xenoamor so this is a completely different issue, not related to using this board without a debugger? Are you flashing using J-Link?

[Xenoamor]

Sorry yes I'm using a J-Link and nrfjprog. Should I make a new issue for this?

[carlescufi]

@Xenoamor yes please, this is completely unrelated.

[lemrey]

Thanks, I'll give it a try when I'm back in the office tomorrow! Just to clarify that this is an issue I'm seeing with hci_usb and not hci_uart though

Sorry @Xenoamor, I had misunderstood. What I said applies for HCI over UARTE.
Follow carlescufi's advice then and create a new issue.

[carlescufi]

All the required PRs have now been merged.
Thanks!