nrf52840_xxAA_REV2 not woring the mcuboot with sdk 3.4.0

[John Galvin]

I've trying to get MCUBOOT woth work with my project & after much time/effort & found my project, untoughed, works on the  nrf52840DK. I then discovered that the  mcuboot build in 3.4.0 (don't know about other SDK's) does not wotk with nrf52840_xxAA_REV2, which is on my board. I found this out because, luckly, I have another board which had the  nrf52840_xxAA_REV3 & this works.

Please can someone clarify with is is true, or I jast have a fault REV2 chip. If this is true, how amy I suposed to hanle this?

[Vidar Berg]

Hello,

If you already have an application that runs fine without a bootloader, this is most likely a configuration issue in the mcuboot build. Does your board design include the optional 32 kHz crystal and the DCDC inductors like the nRF52840 DK? If you build an SDK sample for the nRF52840 DK board, it will be configured to use both by default.

Best regards,

Vidar

[John Galvin]

After further investigation the BT does not run correctly in my application on REV2 parts (I only intend using BT for the bootloader)

As mentioned initially, I found some of my boards which have rev 3 parts fitted & the BT work with my project & the bootloader works too. so my project (at least) does not work with rev 2 parts.

Just to clarify, my hardware fitted with rev 3 parts work with my project as-is..My hardware with rev 2 parts fitted does not work with BT or BT bootloader.

Is there anything I can change so the rev 2 part will work, or do I just need to scrap the rev parts & only use rev 3?

[Vidar Berg]

I am sceptical that this issue is related to the silicon revision. Does your board have the 32 kHz crystal fitted?

[John Galvin]

Yes, my board has the 32khz crystal on it

[Vidar Berg]

Thanks for confirming. 

John Galvin said:

After further investigation the BT does not run correctly in my application on REV2 parts (I only intend using BT for the bootloader)

If you want to troubleshoot the issue further, please repeat this test with the internal RC oscillator selected as the 32K clock source by adding CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y to your project configuration. This will help rule out the clock source as the cause of the problem.