jaredwolff If it responds, that means comms are ok. Not sure what’s going on with newtmgr though. What’s the output of newtmgr conn show?
Barliesque $ newtmgr conn show Connection profiles: serial: type=serial, connstring=‘dev=COM4,baud=1000000’
jaredwolff Another thing that will trip the bootloader process up is if you have COM4 open somewhere else. newtmgr needs full access to the COM port or else it times out/fails. Your configuration settings look ok though.
Barliesque Is there some way to find out if another process is connected to COM4 that I was unaware of?
jaredwolff Barliesque Generally you need to open up a terminal program to do something like that. But I don’t know what’s installed on your machine that could be stealing away the COM port. If you’re able to connect using the LTE Link Monitor then my best guess is that your board (somehow) doesn’t have the correct bootloader. Do you have a nRF9160 or NRF53-DK handy? You can re-flash the bootloader so you can get going on your project.
jaredwolff You can also check with another computer. May be worth double checking that it’s not the machine you’re using right now. (Virtual Machines work well too)
Barliesque My company sent me a second board to work with which I didn’t have any problem with. So, definitely seems there’s an issue with that board. Anyway, thank you for your help with this!
jrherheim HI, I have the same situiation as above and worked through all the steps, so not fully ready out of the box. I have a nrf91 DK, but not the required cable. Are there any reference of which cable to use when updating the bootloader using the DK? Thanks.
jaredwolff You can use a Tag Connect cable as outlined in the documentation here: https://docs.jaredwolff.com/nrf9160-programming-and-debugging.html?highlight=tag%20connect#debugging-in-visual-code Hope that helps! P.S. since this is an old thread feel free to make a new one if you have any other questions.