Hi,
I had an odd problem recently with a J-Link Ultra in trying to connect to a Freescale KL03Z. In the mean time it has been solved but I wonder how.
I am using the Freescale KDS 2.0.0, the GDB client and the Segger GDB server.
I could get everything to work except connecting to the KL03Z device on my FRDM-KL03Z board.
The GDB client connected to the server as expected and the link from there to the J-link ultra worked as well.
After several hours of trying I started using the J-Link commander which connected equally well to the J-Link Ultra device.
I observed it trying to connect to the KL03Z device using all possible methods: JTAG, SWD, ... but none of it worked.
Instead of using the FRDM board I then tried connecting to our prototype hardware but got the same result for a number of hours.
Then I tried to see if I got any SWD clock signals using a scope.
I also changed the speed setting to automatic and restarted the J-link commander.
Again it tried all connection methods and this time it succeeded and came up with a connection speed of 100 kHz.
Ever since then everything works OK, including debugging in the KDS etc...
Could it be that changing the speed and restarting J-Link commander did the trick ?
If so, I know what to do if I run into problems again.
Any info much appreciated.
I had an odd problem recently with a J-Link Ultra in trying to connect to a Freescale KL03Z. In the mean time it has been solved but I wonder how.
I am using the Freescale KDS 2.0.0, the GDB client and the Segger GDB server.
I could get everything to work except connecting to the KL03Z device on my FRDM-KL03Z board.
The GDB client connected to the server as expected and the link from there to the J-link ultra worked as well.
After several hours of trying I started using the J-Link commander which connected equally well to the J-Link Ultra device.
I observed it trying to connect to the KL03Z device using all possible methods: JTAG, SWD, ... but none of it worked.
Instead of using the FRDM board I then tried connecting to our prototype hardware but got the same result for a number of hours.
Then I tried to see if I got any SWD clock signals using a scope.
I also changed the speed setting to automatic and restarted the J-link commander.
Again it tried all connection methods and this time it succeeded and came up with a connection speed of 100 kHz.
Ever since then everything works OK, including debugging in the KDS etc...
Could it be that changing the speed and restarting J-Link commander did the trick ?
If so, I know what to do if I run into problems again.
Any info much appreciated.