51822 bootloader setting

RE: 51822 bootloader setting

Edvin — Fri, 13 May 2022 10:22:08 GMT

I forgot that the keil projects for the bootloader had this. If it works, that is completely fine. What the different command does is quite self explaining. The --reset flag will reset the device when the programming is complete. So if you don't have the --reset flag, you will need to reset the device manually, either by power cycling it, or by using the command nrfjprog --reset.

The --family NRF51 just tells the programmer that it is an nRF51 chip. If you don't specify it, the programmer will check a register that says what chip it is.

Best regards,

Edvin

RE: 51822 bootloader setting

Yulien — Fri, 13 May 2022 01:40:34 GMT

Hi Edvin,

　　Raytac engineer helps me to find out a little different.

In my project which is transformed from SDK sample code, I use these argument setting:

And these are Raytac engineer using (I was told that he uses SDK, too):

So, I try the following 3 argument settings:

--family NRF51 --program "#H"　　　　　➜ I use at first　
--reset --program "#H"　　　　　　　　 ➜ Raytac uses
--reset --family NRF51 --program "#H　 ➜ I mix 1 & 2

Both setting 2 and 3 lead modules to work.

After I turn back to try setting 1, modules work, too.

It seems there is something wrong if I keep using setting 1; and in 2 or 3 Keil fixes the problems.

Thank you for your help.

RE: 51822 bootloader setting

Edvin — Thu, 12 May 2022 11:42:19 GMT

Have you tried using nrfjprog (nrf command line tools)

But you never see these JLink - Cortex-M Error when you debug your application (without bootloader)?

When you try to debug the bootloader, does the JLink error come immediately, or does it reach the main() function first?

RE: 51822 bootloader setting

Yulien — Thu, 12 May 2022 05:31:54 GMT

Hi Edvin,

　　I use either Keil or nrfgo studio through Jlink.

　　If I try to use programmer in nrf connect for desktop, it cannot read my board. It might be some problem which I haven't figure out yet.

RE: 51822 bootloader setting

Edvin — Wed, 11 May 2022 09:08:42 GMT

How have you connected the programmer to your boards, and what programmer are you using?

RE: 51822 bootloader setting

Yulien — Tue, 10 May 2022 10:05:57 GMT

Hi Edvin,

[quote userid="26071" url="~/f/nordic-q-a/87654/51822-bootloader-setting/367082#367082"]So if you have an LFXTAL (32kHz physical xtal) with 20PPM accuracy, that is fine. If not, look in the enum from nrf_sdm.h, line 100, and find one entry that suits your HW. If you don't have an LFXTAL, try using NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION.[/quote]

I've changed it into "NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION" already.

[quote userid="26071" url="~/f/nordic-q-a/87654/51822-bootloader-setting/367082#367082"]If that doesn't work, then have you tried debugging? Try setting a breakpoint in the main() function of the bootloader. What happens? Is it reached?`Try to compare the working and non working device, and see if you see any difference in behavior.[/quote]

Yes, I just use debug mode for a while. It stops and shows this error when the code comes to nrf_delay.h.

The other module, which can work well, stops at other place.

I think there are answers about these errors in devzone, but I haven't figure it out yet.

RE: 51822 bootloader setting

Edvin — Tue, 10 May 2022 08:01:06 GMT

[quote user="Yulien"]According to Raytac document, there is a 16MHz crystal on board, which is covered by a metal shield. Crystal on the other module could be seen with the naked eye.[/quote]

So no LFXTAL (32kHz), then? Does your application settings (sdk_config.h) take this into consideration?

I am not that familiar with the SDK10 bootloader, as it is starting to get quite old, but from a quick glance, the main.c seems to have something like this (looking at the dual_bank_ble_s110 bootloader):

in main.c, line 154:

SOFTDEVICE_HANDLER_APPSH_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, true);

So if you have an LFXTAL (32kHz physical xtal) with 20PPM accuracy, that is fine. If not, look in the enum from nrf_sdm.h, line 100, and find one entry that suits your HW. If you don't have an LFXTAL, try using NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION.

If that doesn't work, then have you tried debugging? Try setting a breakpoint in the main() function of the bootloader. What happens? Is it reached?`Try to compare the working and non working device, and see if you see any difference in behavior.

Best regards,

Edvin

RE: 51822 bootloader setting

Yulien — Tue, 10 May 2022 01:47:35 GMT

Thank you for your information.

I forgot to say. I use legacy dfu.

[quote userid="26071" url="~/f/nordic-q-a/87654/51822-bootloader-setting/366736#366736"]Where did you get the twi different configuration from?[/quote]

I get address from "Project" listed in Keil toolbar.

This is from sample code, so I only change memory map and board settings to fit 51822.

[quote userid="26071" url="~/f/nordic-q-a/87654/51822-bootloader-setting/366962#366962"]Did you try to make sure it was erased before you start? When you hit "Erase all", does it give any errors? If you disconnect and reconnect it, does it appear as only one region, or does it still say "Bootloader" and "Application" regions?[/quote]

Yes, I check every time before I download hex through either Keil or nrfgo studio. In both modules, I could see only one region if I erase all, with no error occurred.

[quote userid="26071" url="~/f/nordic-q-a/87654/51822-bootloader-setting/366962#366962"]So check the flash after programming both devices, and check the readbacks to see that they match, and check whether the one that isn't working has an LFXTAL or not (32kHz crystal). [/quote]

According to Raytac document, there is a 16MHz crystal on board, which is covered by a metal shield. Crystal on the other module could be seen with the naked eye.

If I download only softdevice(s110)+application, it works well on both module (including BLE connection); when it comes to softdevice+application+bootloader, it would fail on Raytac module.

So, I guess there is no difference between the two modules, and the reason may come from bootloader.

RE: 51822 bootloader setting

Edvin — Mon, 09 May 2022 13:23:05 GMT

Sorry, I meant "two" not "twi". I am sorry for the confusion.

I don't know anything about Raytac bootloader, but if you have erased it, I guess that shouldn't matter. Did you try to make sure it was erased before you start? When you hit "Erase all", does it give any errors? If you disconnect and reconnect it, does it appear as only one region, or does it still say "Bootloader" and "Application" regions?

If it doesn't work to erase it using nRFGo studio, please try to use nRF Command Line Tools, and the command "nrfjprog --recover". The reason is that it says that the readback protection is turned on, so you may need to recover the module first. This will erase the chip, and disable the readback protection.

Other than that, are the two modules identical? Does both of them (or none, or only one) have a built in LFXTAL? Did you try to read out the flash after flashing the devices to check that they are the same after being programmed? You can use "nrfjprog --readcode my_flash_dump.hex" and "nrfjprog --readuicr my_uicr_dump.hex" to read out both the flash and UICR registers on both devices. Then you can use a diff tool (I use "Meld", which is a free diff tool) to see whether the content on the flash is actually the same.

[quote user="Yulien"]1. What does "0x0072", which is listed after QFAAH00 in the image, mean?[/quote]

I guess it is just a register it uses to identify the version of the chip.

[quote user="Yulien"]2. Bootloader doesn't work without softdevice, does it?[/quote]

If it is a BLE bootloader, then no, it doesn't work without the softdevice. If it is a serial bootloader, it will work if you have either programmed the softdevice or the MBR. You would use the MBR if your application and bootloader doesn't use the softdevice. The bootloader requires the MBR. The MBR is part of the softdevice, but also exists as a standalone .hex file. If you flash the softdevice, you don't need to flash the MBR separately.

So check the flash after programming both devices, and check the readbacks to see that they match, and check whether the one that isn't working has an LFXTAL or not (32kHz crystal).

Best regards,

Edvin

RE: 51822 bootloader setting

Yulien — Mon, 09 May 2022 01:00:14 GMT

Hi Edvin,

I use Keil v5 and SDK 10 to build bootloader, SDK 7.2 to build application, through both Keil and nrfgo studio to download hex.

I'm not sure what do you mean because I don't use I2C or SPI but UART in my code.

[quote userid="26071" url="~/f/nordic-q-a/87654/51822-bootloader-setting/366736#366736"]

Where did you get the twi different configuration from?

[/quote]

At the very beginning, Raytac module has bootloader inside (attached image), and the other is totally empty. I do erase the memory before download into them.

RE: 51822 bootloader setting

Edvin — Fri, 06 May 2022 13:03:40 GMT

Hello,

What SDK version are you using?

Where did you get the twi different configuration from?

How do you program the devices? Are you using a programmer for both of them? And did you make sure to delete the flash before you programmed everything? (nrfjprog --eraseall if you are using a programmer).

Best regards,

Edvin