Dear,
I have nRF9160 DK, and I tried to control SW5 to debug/programme for nRF91 or nRF52.
I could programme for nRF91, but I couldnt do it for nRF52, for example, Im trying with /nrf/samples/bluetooth/central_uart/
and SW5 to nRF52, then Build and Run:
Did I do something wrong? misunderstand somewhere?
Regards,
hng
Hi Hoang,
Could you confirm that you used these settings when building the samples?
- SW5 to nrf52
- hci_uart
-build and flash for the nrf52
-SW5 to nrf91
- Build and flash for nrf91
Then power cycle the nrf91 DK and check the LTE Link Monitor. (it may take a while to get a link to the basestation the first time)
- make sure to uncheck the "Automatic requests" to use the LTE Link Monitor as a regular serial terminal:
I am adding the .hex files as well.
You can flash these .hex files using the command line:
nrfjprog --program hci_uart.hex -f nrf52 -r --sectorerase --verifyhci_uart.hex
nrfjprog --program lte_gateway.hex -f nrf91 -r --sectorerase --verifylte_gateway.hex
Best Regards,
Martin L.
Hi Hoang,
Could you confirm that you used these settings when building the samples?
- SW5 to nrf52
- hci_uart
-build and flash for the nrf52
-SW5 to nrf91
- Build and flash for nrf91
Then power cycle the nrf91 DK and check the LTE Link Monitor. (it may take a while to get a link to the basestation the first time)
- make sure to uncheck the "Automatic requests" to use the LTE Link Monitor as a regular serial terminal:
I am adding the .hex files as well.
You can flash these .hex files using the command line:
nrfjprog --program hci_uart.hex -f nrf52 -r --sectorerase --verifyhci_uart.hex
nrfjprog --program lte_gateway.hex -f nrf91 -r --sectorerase --verifylte_gateway.hex
Best Regards,
Martin L.
