• State Not Answered
  • Replies 9 replies
  • Subscribers 71 subscribers
  • Views 1501 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 306488
Options

I also encountered the issue of 'Flash Download failed - "Cortex-M4"'

tony55723

Hi Nordic engineer,

I was able to flash before, but I reinstalled Keil5, J-Link, and downloaded Device Family Pack 8.24.1 and CMSIS 4.5.0 from the Nordic website. The SDK version is 15.3.0.

I really don't know how to solve this problem. Can you help me? Thanks

Note: I have three debuggers at hand, 5340 DK, 52840 DK, and a small package debugger given by someone else. The 52840 debugger did not respond when powered on, while the other two could be detected as J-Link and 52811 in Keil. I want to solve the issues with these two debuggers first before asking about the power-on problem with 52840.

Parents Reply
  • 0 in reply to tony55723

    Hi,

    I see, then this makes sense. I assume your nRF52811 device is revision 2 (see SoC revisions and variants)? This has an improved access port protection which is controlled by both SW and HW, and the debug interface is blocked by default (see Access port protection section in the product specification). This SoC is not supported in nRF5 SDK 15.3. See IN151 for more details.

    As you see from IN151, you need to update the MDK if you want to keep using the old SDK (though if this is a new project I recommend you migrate to a newer SDK). With an updated MDK, you only need to use nrfjprog --recover first to open the debug port, and then it will stay open when you flash your new application, as this now includes code from the MDK that allows debugger access.

Children
  • 0 in reply to Einar Thorsrud

    Hi Einar Thorsrud,

    After updating the 'Device Family Pack 8.29.0' I still couldn't download it. However, when I chose 'nRF52xxx softDevice erase,' I was able to download it successfully.

    Does changing the settings have any impact? I tried to download three modules, but only one module worked properly. For the remaining two modules, one module would disconnect when sending data through the phone's connect module, and the other module would receive data but send five times the amount of UART data when I only need one times the amount of data.

    Thank you...

    (This issue has been making my head spin...)

  • 0 in reply to tony55723

    Hi,

    There is no need to change these settings in Keil. However, Keil will not know about how to open up the debug interface on the latest revision devices, so if you have an empty device or a device that is flashed with firmware that does not open up the debug interface, you need to first do "nrfjprog --recover" from the command line using a fairly recent version of nRF Command Line Tools. With that, you should be able to program as normally (to be able to program multiple times and/or debug, you will also need the updated MDK).

  • 0 in reply to Einar Thorsrud

    Hi Einar Thorsrud,

    I feel a bit dizzy and I don't know what the problem is. I tried 4 different burning methods, but all of them failed.

    1、nRF command line

    2、nRFgo studio

    3、nRF connect

    4、keil download

    Regarding the first point, it feels like the pack is not installed. It seems that Keil requires the installation of Device Family Pack.

    Regarding the second point, it also feels like an issue with pack installation.

    Regarding the third point, because I am using Windows 7, if I install version 4.0.0 or 4.0.1, the nRF Connect app will show a gray screen when opened. I can only install an older version and click 'Launch anyway', but then it will give an error.

    Regarding the fourth point, the issue with Keil is still the same as before...

    I don't know how to solve this problem. Can you help me, please?

    Thanks.......

  • 0 in reply to tony55723

    Hi,

    nRFgo studio is legacy software and should not be used. It has not been maintained for a long time and does not know about the latest revision of the nRF52 series IC's.

    For Keil, it is correct that you need to install the device family pack. This is always required when using Keil, and is done from the Pack Installer.

    nRF Connect Programmer is the simplest GUI tool to use. I see from your screenshot that you have a version mismatch, though. Please install the latest version of nRF Connect for Desktop, including the bundeled J-Link drivers, and after that, ensure you have the latest nRF Connect Programmer app (within nRF Connect for desktop).

    However, if you have basic problems with being able to program, I would start with nrfjprog from nRF Command line tools. This way you can easily see the debugger, connecting to the nRF and debug interface there works as expected. With that in place, move on.

    For instance, does "nrfjprog --recover" seemingly work? Are you also able to program a hex file from there using "nrfjprog --program <filename>"? If so, the basics work and you can go back to looking at your Keil configuration (if the end goal is to get that working again).

  • 0 in reply to Einar Thorsrud

    Hi Einar Thorsrud,

    I'm sorry, I just replied to another question about PCB here

    I have deleted it, but I still feel sorry

    I searched for my agent and provided him with hex

    He told me that the address should not start from 0x00

    I don't know how this problem occurred, I haven't changed the address

    I rolled back two versions of my own code, and after downloading the program, it worked fine

    Additionally, I have installed nRF connect 4.0.0+

    After opening the software, the screen appears gray

    So I can only install the old version (3.8.0)

    Is this related to the Win7 I am using?

    Thank you

Related
Terms of service