I am trying to use nrf5280dk with RIOT OS and Contiki OS. I am following these steps to enable access to the device from os.https://devzone.nordicsemi.com/b/blog/posts/setting-up-ipv6-over-ble-using-nrf52-series-and-ri
Setup: Running RIOT OS with vagrant (Virtual Box) in Windows 10 Host machine.
Setup: Running Contiki OS with vagrant (Virtual Box) in Windows 10 Host machine.
I installed the required tools. But, I am getting the following error when I try to connect with the device (nrF52dk)
This image is from RIOT.
I can surely say Contiki was able to detect the device where as I cannot confirm the same for RIOT OS.
Though the error message remains same for both.
The following image is from Contiki, I feel this is some kind of driver issue. But, there is only one software needed.
Exactly same result when I tried this command in RIOT OS.
Update: I was able to connect but not able to flash in Contiki.
I have a followup issue, so instead of creating a new one, I am going to add the same here.
Also, having trouble flashing the board nrf52dk.
**Setup**: Windows 10 Host, Virtual Contiki OS (Ubuntu 14). Using VMWare Workstation Player.
I am following the Tutorials from these links:
1) devzone.nordicsemi.com/.../setting-up-ipv6-over-ble-using-nrf52-series-and-co2) github.com/.../Platform-nrf52dk
**Command**: Target=nrf52dk make![image](user-images.githubusercontent.com/.../45601021-ab67b400-b9cb-11e8-922a-ea2d7f8ecc9a.png)
I am able to connect with the device using J-Link using both connect and usb.So, Contiki-OS is able to read and connect with the device correctly.
Please help. Let me know if I am missing something or if this is some kind of driver issue or something else. Thanks.
Hi Navneet. Two things spring to mind. Firstly are other USB devices able to be seen from these two OS's. I know I have been bitten by problems with USB support into a VM in the past. Secondly I have found the physical USB connection on the DK board to be a bit sub par. Make sure you plug into a USB 3 socket - more current. Secondly ensure there is no strain on the plugs either end - cable is loose and not bent. Finally try another cable.
hope this helps
Hey Paul, actually virtual is having some issue. So, switched to VMWare and it worked. I have another question though.
There seems to a conflict between toolchain/device and RIOT OS (hard compilation vs soft compilation). Does anything come to your mind? I am using GCC ARM toolchain.
Is there a particular toolchain I should install to make it work? Thanks.
I think that the soft/hard thing refers to how the floating point is handled. Some arm processors can do floating point in hardware otherwise gcc adds software support.
If you hang around here long enough you will find out that relatively recently Nordic moved from pushing an IDE called IAC and another called Keil to pushing a new one called Segger Embedded studio (often abreviated to SES). When I say pushing, you can use whatever you like and people, including Nordic, will try and help you, but that is now the default. It was also built in consultation with this forum and Nordic so possibly supports the nordic chips the best.
Because you are using a nordic chipset, you can get a free license for SES and download it. Things that I hate about it are that it uses all its own libraries etc - one mistake I made was to try and mix in some standard Linux libs. Secondly it tends to put every file in the root directory. Thirdly you have to essentially list every file you use which makes starting hard especially if you are building off a Nordic example and want to move the code.
I am very much a newbie with only about 6 weeks in this environment.
BTW generally best to start a new thread when you have a new question - makes it easier for the searchers who follow.
BTW2 Nordic tends to chime in on unanswered posts after a couple of days - all cudos to them.
Hey Paul, thanks for the insight. Actually, the issue was that the toolchain was not upgraded to v7. Even a fresh install via Linux cmd was resulting in v6.