Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
Thursday, December 10th 2015, 9:36am
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link
Thursday, December 10th 2015, 4:13pm
Hello Nikla,
thanks for the explanation.
Official support for this Titan device is very welcome.
So far there were no problems with the internal flash programming.
The question just showed up with J-Link 5.10+ software because our scripts did not give the device in the expected order
and the "Unspecified" -> please select.. appeared, both with MB9DF125 and MB9EF226.
When beeing in
"C:\Program Files\SEGGER\JLink_V510c"
and running
where the commander script is
This now triggers a IRPre/DRPre question:
when adding the [code]Config 0,0[code] in first line of the commander script
i get the Device Selection message "The selected device "UNSPECIFIED" is unknown to this version of the J-Link software..".
What is the correct sequence to automatically conncet here?
Is there some equivalent command line option for the Config command?
thanks for the explanation.
Official support for this Titan device is very welcome.
So far there were no problems with the internal flash programming.
The question just showed up with J-Link 5.10+ software because our scripts did not give the device in the expected order
and the "Unspecified" -> please select.. appeared, both with MB9DF125 and MB9EF226.
When beeing in
"C:\Program Files\SEGGER\JLink_V510c"
and running
|
Source code |
1 2 3 4 5 6 |
JLink.exe -If JTAG -Speed 25000 -Device MB9DF126 -CommanderScript atlas_l.jlink -JLinkScriptFile Samples\JFlash\ProjectFiles\Fujitsu\MB9DF126.JLinkScript |
where the commander script is
|
|
Source code |
1 |
loadbin sample.bin,0x01000000 |
This now triggers a IRPre/DRPre question:
|
|
Source code |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
SEGGER J-Link Commander V5.10c (Compiled Dec 4 2015 17:25:58) DLL version V5.10c, compiled Dec 4 2015 17:25:20 Script file read successfully. Processing script file... J-Link connection not established yet but required for command. Connecting to J-Link via USB...O.K. Firmware: J-Link Ultra Rev.1 compiled Dec 3 2013 14:27:53 Hardware version: V1.00 S/N: 501200383 License(s): RDI, FlashBP, FlashDL, JFlash, GDB Emulator has Trace capability VTref = 4.588V Target connection not established yet but required for command. Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect JTAGConf> |
when adding the [code]Config 0,0[code] in first line of the commander script
i get the Device Selection message "The selected device "UNSPECIFIED" is unknown to this version of the J-Link software..".
What is the correct sequence to automatically conncet here?
Is there some equivalent command line option for the Config command?
Monday, December 14th 2015, 8:28pm
no not solved. It seems i can not avoid the JTAGConf> prompt,
even when doing "config 0,0".
results in
even when doing "config 0,0".
|
|
Source code |
1 2 3 4 5 6 |
si JTAG speed 25000 exec Device CORTEX-.. config 0,0 Device CORTEX-.. connect |
results in
|
|
Source code |
1 2 3 4 |
Cortex-.. identified. Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect JTAGConf> |
Wednesday, December 16th 2015, 7:49pm
Hi,
Sorry for the delay in response.
Could you try to invoke J-Link commander with this command line instead of setting the parameters in a commander script?
>>config 0,0<< does not set all variables required. We will fix this behavior in future versions of the J-Link software & documentation pack .
Best regards,
Niklas
Sorry for the delay in response.
Could you try to invoke J-Link commander with this command line instead of setting the parameters in a commander script?
Quoted
jlink.exe -device MB9DF126 -if JTAG -speed 25000 -JTAGConf -1,-1 -AutoConnect 1
>>config 0,0<< does not set all variables required. We will fix this behavior in future versions of the J-Link software & documentation pack .
Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link
Similar threads
-
J-Link/Flasher related »-
[SOLVED] J-Link debugger: option to use J-Link settings file
(Nov 5th 2015, 4:08pm)
-
- J-Link/Flasher related »
-
Programming security code on fujitsu-spansion MB9BFD18S
(Jun 30th 2014, 8:54am)
-
- J-Link/Flasher related »
-
J Link not detecting SK-MB9DF120-001
(Aug 2nd 2012, 3:14pm)
-
- J-Link/Flasher related »
-
Not able to find the Core using JLink
(Jul 18th 2012, 11:16am)
-
- J-Link/Flasher related »
-
STM32F207 support
(Apr 17th 2012, 11:30pm)