[SOLVED] Mediatek 6765 board (Cortex A53): "Could not power-up system power domain."

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Mediatek 6765 board (Cortex A53): "Could not power-up system power domain."

    Dear all,

    Would be grateful to get some insight on this. I'm trying to connect to the development board based on MTK (8xCortex A53) with J-Link EDU V11, getting the following output:

    Source Code

    1. SEGGER J-Link Commander V6.54 (Compiled Oct 28 2019 10:34:47)
    2. DLL version V6.54, compiled Oct 28 2019 10:34:34
    4. Connecting to J-Link via USB...O.K.
    5. Firmware: J-Link V11 compiled Aug 14 2019 16:21:09
    6. Hardware version: V11.00
    7. S/N: 261000881
    8. License(s): FlashBP, GDB
    9. OEM: SEGGER-EDU
    10. VTref=1.806V
    13. Type "connect" to establish a target connection, '?' for help
    14. J-Link>connect
    15. Please specify device / core. <Default>: CORTEX-A53
    16. Type '?' for selection dialog
    17. Device>CORTEX-A53
    18. Please specify target interface:
    19. J) JTAG (Default)
    20. S) SWD
    21. T) cJTAG
    22. TIF>J
    23. Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
    24. JTAGConf>
    25. Specify target interface speed [kHz]. <Default>: 4000 kHz
    26. Speed>
    27. Device "CORTEX-A53" selected.
    30. Connecting to target via JTAG
    31. TotalIRLen = 4, IRPrint = 0x01
    32. JTAG chain detection found 1 devices:
    33. #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    34. DAP: Could not power-up system power domain.
    35. Scanning AP map
    36. AP scan stopped (IDR reports 0, end of AP map reached)
    37. TotalIRLen = 4, IRPrint = 0x01
    38. JTAG chain detection found 1 devices:
    39. #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    40. DAP: Could not power-up system power domain.
    41. Scanning AP map
    42. AP scan stopped (IDR reports 0, end of AP map reached)
    44. ****** Error: Could not determine APB-AP (debugging not possible)
    46. TotalIRLen = 4, IRPrint = 0x01
    47. JTAG chain detection found 1 devices:
    48. #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    49. DAP: Could not power-up system power domain.
    50. Scanning AP map
    51. AP scan stopped (IDR reports 0, end of AP map reached)
    52. TotalIRLen = 4, IRPrint = 0x01
    53. JTAG chain detection found 1 devices:
    54. #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    55. DAP: Could not power-up system power domain.
    56. Scanning AP map
    57. AP scan stopped (IDR reports 0, end of AP map reached)
    59. ****** Error: Could not determine APB-AP (debugging not possible)
    Display All



    Thanks in advance!

  • Hello,

    Thank you for your inquiry.
    The Mediatek 6765 is currently not supported by J-Link:
    segger.com/downloads/supported-devices.php

    As such chips are usually not designed to be debugged by a external debug probe but rather to have a Linux running on top of it there are currently no plans to add support for this particular device.
    However you can try to add support yourself. I assume that the error message comes from some targetspecific init steps needed before the core can be accessed.
    This can be done via JLinkScript files for example. How to use and create one is explained in the J-Link user guide UM08001.

    Please understand that we can't provide support in the creation of such a script file.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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 you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • SEGGER - Nino wrote:

    Hello,

    Thank you for your inquiry.
    The Mediatek 6765 is currently not supported by J-Link:
    segger.com/downloads/supported-devices.php

    As such chips are usually not designed to be debugged by a external debug probe but rather to have a Linux running on top of it there are currently no plans to add support for this particular device.
    However you can try to add support yourself. I assume that the error message comes from some targetspecific init steps needed before the core can be accessed.
    This can be done via JLinkScript files for example. How to use and create one is explained in the J-Link user guide UM08001.

    Please understand that we can't provide support in the creation of such a script file.

    Best regards,
    Nino
    Thanks, that's all I wanted to know. Will look into JLinkScript documentation!