I was working with a nordic 52840 dev card with segger OB debugger; until I think I may have trashed the devcard.
Segger OB nolonger appears to be listed under linux when I do a "lsusb"; rebooting linux or unplugging/plugging the devcard does not make devcard appear.
It is almost like I have trashed the FW for the segger OB itself; which should be not be possible when running commands that should only be relevant to the connected development processor the 52840 on the devcard.
I have been working on porting some manufacturing scripting I use from windows to linux. As part of this port I cannot use nrfjprog (nordic segger programmig utility) as this does not exist for linux; hence I added some segger scripting to try and do the eraseall of my 52840 via the debugger core of the 52840 DAP CTRL_AP, CTRL_DP. After I did this the memory regions appeared erased.
But now the next day I try and access the JLinkExe says it cannot connect to the debugger; an as said the debugger is not listed under lsusb.
Anyone any ideas?
Is it possible to recover reload the Segger OB firmware?
I have visions of repeating this mistake with other units.....
All the best,
Owain
Segger OB nolonger appears to be listed under linux when I do a "lsusb"; rebooting linux or unplugging/plugging the devcard does not make devcard appear.
It is almost like I have trashed the FW for the segger OB itself; which should be not be possible when running commands that should only be relevant to the connected development processor the 52840 on the devcard.
I have been working on porting some manufacturing scripting I use from windows to linux. As part of this port I cannot use nrfjprog (nordic segger programmig utility) as this does not exist for linux; hence I added some segger scripting to try and do the eraseall of my 52840 via the debugger core of the 52840 DAP CTRL_AP, CTRL_DP. After I did this the memory regions appeared erased.
But now the next day I try and access the JLinkExe says it cannot connect to the debugger; an as said the debugger is not listed under lsusb.
Anyone any ideas?
Is it possible to recover reload the Segger OB firmware?
I have visions of repeating this mistake with other units.....
All the best,
Owain