run ble uart application with proper bootloader on a custom board

RE: run ble uart application with proper bootloader on a custom board

Hung Bui — Mon, 16 Mar 2015 12:54:20 GMT

@Liushu: I would suggest you to run in debug mode and check if it stuck or assert at some point. I think it most likely because the UART interface on your board and the beaconkit is not implemented properly. You can try to temporarily remove any UART related command in your code or change HWFC to false when configure UART to see if that helps.

RE: run ble uart application with proper bootloader on a custom board

liushu1314 — Fri, 13 Mar 2015 20:55:51 GMT

@Hung Bui: I tried both. After programming the SoftDevice 8, I saw that the start address in the nRFgo was 0x18000. For SoftDevice 7, the address was 0x16000. My main problem is that after programming the SoftDevice 7 or 8 with SDK7 or 8 's ble_app_uart application, my board and Beacon Kit are not broadcasting BLE signals. However, the Development Kit board does broadcast.

RE: run ble uart application with proper bootloader on a custom board

liushu1314 — Fri, 13 Mar 2015 20:50:52 GMT

After programming the SoftDevice 8, I saw that the start address in the nRFgo was 0x18000

RE: run ble uart application with proper bootloader on a custom board

Hung Bui — Fri, 13 Mar 2015 13:21:08 GMT

@liushu: please follow the instruction from Martin, you need to set the start address of iROM1 to 0x18000. I would suggest you to eigher use SDK v8.0 with S110 v8.0 or SDK v7.x with S110 v7.x. If you want to mix them you need to update the ROM location and the API file headers.

RE: run ble uart application with proper bootloader on a custom board

Chris — Thu, 12 Mar 2015 19:36:12 GMT

Beware when you switch to SDK 8 the section will be 0x18000 instead of 0x16000.

RE: run ble uart application with proper bootloader on a custom board

liushu1314 — Thu, 12 Mar 2015 17:59:11 GMT

Martin,

One more thing that I just noticed was that the DK uses nRF51422 chip while our board uses nRF51822. Would that be the case?

In the UART application, the output file is named nrf51422_xxac_s110.hex

Shu

RE: run ble uart application with proper bootloader on a custom board

liushu1314 — Thu, 12 Mar 2015 15:12:48 GMT

@Martin

SDK v7.0.0
both are 0x16000
The board is not broadcasting and i could not find it from BLE scan app if the bootloader is not programmed. However the DK board does broadcast.
I will try the SDK v8.0.0.

RE: run ble uart application with proper bootloader on a custom board

liushu1314 — Thu, 12 Mar 2015 15:08:35 GMT

@Hung Bui: The HWFC is off in the application and on our board, we only connect TX RX and GND signals to peer device, no flow controls.

RE: run ble uart application with proper bootloader on a custom board

Hung Bui — Thu, 12 Mar 2015 13:06:55 GMT

@Liushu: Could you check if in your code when you setting up simple uart you used HWFC or not. If you choose to use HWFC, you should connect all 4 pins for UART CTS, RTS, TXD & RXD to the peer device, otherwise the simplet uart will stuck at the loop to wait for CTS signal.

RE: run ble uart application with proper bootloader on a custom board

MartinBL — Thu, 12 Mar 2015 12:27:10 GMT

The experimental_ble_app_uart shouldn't need a bootloader. Neither should any nRF51 example/project in general if you are not planning to use a DFU or some custom solution. You only need a SoftDevice and your application code/example.

What SDK version are you using?
Are you sure that the IROM1 Start address is set correctly in both of your cases?
Can you clarify what you mean by "board can not be detected"? Is it detected by your programmer?

And by the way, we have just released SDK v8.0.0 where the ble_app_uart example is no longer experimental.

Martin