• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 73 subscribers
  • Views 1270 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 108422
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Port rRF51 IoT SDK to RBL BLE Nano

Max

I compile the coap client example and drag-n-drop the hex file to a RBL BLE Nano. However, no advertising packets picked up by sniffer. Is it possible to port IoT SDK to a BLE Nano?

Parents
  • 0

    I believe the BLE Nano only has 16 kB of RAM.

    If you see in the release notes if IoT SDK 0.8.0 here, under supported boards, you will see that only the nRF51 DK is supported. This has a nRF51422. The examples should work on nRF51822 as well, but you need 32 kB of RAM. With 16 kB RAM, you may be able to use some of the examples in IoT SDK 0.7.0.

    In Keil you can try to set IRAM1 to start 0x20002000 and size 0x2000, and change Heap_Size EQU 2048 to Heap_Size EQU 0 in arm_startup_nrf51.s. Then you should be able to use the coap client example from IoT SDK 0.7.0.

  • 0 in reply to Petter Myhre

    I bought a few 32KB-RAM BLE Nano and can program COAP_Client to it. However, I can only merge the hex file generated in armgcc with s1xx-iot-prototype2_softdevice.hex but fail to do the same merge in arm4 with the following error message:

    ERROR: The hex files cannot be merged since there are conflicts.

Reply
  • 0 in reply to Petter Myhre

    I bought a few 32KB-RAM BLE Nano and can program COAP_Client to it. However, I can only merge the hex file generated in armgcc with s1xx-iot-prototype2_softdevice.hex but fail to do the same merge in arm4 with the following error message:

    ERROR: The hex files cannot be merged since there are conflicts.

Children
No Data
Related
Terms of service