1272 - Mico32:  How do I reestablish access to the LatticeMico32 debugger without rebooting?

The LatticeMico32 debugger is accessed using the Lattice USB download cable. Other Lattice tools like ispVM System, Reveal, and Orcastra also use the USB download cable. During development it is common to build and download new FPGA bitstreams. New bitstreams are loaded using ispVM System. Downloads from ispVM System are not prevented when a LatticeMico32 debug session is active.

In order to recover, on a Microsoft Windows system, without having to reboot you can try the following:

Launch the Windows Task Manager
Select lm32-elf-gdb (if present) and click on End Process
Use one of the following two solutions to terminate JTAGLServer

Select JTAGLServer and click on End Process.
Another solution for clearing the JTAGLServer is to unplug the USB cable, wait for a few seconds, and reinsert the USB cable.

Once these processes are terminated it should be possible to launch a new debug session without rebooting the PC.

Related Articles
5799 - [MachXO3] Lattice Mico32: Why is the Mico32 debugging not working on MachXO3-9400 Development Kit?
Add a PLL to drive the clock to 48 Mhz to make the clock faster and debugger to work.
2020 - Will open drain and HVOUT outputs have defined state when VCCD/VCCA are unavailable and VCCINP is supplied?
When VCCA/VCCD supply is turned off or it is not supplied, open drain output pins (OUTx) becomes High-Z and HVOUT will become low. The state would be similar to a reset state. Please refer to page 1-31 of the datasheet DS1015. Valid state/level for ...
1138 - Mico32: How to compile and link the Mico32 executable code to be either position-independent or relocatable?
Because the Mico32 compiler does not support the option to generate position-independent code, such as using only relative branch instructions for all code branching, the compiled code will not be position-independent, and it cannot be placed to any ...
1258 - Mico32: I updated my LatticeMico32 project after installing ispLEVER 8.1SP1 and now it doesn't work. What happened to my platform and how do I get it to work again?
The LatticeMico32 System Builder software has, from its inception, provided a set of components that provide industry standard interface functions. Four of these components were updated in ispLEVER 8.1SP1. The four components that changed are: RS232 ...
7406 - RISC-V CPU IP Core: Do Lattice RISC-V supports exception trap handler when writing data to an invalid address?
Description: RISC-V SM(v1.5)/MC(v2.5) CPUs currently only support trap handler for read access error. When CPU read from an invalid instruction/data address range, it will cause an exception which trigger the trap handler. However, if CPU write to an ...

1272 - Mico32:&nbsp; How do I reestablish access to the LatticeMico32 debugger without rebooting?

1272 - Mico32:&nbsp; How do I reestablish access to the LatticeMico32 debugger without rebooting?

Related Articles

5799 - [MachXO3] Lattice Mico32: Why is the Mico32 debugging not working on MachXO3-9400 Development Kit?

2020 - Will open drain and HVOUT outputs have defined state&nbsp;when VCCD/VCCA are unavailable and&nbsp;VCCINP is supplied?

1138 - Mico32: How to compile and link the Mico32 executable code to be either position-independent or relocatable?

1258 - Mico32: I updated my LatticeMico32 project after installing ispLEVER 8.1SP1 and now it doesn't work. What happened to my platform and how do I get it to work again?

7406 - RISC-V CPU IP Core: Do Lattice RISC-V supports exception trap handler when writing data to an invalid address?

1272 - Mico32: How do I reestablish access to the LatticeMico32 debugger without rebooting?

1272 - Mico32: How do I reestablish access to the LatticeMico32 debugger without rebooting?

2020 - Will open drain and HVOUT outputs have defined state when VCCD/VCCA are unavailable and VCCINP is supplied?