Sysprogs forums › Forums › VisualGDB › How to install nRF5x IoT SDK on visual GDB?
- This topic has 8 replies, 2 voices, and was last updated 8 years, 1 month ago by support.
-
AuthorPosts
-
September 5, 2016 at 12:47 #8972AnujaMutalikParticipant
Hi,
Can anyone tell me how to install nRF51 IoT SDK on visual GDB ?
Thanks ,
AnujaSeptember 6, 2016 at 02:27 #8978supportKeymasterHi,
We are actually working on supporting the new IoT SDK out-of-the-box and expect to release a BSP for it in the next couple of months.
If you want to set it up manually, please refer to the following thread for a discussion about the SDK. https://sysprogs.com/w/forums/topic/nrf5x-iot-sdk-setup-in-visualgdb/
- This reply was modified 8 years, 2 months ago by support.
September 6, 2016 at 07:43 #8983AnujaMutalikParticipantHi,
I want to set it up manually. Could you please give me link to the thread which you mentioned above?
Thanks,
AnujaSeptember 6, 2016 at 16:32 #8988supportKeymasterHi,
Sure, sorry, looks like the link did not get inserted properly first: https://sysprogs.com/w/forums/topic/nrf5x-iot-sdk-setup-in-visualgdb/
September 6, 2016 at 23:22 #8992AnujaMutalikParticipantHi,
Thank you for the link. Actually, I only had posted that question.
I have been successful in adding all IOT specific files to current SDK on visual GDB. But it seems there is some issue with softdevice. The IOT SDK expects ‘IOT softdevcie’, whereas the SDK on visual GDB has s130. So how can I change this s130 to ‘IOT softdevice’ ? I have hex file and .o file for ‘IOT softdevice’. How can I use them with visual GDB?
Thank you for the support.
September 7, 2016 at 04:30 #8997supportKeymasterHi,
In order to use a custom softdevice in your VisualGDB project, you will need to do 2 steps:
- Convert the softdevice from the .hex format to a .o file (see nRF51\SoftdeviceLibraries\ConvertSoftdevice.bat)
- Modify your linker script to have correct addresses/sizes for the softdevice FLASH/RAM and program FLASH/RAM (you can take those from the linker scripts in the IoT SDK).
- Change the name of the .o file with the softdevice mentioned in the linker script (inside the GROUP() statement).
September 7, 2016 at 06:34 #8998AnujaMutalikParticipantHi,
Thank you very much for the guidelines. I have performed all above steps. But now I am getting ‘connection_handler missing’ error in all of the SVCALL instructions of BLE. Could you tell me reason of these errors and how to solve them?
September 7, 2016 at 06:53 #8999AnujaMutalikParticipantHi,
I have one more question.
I am trying to integrate IoT SDK with the current version of SDK on visual GDB. I am trying to make CoAP protocol files run. I am using all IoT specific files and IoT softdevice’ files from new IoT SDK. Will it work in this way? There won’t be any version mismatch between IoT softdevice’ and current SDK ?
Thanks ,
AnujaSeptember 11, 2016 at 18:50 #9035supportKeymasterHi,
This is something that the Nordic guys should know much better than us. Their softdevice is closed-source, so it’s hard to say how compatible different versions are. Please consider contacting the Nordic support or asking on their forums.
-
AuthorPosts
- You must be logged in to reply to this topic.