HI, I am trying to connect IAR jlink with uvision 3.8. My computer is not even detecting the Jlink. It says the installation is not compelte, because it could not find the jlink.sys file. I am unable to find the jlink.sys file in my computer. Can someone help me in this?
IAR make their jlink to work with their tools;
Keil make their ulink to work with their tools;
I can't see either of them providing support for using their hardware with the other's tools...
Jlink is made by Seggar. At one time Keil had a driver for the Seggar Jlink. I believe it iterfaced with RDI. I will attempt to look up more info but I though I would throw this out and others might have more info sooner. Bradford
I looked into my MDK ARM toolset and found the Seggar Jlink supported. I could not find the same support in my PK51 tools. Bradford
Hi,
there are different J-Links out in the world.
- the BLACK J-Links can work with every IDE and every ARM - the BLUE (SAM-ICE) J-Links can work with every IDE and _only_ with Atmel's chips - the YELLOW (IAR-LINK) can _only_ work with IAR IDE and with every chip
Keil uVision supports all black J-Links (including SW/JTAG, SWO) and also the blue SAM-ICE. The IAR-LINK is locked and only works with IAR. think it is possible to scan the chain / SW with uVision, but debug/Flash download is impossible.
Other J-Links out there I've not tested...
--- Any further questions? :-)
BR, /th.
> Seggar Jlink They are called Segger :-)
> HI, I am trying to connect IAR jlink with uvision > 3.8. My computer is not even detecting the Jlink. It > says the installation is not compelte, because it > could not find the jlink.sys file. I am unable to > find the jlink.sys file in my computer. Can someone > help me in this?
You need to install the J-Link driver from http://www.segger.com first. The uVision setup contains three dlls: - jlinkarm.dll -> driver dll from segger, not for initial setup! - jltagdi.dll -> driver dll from Keil, for ARM7/9 support - jl2cm3.dll -> driver dll from Keil, for Cortex-M3 support
> I believe it iterfaced with RDI. RDI is depricated. Please use the appropriate driver dll as described above.
... at the SILabs forum which all come down to the fact that the SILabs "equivalent to jlink" and Keil are out of synch i.e. to use SILabs release x, you need Keil release y. Fortunately the SILabs JTAG emulator is complete and operates quite well as a freestanding program which does not seem to be the case for jlink.
I would GUESS that since, as you state, it is documented as avaliable, the problem is synchronization since, as the above similar is "out of synch" on a regular basis.
Do contact Keil support and request which Keil version match the version you have of jlink.
Erik
not just the main revisions, it should have read
"to use SILabs release x.abc, you need Keil release y.def.
I'm a bit *confused* about the two last posts. Technically there should be no big difference if that all are J-Links in a different robe :-) (black, blue, yellow, ...)
The J-Link itselv decides if it wants to operate or not, and this behaviour cannot be changed.
So, if the SI-Labs J-Link is not dependant on their GUI it should work with ARM7/9 J-Link / J-Trace or Cortex-M3 J-Link driver.
I do not have an SI Labs J-Link here so I cannot test ...
1) SILabs do NOT have a Jlink, they have an interface to Keil that gives ICE functionality. BTW SILabs do not make ARMs, but '51s
2) the interface keeps changing and thus I GUESSED that your Jlink problems could be an interface mismatch due to a Keil change.
ok, I am *still_confused* about the J-Link problems ...
1st: The (yellow) IAR J-Link does _not_ work with Keil, because it is a special Version of the J-Link.
2nd: If your computer says, that the J-Link is not installed properly, please doanload the latest driver package from segger (http://www.segger.com), which includes the windows kernel driver for J-Link, which is needed.