[ABANDONED] MB9EF226 JFLASH CANT GET CONNECTION

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

  • [ABANDONED] MB9EF226 JFLASH CANT GET CONNECTION

    Hi!

    Could you help me to read this MCU.
    I use Flasher Pro XL.

    Source Code

    1. Connecting ...
    2. - Connecting via USB to probe/ programmer device 0
    3. - Probe/ Programmer firmware: J-Link / Flasher PRO V5 compiled Feb 14 2022 19:10:29
    4. - Device "MB9EF226" selected.
    5. - Target interface speed: 4000 kHz (Fixed)
    6. - VTarget = 4.913V
    7. - InitTarget() start
    8. - --- FSEU script --- InitTarget() from JLinkScript is executed
    9. - --- FSEU script --- MCU reset
    10. - TotalIRLen = 4, IRPrint = 0x01
    11. - JTAG chain detection found 1 devices:
    12. - #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    13. - --- FSEU script --- ERROR: Could not power up debug port (time-out reached)!
    14. - --- FSEU script --- OK: ARM JTAG-DP detected (JTAG IDCODE: 0x4ba00477)
    15. - --- FSEU script --- ERROR: Reading SCCFG_STAT2 caused the StickyError flag to be set!
    16. - --- FSEU script --- OK: MCU is unsecured
    17. - --- FSEU script --- ERROR: Core could not be halted (time-out reached)!
    18. - --- FSEU script --- ERROR: Watchdog configuration could not be changed!
    19. - --- FSEU script --- OK: System RAM wait cycles changed
    20. - InitTarget() end
    21. - TotalIRLen = 4, IRPrint = 0x01
    22. - JTAG chain detection found 1 devices:
    23. - #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    24. - DPv0 detected
    25. - Scanning AP map to find all available APs
    26. - AP[3]: Stopped AP scan as end of AP map has been reached
    27. - AP[0]: AHB-AP (IDR: 0x44770001)
    28. - AP[1]: APB-AP (IDR: 0x24770002)
    29. - AP[2]: JTAG-AP (IDR: 0x14760010)
    30. - Iterating through AP map to find APB-AP to use
    31. - AP[0]: Skipped. Not an APB-AP
    32. - AP[1]: APB-AP found
    33. - ROMTbl[0][0]: CompAddr: 80001000 CID: 00000000, PID: 00000000 ???
    34. - InitTarget() start
    35. - --- FSEU script --- InitTarget() from JLinkScript is executed
    36. - --- FSEU script --- MCU reset
    37. - --- FSEU script --- ERROR: Could not power up debug port (time-out reached)!
    38. - --- FSEU script --- OK: ARM JTAG-DP detected (JTAG IDCODE: 0x4ba00477)
    39. - --- FSEU script --- ERROR: Reading SCCFG_STAT2 caused the StickyError flag to be set!
    40. - --- FSEU script --- OK: MCU is unsecured
    41. - --- FSEU script --- ERROR: Core could not be halted (time-out reached)!
    42. - --- FSEU script --- ERROR: Watchdog configuration could not be changed!
    43. - --- FSEU script --- OK: System RAM wait cycles changed
    44. - InitTarget() end
    45. - TotalIRLen = 4, IRPrint = 0x01
    46. - JTAG chain detection found 1 devices:
    47. - #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    48. - ERROR: Cortex-A/R (connect): Could not determine address of core debug registers. Incorrect CoreSight ROM table in device?
    49. - ERROR: Failed to connect.
    50. Could not establish a connection to target.
    Display All

  • Hello,

    Thank you for your inquiry.
    It looks like either the device connection is not set up correctly, or the debug interface of your device is disabled to prevent connection.
    Could you check if all wires are correctly connected to J-Link? If yes, then most likely your device is locked and can't be accessed.
    For possible recoveries we recommend to contact the chip vendor support.

    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.