LS1021A custom board bring-up

[winstonjacob]

Hi guys,

      I am using ls1021a custom board, here I configured a debug uart in RCW and DDR configuration for SD card boot, and I am are not getting the clock from the SD card while boot with sd card, any other configuration needed to boot the board.

Regards

Winston.

[ufedor]

Points to check:

1) SYSCLK has correct frequency, is present at the processor's pin(s) and is properly selected.

cfg_eng_use0 selects between SYSCLK (single ended) and DIFF_SYSCLK/DIFF_SYSCLK_B (differential) clock inputs - refer to the AN4878 - LS1021A Design Checklist, Table 8. LS1021A reset configuration signals, IFC_WE0_B.

2) PORESET_B is asserted for at least 1ms (after all power supplies are stable) - refer to the QorIQ LS1021A Data Sheet, Table 24. RESET initialization timing specifications.

3) TRST_B is pulsed low during POR - refer to the Design Checklist, Table 61. JTAG system-level checklist, Boundary-scan testing.

4) Use a digital scope to check POR levels of all configuration signals described in the Design Checklist, Table 8. LS1021A reset configuration signals to ensure, in particular, that RCW source is selected properly.

5) Use a digital scope to ensure that all signals with Note 5 in ht eQorIQ LS1021A Data Sheet, Table 1. Pinout list by bus are not pulled low during POR.

[winstonjacob]

Hi,

  Do we need to flash anything through codewarrior for fresh custom board to do SD boot?

Or can we directly boot the fresh custom board using SD card, given above hardware conditions are satisfied?

[ufedor]

> Do we need to flash anything through codewarrior for fresh custom board to do SD boot?

No.

[winstonjacob]

Our sd clock is not generated, so we are using Codewarrior to flash images to fresh custom ls1021a board (NOR), but the connection is not  establishing, we keep getting the error "Failed to correctly configure jtag chain", How can we verify the jtag connection is proper or not.

Thanks for your immediate reply @ufedor .

Regards

Winston

[ufedor]

1) Open a CCS window (C:\Freescale\CW4NET_v2020.06\Common\CCS\bin\ccs.exe)
2) Physical connection: USB to PC, JTAG to the customer board.
3) SW connection: in the ccs window type

source IDcode.tcl

4) Select CWTAP connection method and capture the test output.

[winstonjacob]

Hi,

Please find below CCS log after running loopback test.

(bin) 28 % source IDcode.tcl

Scanning for available TAPs connected via USB.....

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+ Available Remote Connections
+
+ 1 - CodeWarriorTAP - 00:04:9f:06:6d:ba
+ 2 - CodeWarriorTAP - <Specify IP Address>
+ 3 - GigabitTAP - <Specify IP Address>
+
+ x - Exit Script without Changes
+
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Specify connection:
1

Configuring TAP Interface....

Configured Connection: cwtap : 00:04:9f:06:6d:ba

TDO -----
|
|
TDI -----

###################################################
#
# configTAP - Redefine TAP interface
#
# scanboard - Scans the target system
# and returns the JTAG IDCode
#
# ir - Loopback test
#
###################################################

(bin) 29 % ir
0: 0x0000000000000000
1: 0x0000000000000000
2: 0x0000000000000000
3: 0x0000000000000000
4: 0x0000000000000000
5: 0x0000000000000000
6: 0x0000000000000000
7: 0x0000000000000000
8: 0x0000000000000000
9: 0x0000000000000000
10: 0x0000000000000000
11: 0x0000000000000000
12: 0x0000000000000000
13: 0x0000000000000000
14: 0x0000000000000000
15: 0x0000000000000000
16: 0x0000000000000000
17: 0x0000000000000000
18: 0x0000000000000000
19: 0x0000000000000000
20: 0x0000000000000000
21: 0x0000000000000000
22: 0x0000000000000000
23: 0x0000000000000000
24: 0x0000000000000000
25: 0x0000000000000000
26: 0x0000000000000000
27: 0x0000000000000000
28: 0x0000000000000000
29: 0x0000000000000000
30: 0x0000000000000000
31: 0x0000000000000000
32: 0x0000000000000000
33: 0x0000000000000000
34: 0x0000000000000000
35: 0x0000000000000000
36: 0x0000000000000000
37: 0x0000000000000000
38: 0x0000000000000000
39: 0x0000000000000000
40: 0x0000000000000000
41: 0x0000000000000000
42: 0x0000000000000000
43: 0x0000000000000000
44: 0x0000000000000000
45: 0x0000000000000000
46: 0x0000000000000000
47: 0x0000000000000000
48: 0x0000000000000000
49: 0x0000000000000000
50: 0x0000000000000000
51: 0x0000000000000000
52: 0x0000000000000000
53: 0x0000000000000000
54: 0x0000000000000000
55: 0x0000000000000000
56: 0x0000000000000000
57: 0x0000000000000000
58: 0x0000000000000000
59: 0x0000000000000000
(bin) 30 %

[ufedor]

> CCS log after running loopback test.

What do you mean by "loopback test"?

The IDcode.tcl has to be executed when processor is included into the JTAG chain.

[winstonjacob]

>What do you mean by "loopback test"?

after running source IDcode.tcl, I run ir command. That test returns 0. Can you check my log and tell me what else I can do?

[ufedor]

TDO -----
|
|
TDI -----

This means that the processor is not included into the JTAG chain - i.e. between TDI and TDO.

[winstonjacob]

Hi, now am getting that. IR loopback test returns non zero value. But all the values seems to be same. Is it expected. Am still getting Configure JTAG chain error only.

(bin) 67 % source IDcode.tcl

Scanning for available TAPs connected via USB.....

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+ Available Remote Connections
+
+ 1 - CodeWarriorTAP - 00:04:9f:06:6d:ba
+ 2 - CodeWarriorTAP - <Specify IP Address>
+ 3 - GigabitTAP - <Specify IP Address>
+
+ x - Exit Script without Changes
+
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Specify connection:
1

Configuring TAP Interface....

Configured Connection: cwtap : 00:04:9f:06:6d:ba

TDO -----
|
* Device 0 IDCODE: 5BA00477 Device: ARM DAP rev 5.x
* Device 1 IDCODE: 16B0001D Device: NXP LS1021A rev 2.x
|
TDI -----

###################################################
#
# configTAP - Redefine TAP interface
#
# scanboard - Scans the target system
# and returns the JTAG IDCode
#
# ir - Loopback test
#
###################################################

(bin) 68 % ir
0: 0xF2E8876543218081
1: 0xF2E88765432187F6
2: 0xF2E88765432187F6
3: 0xF2E88765432187F6
4: 0xF2E88765432187F6
5: 0xF2E88765432187F6
6: 0xF2E88765432187F6
7: 0xF2E88765432187F6
8: 0xF2E88765432187F6
9: 0xF2E88765432187F6
10: 0xF2E88765432187F6
11: 0xF2E88765432187F6
12: 0xF2E88765432187F6
13: 0xF2E88765432187F6
14: 0xF2E88765432187F6
15: 0xF2E88765432187F6
16: 0xF2E88765432187F6
17: 0xF2E88765432187F6
18: 0xF2E88765432187F6
19: 0xF2E88765432187F6
20: 0xF2E88765432187F6
21: 0xF2E88765432187F6
22: 0xF2E88765432187F6
23: 0xF2E88765432187F6
24: 0xF2E88765432187F6
25: 0xF2E88765432187F6
26: 0xF2E88765432187F6
27: 0xF2E88765432187F6
28: 0xF2E88765432187F6
29: 0xF2E88765432187F6
30: 0xF2E88765432187F6
31: 0xF2E88765432187F6
32: 0xF2E88765432187F6
33: 0xF2E88765432187F6
34: 0xF2E88765432187F6
35: 0xF2E88765432187F6
36: 0xF2E88765432187F6
37: 0xF2E88765432187F6
38: 0xF2E88765432187F6
39: 0xF2E88765432187F6
40: 0xF2E88765432187F6
41: 0xF2E88765432187F6
42: 0xF2E88765432187F6
43: 0xF2E88765432187F6
44: 0xF2E88765432187F6
45: 0xF2E88765432187F6
46: 0xF2E88765432187F6
47: 0xF2E88765432187F6
48: 0xF2E88765432187F6
49: 0xF2E88765432187F6
50: 0xF2E88765432187F6
51: 0xF2E88765432187F6
52: 0xF2E88765432187F6
53: 0xF2E88765432187F6
54: 0xF2E88765432187F6
55: 0xF2E88765432187F6
56: 0xF2E88765432187F6
57: 0xF2E88765432187F6
58: 0xF2E88765432187F6
59: 0xF2E88765432187F6
(bin) 69 %

[ufedor]

JTAG chain is correct now.

To program RCW into a fresh-new board it is required either:

1) select cfg_rcw_src configuration signals for a hard-coded option

or

2) use CodeWarrior RCW override technique referring CodeWarrior for ARMv7 Targeting Manual, 8.2 Using a JTAG configuration file to override RCW and attached screenshot.

[winstonjacob]

We already using this steps, and I attached the RCW file from JTAG chain, so please check that, and do we need to flash any thing in OCRAM, for custom board?

Thanks for your immediate reply.

Regards

Winston