iMX6 DS-5

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

iMX6 DS-5

1,789 次查看
davidpatton
Contributor III

Working on a new board with an iMX6, my responsibilites lie on the ARM A9 side. I have an ARM DS-5, that I am trying to get to connect via JTAG; Windows sees the debugger via USB, the DS-5 recognizes the presence of a target via JTAG, but in trying to set the platform, neither Freescale nor NXP have an iMX6 listed; if I try to use "Auto Configure" it fails with the PCE Console output attached...I am assuming, since the iMX6 is not a brand new processor, there is some type of existing extension I need to load to get iMX6 support?

 

Thanks!

Original Attachment has been moved to: ds-5-autodetect.txt.zip

标签 (1)
0 项奖励
回复
4 回复数

1,316 次查看
davidpatton
Contributor III

I've also opened a case with ARM, when they get it resolved I will post the answer...thanks guys!

0 项奖励
回复

1,316 次查看
chrismartin
Contributor I

Hi David, 

The v5.27.1 install of DS-5 does include several i.MX6 debug configurations pre-installed (see below) that likely did not exist in the v5.21 version.  One of these configurations may also work, especially if you are using one of these boards (such as the i.Mx6 SoloLite or SoloX Sabre SDB) and since you now have installed this version. 

pastedImage_1.png

This may allow you to get around having to use the platform configuration editor to auto-detect the platform. 

Regards,

Chris Martin

0 项奖励
回复

1,316 次查看
igorpadykov
NXP Employee
NXP Employee

Hi David

please refer to sect.Chapter 7 Configuring JTAG Tools

attached document, check that signal JTAG_MOD=0.

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 项奖励
回复

1,316 次查看
davidpatton
Contributor III

Update: the installation DVD installed 5.21.1 and did an upgrade on the firmware, I assumed to the latest, after getting an error that the firmware was not the latest, I installed 5.27.1 and upgraded the firmware to match, autodetect now appears to get further along, but still ends in error

[03/10/17 16:35:17] ARM DS-5 v5.27.1, build number 5271024
[03/10/17 16:35:17] Beginning Autodetection
[03/10/17 16:35:19] --- --- ---
[03/10/17 16:35:19] Counting devices:
[03/10/17 16:35:19] DR Chain [64]:
[03/10/17 16:35:19] [1111111111111111111111111111111111111111111111111111111111110000]
[03/10/17 16:35:19] Device Count: 4
[03/10/17 16:35:19] The total IR length of the scanchain measured as 17
[03/10/17 16:35:19] Reading IDCODEs:
[03/10/17 16:35:19] DR Chain [128]:
[03/10/17 16:35:19] [00000000000000000000000000000000000100010010001110000000001110100100101110100000000001000111011101001011101000000000010001110111]
[03/10/17 16:35:19] Device 0 has IDCODE = 0x0891C01D
[03/10/17 16:35:19] Device 1 has no IDCODE
[03/10/17 16:35:19] Device 2 has IDCODE = 0x4BA00477
[03/10/17 16:35:19] Device 3 has IDCODE = 0x4BA00477
[03/10/17 16:35:19] IR Chain [1024]:
[03/10/17 16:35:19] [11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111100001000000010001]
[03/10/17 16:35:19] Device 0 detected IR Length = 1
[03/10/17 16:35:19] Device 1 detected IR Length = 5
[03/10/17 16:35:19] Device 2 detected IR Length = 8
[03/10/17 16:35:19] Device 3 detected IR Length = 4
[03/10/17 16:35:19]
The measured device IR lengths do not match the total scanchain length.
An attempt will be made to correctly identify scanchain devices, but in the case of failure,
the scanchain should be configured manually.

[03/10/17 16:35:19]
The following scanchain will be used:
[03/10/17 16:35:19] JTAGDeviceInfo[IDCODE = 0x0891C01D, IR Length = 5, Name = UNKNOWN_5]
[03/10/17 16:35:19] JTAGDeviceInfo[IDCODE = 0x00000000, IR Length = 4, Name = UNKNOWN_4]
[03/10/17 16:35:19] JTAGDeviceInfo[IDCODE = 0x4BA00477, IR Length = 4, Name = UNKNOWN_4]
[03/10/17 16:35:19] JTAGDeviceInfo[IDCODE = 0x4BA00477, IR Length = 4, Name = UNKNOWN_4]
[03/10/17 16:35:19]

[03/10/17 16:35:20] Autodetection Complete
[03/10/17 16:35:50] Platform 'GE - Nebula' did not build successfully: NO_CORES_FOUND

0 项奖励
回复