This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF52_DK 2.0.0 interface MCU MBED FW problem

Hi all,

i've try to update the NRF52_DK interface MCU firmware to MBED firmware (nrf5x_atsam3u2c_if_mbed_V0221_11012017.bin).

After power cycle, LD5 at interface MCU blinking, the hardware does not answer. 

I tried to update to 0253_SAM3U2C_MKIT_DK_DONGLE_NRF5X_0X5000.BIN at https://armmbed.github.io/DAPLink/ but it is failed too.

When i try to update to JLink firmware, it is working, but the MBed Studio not allow debugging via PyOCD.

The previous version of NRF52_DK (1.2.0) works fine with both of MBed interface firmware. 

Is there any update for 2.0.0 board to enable MBed?

Thank you, best regards,

David

Parents
  • Hello David,

    The nRF52 DK is indeed compatible with MBed, but you will need to use their firmware.

    Is there any update for 2.0.0 board to enable MBed?

    You will also need to update the JLink debugger firmware.

    Personally I am not familiar with using MBed Studio or Mbed software, but I suggest that you open a ticket at the Mbed forums instead - to have a look at the JLink firmware update issue.

    For future reference, it will become much easier to help you resolve your issue if you would elaborate / be more specific about what fails and what errors are generated, in reference to when you say "it failed too". Any additional error detail is beneficial.

    Best regards,
    Karl

Reply
  • Hello David,

    The nRF52 DK is indeed compatible with MBed, but you will need to use their firmware.

    Is there any update for 2.0.0 board to enable MBed?

    You will also need to update the JLink debugger firmware.

    Personally I am not familiar with using MBed Studio or Mbed software, but I suggest that you open a ticket at the Mbed forums instead - to have a look at the JLink firmware update issue.

    For future reference, it will become much easier to help you resolve your issue if you would elaborate / be more specific about what fails and what errors are generated, in reference to when you say "it failed too". Any additional error detail is beneficial.

    Best regards,
    Karl

Children
No Data
Related