MA35H0 Cannot find debug component in ROM Table

Follow

Yoon-Ki Hong

• May 27, 2024 10:51

hello.

This time, I want to use the MA35H0 series from Nuvoton, so I am writing a Support Package.

When I try to connect using CrossConnect Neo, the results are displayed as below.

Connecting 'CrossConnect for ARM' using '07000023'
DPIDR 0x6ba02477 DPv2
AXI-AP 0 0x44770004 
APB-AP 1 0x54770002 
AHB-AP 2 0x24770011 
Identifying
ROM Table 0xe0800000
CSCTI Rev 5 Base Address 0xe0801000
CSTSG Rev 1 Base Address 0xe0802000
Debug Component ID 0xb105900d Base Address 0xe0803000 Peripheral ID 0x04002bb909 4KB Count = 1 JEP 106 code = 0x4 0x3b RevAnd 0x0 Customer Modified 0x0 Rev 2 Part Number 0x909 Device ID 0x02 Device Type 0x22
TPIU Rev 5 Base Address 0xe0804000
CSETB Rev 4 Base Address 0xe0805000
CSTF Rev 3 Base Address 0xe0806000
ROM Table ID 0xb105100d Base Address 0xe0c00000 Peripheral ID 0x04003bb4aa 4KB Count = 1 JEP 106 code = 0x4 0x3b RevAnd 0x0 Customer Modified 0x0 Rev 3 Part Number 0x4aa Device ID 0x00 Device Type 0x00
ROM Table 0xe0c00000
Debug Component ID 0xb105900d Base Address 0xe0c10000 Peripheral ID 0x04003bbd04 4KB Count = 1 JEP 106 code = 0x4 0x3b RevAnd 0x0 Customer Modified 0x0 Rev 3 Part Number 0xd04 Device ID 0x03 Device Type 0x15
Debug Component ID 0xb105900d Base Address 0xe0c20000 Peripheral ID 0x04003bb9da 4KB Count = 1 JEP 106 code = 0x4 0x3b RevAnd 0x0 Customer Modified 0x0 Rev 3 Part Number 0x9da Device ID 0x00 Device Type 0x14
Debug Component ID 0xb105900d Base Address 0xe0c30000 Peripheral ID 0x04003bb9da 4KB Count = 1 JEP 106 code = 0x4 0x3b RevAnd 0x0 Customer Modified 0x0 Rev 3 Part Number 0x9da Device ID 0x00 Device Type 0x16
Debug Component ID 0xb105900d Base Address 0xe0c40000 Peripheral ID 0x04003bb9da 4KB Count = 1 JEP 106 code = 0x4 0x3b RevAnd 0x0 Customer Modified 0x0 Rev 3 Part Number 0x9da Device ID 0x00 Device Type 0x13
Debug Component ID 0xb105900d Base Address 0xe0d10000 Peripheral ID 0x04003bbd04 4KB Count = 1 JEP 106 code = 0x4 0x3b RevAnd 0x0 Customer Modified 0x0 Rev 3 Part Number 0xd04 Device ID 0x03 Device Type 0x15
Debug Component ID 0xb105900d Base Address 0xe0d20000 Peripheral ID 0x04003bb9da 4KB Count = 1 JEP 106 code = 0x4 0x3b RevAnd 0x0 Customer Modified 0x0 Rev 3 Part Number 0x9da Device ID 0x00 Device Type 0x14
Debug Component ID 0xb105900d Base Address 0xe0d30000 Peripheral ID 0x04003bb9da 4KB Count = 1 JEP 106 code = 0x4 0x3b RevAnd 0x0 Customer Modified 0x0 Rev 3 Part Number 0x9da Device ID 0x00 Device Type 0x16
Debug Component ID 0xb105900d Base Address 0xe0d40000 Peripheral ID 0x04003bb9da 4KB Count = 1 JEP 106 code = 0x4 0x3b RevAnd 0x0 Customer Modified 0x0 Rev 3 Part Number 0x9da Device ID 0x00 Device Type 0x13
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Skipping ROM Table Entry 0x00000010
Cannot find debug component in ROM Table

Is there anything I can refer to to resolve this error?

The Support Package I currently wrote is as follows.

https://github.com/mymy49/CrossworksForARM_MA35H0 

0

• 

  Michael Johnson

  • May 29, 2024 10:25

  I don't think we've seen a Cortex-A35 before - which board are you using?

  0

  Comment actions Permalink
• 

  Yoon-Ki Hong

  • May 29, 2024 14:32

  The board I use was purchased from the link below.

  https://direct.nuvoton.com/en/numaker-hmi-ma35h0-a1 

  0

  Comment actions Permalink
• 

  Michael Johnson

  • May 30, 2024 07:23

  I'll see if I can get a board to reproduce.

  0

  Comment actions Permalink
• 

  Yoon-Ki Hong

  • May 30, 2024 08:45

  Thank you very much!!

  0

  Comment actions Permalink
• 

  Michael Johnson

  • June 17, 2024 14:35

  I have a board, but don't see any life on the debug port. Do I need to set a jumper on the board?

  0

  Comment actions Permalink
• 

  Yoon-Ki Hong

  • June 18, 2024 00:24

  Yes. As shown in the image below, you must remove the jumpers on R44, R45, R46, R47, and R48, and attach jumpers on R368, R369, R370, R371, and R372.

  

  0

  Comment actions Permalink
• 

  Michael Johnson

  • June 18, 2024 15:40

  Did you do anything with J17?

  0

  Comment actions Permalink
• 

  Yoon-Ki Hong

  • June 20, 2024 00:05
  • Edited

  I did not change the J17 jumper settings.

  I was mistaken. 
  I checked again now and found that the jumper was put on J17. 
  Just reading your comment, this is my first time seeing J17? I thought and answered.

  0

  Comment actions Permalink
• 

  Michael Johnson

  • June 20, 2024 07:18

  Last night's build

  http://www.rowleydownload.co.uk/snapshots/arm_crossworks_v5_win_x64_setup.exe

  can identify the debug components of CA35.

  To use the debugger you'll need to find a way for the device to boot and not execute any code.

  Without sd-card inserted the debugger doesn't work (I suspect a boot loader is running) and when booted from the sd-card it can't see memory - probably due to the MMU being enabled

  0

  Comment actions Permalink
• 

  Yoon-Ki Hong

  • June 20, 2024 14:34

  Michael Johnson sir,

  Thank you very much~!

  I will try to find a way the device to boot and not execute any code. If found, I will write a comment.

  0

  Comment actions Permalink

Please sign in to leave a comment.