If we edit the example code in seggar embedded, are the same changes done for the hex files of the same examples? IF not how do we change the code and put it in the dongle?
If we edit the example code in seggar embedded, are the same changes done for the hex files of the same examples? IF not how do we change the code and put it in the dongle?
SES creates an Output folder inside the SES folder from which you loaded the project. This folder contains a build type based on what you selected, IE Release or Debug. In these folders, under EXE you'll find the new hex file. You'll need to use nRF Connect to load the new hex file to the dongle (start nr fConnect, select programming, drag the new files to the right hand window, once you've selected the dongle as the device ).
You'll probably need to also add the softdevice to the files to be flashed if you are unsure as to which version is on the dongle. The softdevice can be found in the components/softdevice folder off the root of the SDK. The softdevice for the nrf 52840 is S140.
Hope this helps
SES creates an Output folder inside the SES folder from which you loaded the project. This folder contains a build type based on what you selected, IE Release or Debug. In these folders, under EXE you'll find the new hex file. You'll need to use nRF Connect to load the new hex file to the dongle (start nr fConnect, select programming, drag the new files to the right hand window, once you've selected the dongle as the device ).
You'll probably need to also add the softdevice to the files to be flashed if you are unsure as to which version is on the dongle. The softdevice can be found in the components/softdevice folder off the root of the SDK. The softdevice for the nrf 52840 is S140.
Hope this helps
In addition to the suggestion above, I would like to mention that we have a blog post that might be useful for you:
nRF52840 Dongle Programming Tutorial
Best regards,
Joakim.