Thursday, April 19th 2018, 1:58pm UTC+2

You are not logged in.

  • Login
  • Register

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.

nobody

Beginner

Date of registration: Mar 7th 2018

Posts: 2

1

Wednesday, April 11th 2018, 4:21pm

JLINK how to get uboot running on imx6ull

Hello,

I have a imx6ull evk and I would like to test the JTAG interface. Executing JLinkExe and starting JLinkGdbServer works fine.

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
SEGGER J-Link Commander V6.30k (Compiled Apr  9 2018 18:33:16)
DLL version V6.30k, compiled Apr  9 2018 18:33:07

Connecting to J-Link via USB...O.K.
Firmware: J-Link V10 compiled Mar 29 2018 17:45:34
Hardware version: V10.10
S/N: 50105141
License(s): GDB
VTref = 3.315V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: MCIMX6Y2
Type '?' for selection dialog
Device>
Please specify target interface:
  J) JTAG (Default)
  S) SWD
TIF>
Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MCIMX6Y2" selected.


Connecting to target via JTAG
J-Link script: Setting up AP map
TotalIRLen = 13, IRPrint = 0x0101

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)

**************************

JTAG chain detection found 3 devices:
 #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
 #1 Id: 0x00000001, IRLen: 05, Unknown device
 #2 Id: 0x088C101D, IRLen: 04, JTAG-DP
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[1]: APB-AP (IDR: Not set)
Using preconfigured AP[1] as APB-AP
AP[1]: APB-AP found
ROMTbl[0][0]: CompAddr: 80001000 CID: B105900D, PID:04-001BB961 TMC
ROMTbl[0][1]: CompAddr: 80002000 CID: B105900D, PID:04-004BB906 CTI
ROMTbl[0][2]: CompAddr: 80003000 CID: B105900D, PID:04-004BB912 TPIU
ROMTbl[0][3]: CompAddr: 80004000 CID: B105F00D, PID:04-001BB101 TSG
ROMTbl[0][4]: CompAddr: 80020000 CID: B105100D, PID:04-000BB4A7 ROM Table
ROMTbl[1][0]: CompAddr: 80030000 CID: B105900D, PID:04-005BBC07 Cortex-A7
Found Cortex-A7 r0p5
6 code breakpoints, 4 data breakpoints
Debug architecture ARMv7.1
Data endian: little
Main ID register: 0x410FC075
I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 32 KB, 128 Sets, 64 Bytes/Line, 4-Way
Unified-Cache L2: 128 KB, 256 Sets, 64 Bytes/Line, 8-Way
System control register:
  Instruction endian: little
  Level-1 instruction cache enabled
  Level-1 data cache disabled
  MMU disabled
  Branch prediction enabled
Cortex-A7 identified.
J-Link>
Unknown command. '?' for help.
J-Link>


Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
SEGGER J-Link GDB Server V6.30k Command Line Version

JLinkARM.dll V6.30k (DLL compiled Apr  9 2018 18:33:07)

-----GDB Server start settings-----
GDBInit file:              	none
GDB Server Listening port: 	2331
SWO raw output listening port: 2332
Terminal I/O port:         	2333
Accept remote connection:  	yes
Generate logfile:          	off
Verify download:           	off
Init regs on start:        	off
Silent mode:               	off
Single run mode:           	off
Target connection timeout: 	0 ms
------J-Link related settings------
J-Link Host interface:     	USB
J-Link script:             	none
J-Link settings file:      	none
------Target related settings------
Target device:             	Unspecified
Target interface:          	JTAG
Target interface speed:    	4000kHz
Target endian:             	little

Connecting to J-Link...
J-Link is connected.
Failed to set device (Unspecified). Unknown device selected?ERROR : Failed to set device.

Firmware: J-Link V10 compiled Mar 29 2018 17:45:34
Hardware: V10.10
S/N: 50105141
Feature(s): GDB
Checking target voltage...
Target voltage: 3.32 V
Listening on TCP/IP port 2331
Connecting to target...ERROR: No CPU core or target device has been selected. Please make sure at least the core J-Link shall connect to, is selected.
ERROR: Could not connect to target.
Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
Shutting down...
Could not connect to target.
Please check power, connection and settings.cb82lol@cb82lol:~$ JLinkGDBServer -device MCIMX6Y2
SEGGER J-Link GDB Server V6.30k Command Line Version

JLinkARM.dll V6.30k (DLL compiled Apr  9 2018 18:33:07)

Command line: -device MCIMX6Y2
-----GDB Server start settings-----
GDBInit file:              	none
GDB Server Listening port: 	2331
SWO raw output listening port: 2332
Terminal I/O port:         	2333
Accept remote connection:  	yes
Generate logfile:          	off
Verify download:           	off
Init regs on start:        	off
Silent mode:               	off
Single run mode:           	off
Target connection timeout: 	0 ms
------J-Link related settings------
J-Link Host interface:     	USB
J-Link script:             	none
J-Link settings file:      	none
------Target related settings------
Target device:             	MCIMX6Y2
Target interface:          	JTAG
Target interface speed:    	4000kHz
Target endian:             	little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link V10 compiled Mar 29 2018 17:45:34
Hardware: V10.10
S/N: 50105141
Feature(s): GDB
Checking target voltage...
Target voltage: 3.32 V
Listening on TCP/IP port 2331
Connecting to target...WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)


J-Link found 3 JTAG devices, Total IRLen = 13
JTAG ID: 0x5BA00477 (Cortex-A7)
Connected to target
Waiting for GDB connection...


My first aim is to load a u-boot image to the RAM and execute it.
Does anyone have a proper docu?

Thanks

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 931

2

Thursday, April 12th 2018, 3:03pm

Hello,

Thank you for your inquiry.
To make sure we understand you correctly. You want to program u-boot to the RAM of imx6ull using one of our tools?
U-boot is not our software so we can't provide any images for that.

But if you have an image already you can simply load it using J-Link Commander using the "loadfile" command.
More information about this can be found in the J-Link user manual in the J-Link install folder under /Doc

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/


nobody

Beginner

Date of registration: Mar 7th 2018

Posts: 2

3

Yesterday, 5:31pm

Hello Nino,

I have compiled u-boot. Running J-Link as I have shown in my first post is also not a problem.
My problem is, that I am not able to upload a file to the imx6ull.

Here is the output:

Source code

1
2
3
4
J-Link>loadfile /home/user/projekte/u-boot/u-boot-imx6/u-boot.srec 0x80000000
Downloading file [/home/user/projekte/u-boot/u-boot-imx6/u-boot.srec]...
Memory access: CPU temp. halted: https://wiki.segger.com/Memory_accesses#Stop_mode
O.K.


On the mentioned page: https://wiki.segger.com/Memory_accesses#Stop_mode I could not find any additional info.

I also got outputs like this

Source code

1
2
3
J-Link>loadfile /home/user/projekte/u-boot/u-boot-imx6/u-boot.srec 0x80000
Downloading file [/home/user/projekte/u-boot/u-boot-imx6/u-boot.srec]...
Writing target memory failed


I found the following page:
https://wiki.segger.com/index.php?title=I.MX6_SoloX_Support

If something like this could be provided for the imx6ull, I guess this would help.

Regards

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 931

4

Today, 9:35am

Hello,

Quoted

My problem is, that I am not able to upload a file to the imx6ull.

The first textbox shows the download succeeded.
The link to the wiki is only an information for the user that the CPU has been halted temporarily to enable programming.
The article is currently being worked on, that is why you don't find any information there. Sorry for this inconvenience.

We recommend halting the CPU manually before using loadfile for this device.
So your commands would be:
halt
loadfile...

Quoted

I found the following page:
https://wiki.segger.com/index.php?title=I.MX6_SoloX_Support

If something like this could be provided for the imx6ull, I guess this would help.


A QSPI Flash loader for the imx6ull is already available. But it has nothing to do with the issues you were seeing as the Flash loader is, as the name indicates, there to write to Flash and not RAM.

For best J-Link implementation, debugging and software project management we recommend using our IDE Embedded Studio for debugging: https://www.segger.com/products/developm…mbedded-studio/

Should you however want to stay with your current IDE environment we recommend debugging with our debug software Ozone that supports various compiler outputs and can be used for free with a J-Link Plus or higher: https://www.segger.com/products/developm…-link-debugger/

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/