Running the BLE bootloader example

RE: Running the BLE bootloader example

Javier — Mon, 16 Jan 2017 14:31:40 GMT

Don´t worry! :)

RE: Running the BLE bootloader example

bjorn-spockeli — Mon, 16 Jan 2017 13:58:06 GMT

Great! Again, I apologize for not catching this earlier.

RE: Running the BLE bootloader example

Javier — Mon, 16 Jan 2017 13:28:25 GMT

Tested the new changes on two diferent custom nRF51822 boards and It works like a charm!!!! Thank you!!!

RE: Running the BLE bootloader example

bjorn-spockeli — Mon, 16 Jan 2017 13:10:49 GMT

I am sorry for not catching this earlier, but the nRF51822 QFAA only has 16 kB of RAM(0x4000) bytes. The bootloader example in the SDK is intended for the nRF51422 QFAC which has 32 kB of RAM. This means that you have to adjust the RAM size to the following:

IRAM1: Start 0x20002C00 Size 0x1380
IRAM2: Start 0x20003F80 Size 0x80   No Init: set

Does this solve the issue?

RE: Running the BLE bootloader example

Javier — Mon, 16 Jan 2017 12:50:34 GMT

This chip: nRF51822QFAAH00 So, in the target option I have the following settings:

IROM1: Start 0x3C000 Size 0x3C00
IRAM1: Start 0x20002C00 Size 0x5380
IRAM2: Start 0x20007F80 Size 0x80   No Init: set

RE: Running the BLE bootloader example

bjorn-spockeli — Mon, 16 Jan 2017 12:12:13 GMT

Ok, so you still reach dfu_ble_peer_data_get(), but it does not return? The chip you're trying to run it on is a nRF51822 QFAA right? Could you post the ROM and RAM settings you're using?

RE: Running the BLE bootloader example

Javier — Mon, 16 Jan 2017 11:52:55 GMT

Yes, they do have. Both crystals, 32kHz and 16MHz

RE: Running the BLE bootloader example

bjorn-spockeli — Mon, 16 Jan 2017 11:47:08 GMT

Does the custom boards have external 32kHz crystals like the nRF51 DK?

RE: Running the BLE bootloader example

Javier — Mon, 16 Jan 2017 09:37:58 GMT

Well, with the nRF51822 still the same problem. No matter if I upload the bootloder for SoftDevice S110 or S130, it does not advertise the NRF_Targ. I will continue testing with other custom boards.

RE: Running the BLE bootloader example

bjorn-spockeli — Thu, 12 Jan 2017 11:35:46 GMT

Are you still seeing the same issue as before or is there a new issue that causes the bootloader code to not function properly on the custom nRF51822 board?

RE: Running the BLE bootloader example

Javier — Thu, 12 Jan 2017 11:16:51 GMT

Dear Bjørn, In the end we have managed to make the bootloader work but in the PCA10031 (USB Dongle). Still we couldn´t make it work in the nrf51822, so technically it is not problem of the code...

RE: Running the BLE bootloader example

bjorn-spockeli — Tue, 29 Nov 2016 15:29:34 GMT

Yes, in the app_error_weak.c file.

RE: Running the BLE bootloader example

Javier — Tue, 29 Nov 2016 14:10:19 GMT

You mean in the app_error_weak.c file?

RE: Running the BLE bootloader example

bjorn-spockeli — Tue, 29 Nov 2016 11:40:13 GMT

Hi Javier, you can just ignore the nrf_delay.h include error, it is a known issue that will not affect your code. However, I cant see why execution should stop in crc16_compute, it should return the crc value and then an error if its incorrect. Can you set a breakpoint in app_error_fault_handler and see if you end up there ?

RE: Running the BLE bootloader example

Javier — Tue, 29 Nov 2016 08:36:54 GMT

Hi again!

I have been checking the whole code again. I always had an error while including "nrf_delay.h", more a "cosmetic" error since it works fine. Now I also have one error in: #include "bootloader.h"

The error states: error in include chain (cmsis_armcc.h): expected identifier or ´(´ So I open the header file, which it took me to another and another untill the "error" in cmsis_armcc.h.

The error is in the line 48:

__STATIC_INLINE uint32_t __get_CONTROL(void)

error: unknown type name ´__STATIC_INLINE´ error: expected ´;´after top level declarator

In the Pack Installer, the ARM::CMSIS is up-to-date.

Any idea? or it is not a real error?

Javier

RE: Running the BLE bootloader example

Javier — Mon, 28 Nov 2016 13:09:11 GMT

Hi! While in debug mode, inside dfu_transport_update_start(void) it reachs to err_code = dfu_ble_peer_data_get(&m_ble_peer_data); Inside that function it gets stuck in:

crc = crc16_compute((uint8_t *)&m_peer_data, sizeof(m_peer_data), NULL);

There is where the debugger gets blocked...

RE: Running the BLE bootloader example

bjorn-spockeli — Fri, 25 Nov 2016 15:25:22 GMT

Hi Javier, that is expected, as the bootloader will enter a infinite for loop when it enters wait_for_events() in bootloader_dfu_start(). Can you check if you reach advertising_start() in dfu_transport_update_start() in dfu_transport_ble.c? If it returns from this function, then the device should advertise.

RE: Running the BLE bootloader example

Javier — Fri, 25 Nov 2016 14:18:58 GMT

It gets blocked at bootloader_dfu_start(); I am trying to find the exact point.

RE: Running the BLE bootloader example

bjorn-spockeli — Fri, 25 Nov 2016 10:06:00 GMT

Are you able to debug the bootloader, i.e. do you enter the main() of the bootloader?

RE: Running the BLE bootloader example

Javier — Fri, 25 Nov 2016 07:28:22 GMT

No, the App nRF Connect doesn´t detect something. I have double-checked that the board works uploading again an example (ble_app_uart) and it works perfectly....but the bootloader still not working

RE: Running the BLE bootloader example

bjorn-spockeli — Thu, 24 Nov 2016 14:31:49 GMT

Are you able to see the device advertising with the nRF Connect for Android or iOS app?

RE: Running the BLE bootloader example

Javier — Thu, 24 Nov 2016 13:10:03 GMT

Hello Bjørn,

I have tried with nRF51822QFAAH00 (0x0072).

First with the nRFgo Studio I have flashed the device, and then uploaded the: nRF5_SDK_11.0.0_89a8197/components/softdevice/s130/hex/s130_nrf51_2.0.0_softdevice.hex
In KeiluVision I have opened nRF5_SDK_11.0.0_89a8197\examples\dfu\bootloader\pca10028\dual_bank_ble_s130 In project option, in the utilities Tab for the nrfjprog.exe I have added the following line: --program "#H" -f NRF51 And then in the code modified the pins of LED´s to: Led1 3 / Led2 4 / Led3 6 / Button4 7

The reason of those changes is because those are the PINs I have acces to. Uploaded the code, and again the MCP doesn´t detect the Board and LED1 and 2 are on. LED3 is off. I have tried with the Button....nothing at all

Javier

RE: Running the BLE bootloader example

bjorn-spockeli — Tue, 22 Nov 2016 12:54:57 GMT

Happy to help. Let me know when you've tried this on a rev 3 IC.

RE: Running the BLE bootloader example

Javier — Tue, 22 Nov 2016 12:01:04 GMT

You are right, the chip version of the PCA10004 Rev.2.2.0 is the N51822QFAAG0, non compatible. Then I have a custom board with the chip N51822QFAAG2, but this one also enter in the revision 2 IC? I will check with another custom board with N51822QFAAH0, revision 3.

Thank you.

RE: Running the BLE bootloader example

bjorn-spockeli — Tue, 22 Nov 2016 11:37:14 GMT

If you're using a PCA10004 Rev.2.2.0 board, then its higly likely that you're using a nRF51822 IC revision 2 chip, please check the chip markings against the overview on this Infocenter page. If you're using a revision 2 IC, then its not compatible with SDK v11.0.0, please see the compatibility matrix found here.