[ABANDONED] MPC5606b can't be halted?

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

  • [ABANDONED] MPC5606b can't be halted?

    I'm using a mpc5606b where is possible to read the cpu id but when i read the flash (it is unprotected) , the processor cant be halted. I tried different reset type but no way to stop it after the reset.
  • Hello,

    Thank you for your inquiry.
    The MPC5606b seems to be a PowerPC e200z0 core.
    On our webpage you can find an overview of supported coretypes and target devices: segger.com/products/debug-prob…pported-cpus-and-devices/


    PowerPC is currently not supported and due to low demand there are currently no plans to add it.

    So we can't provide you with any information here. If connection is somehow working it is most likely just luck.


    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.
  • Thanks for the replay.

    I seen the support this chip here segger.com/downloads/supported…hp?model=flasher-portable . Also it is present on the document of jlink 633g "ReleaseNotes_JLink.html" (should be included a file "MPC5606B.jflash" but it is missing).

    Anyway I tried to read the internal flash but if the processor is not in halt state, your program stop after a while.


    At this point, is this MPC5606b supported or not?
  • Hello,

    the PowerPC architecture is only "partially" supported, but you should be
    able to connect to the processor, halt it and then read memory.

    We just gave it a quick try:

    Source Code

    1. SEGGER J-Link Commander V6.32g (Compiled Jun 15 2018 17:26:48)
    2. DLL version V6.32g, compiled Jun 15 2018 17:26:15
    3. Connecting to J-Link via USB...O.K.
    4. Firmware: J-Link Ultra V4 compiled Apr 20 2018 16:46:34
    5. Hardware version: V4.00
    6. S/N: 504302944
    7. License(s): RDI, FlashBP, FlashDL, JFlash, GDB
    8. VTref=4.572V
    9. Type "connect" to establish a target connection, '?' for help
    10. J-Link>con
    11. Please specify device / core. <Default>: MPC5606B
    12. Type '?' for selection dialog
    13. Device>
    14. Please specify target interface:
    15. J) JTAG (Default)
    16. TIF>
    17. Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
    18. JTAGConf>
    19. Specify target interface speed [kHz]. <Default>: 4000 kHz
    20. Speed>
    21. Device "MPC5606B" selected.
    22. Connecting to target via JTAG
    23. TotalIRLen = 10, IRPrint = 0x0209
    24. JTAG chain detection found 1 devices:
    25. #0 Id: 0x07E0E01D, IRLen: 10, PowerPC OnCE-TAP
    26. PowerPC (Nexus 1) identified.
    27. J-Link>h
    28. R0 = 00000000, R1 = 400000BC, R2 = 40018000, R3 = 00000000
    29. R4 = 00000000, R5 = 00000001, R6 = 0036A230, R7 = C3FDC001
    30. R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 400000FC
    31. R12= 00000000, R13= 40018000, R14= 00000000, R15= 00000000
    32. R16= 00000000, R17= 00000000, R18= 00000000, R19= 00000000
    33. R20= 00000000, R21= 00000000, R22= 00000000, R23= 00000000
    34. R24= 00000000, R25= 00000000, R26= 00000000, R27= 00000000
    35. R28= 00000000, R29= 00000000, R30= 00000000, R31= 00000000
    36. CR = 20000000, CTR= 00000000, LR = 00000000, XER= 00000000
    37. PC = 00000004
    38. PVR =817F0000, PIR =00000000, SVR =00000000
    39. MSR =00000000, HID0 =00000000, HID1 =00000000
    40. SPRG0 =B428000C, SPRG1 =20441900, SRR0 =6200AA00, SRR1 =10A82250
    41. CSRR0 =04100401, CSRR1 =449C0311, DSRR0 =00584171, DSRR1 =57010010
    42. ESR =00000000, MCSR =00000000, DEAR =01841488, IVPR =00000000
    43. PID0 =00000000, MMUCFG=00000003, L1CFG0=00000000, BUCSR =00000000
    44. DBCR0 =80000000, DBCR1 =00000000, DBCR2 =00000000, DBSR =00000000
    45. IAC1 =00000000, IAC2 =00000000, IAC3 =00000000, IAC4 =00000000
    46. DAC1 =00000000, DAC2 =00000000
    47. J-Link>mem 0 128
    48. 00000000 = 48 06 20 07 20 06 E8 FF 00 00 00 02 00 00 00 03
    49. 00000010 = 00 00 00 04 00 00 00 05 00 00 00 06 00 00 00 07
    50. 00000020 = 00 00 00 08 00 00 00 09 00 00 00 0A 00 00 00 0B
    51. 00000030 = 00 00 00 0C 00 00 00 0D 00 00 00 0E 00 00 00 0F
    52. 00000040 = 00 00 00 10 00 00 00 11 00 00 00 12 00 00 00 13
    53. 00000050 = 00 00 00 14 00 00 00 15 00 00 00 16 00 00 00 17
    54. 00000060 = 00 00 00 18 00 00 00 19 00 00 00 1A 00 00 00 1B
    55. 00000070 = 00 00 00 1C 00 00 00 1D 00 00 00 1E 00 00 00 1F
    56. 00000080 = 00 00 00 20 00 00 00 21 00 00 00 22 00 00 00 23
    57. 00000090 = 00 00 00 24 00 00 00 25 00 00 00 26 00 00 00 27
    58. 000000A0 = 00 00 00 28 00 00 00 29 00 00 00 2A 00 00 00 2B
    59. 000000B0 = 00 00 00 2C 00 00 00 2D 00 00 00 2E 00 00 00 2F
    60. 000000C0 = 00 00 00 30 00 00 00 31 00 00 00 32 00 00 00 33
    61. 000000D0 = 00 00 00 34 00 00 00 35 00 00 00 36 00 00 00 37
    62. 000000E0 = 00 00 00 38 00 00 00 39 00 00 00 3A 00 00 00 3B
    63. 000000F0 = 00 00 00 3C 00 00 00 3D 00 00 00 3E 00 00 00 3F
    64. 00000100 = 00 00 00 40 00 00 00 41 00 00 00 42 00 00 00 43
    65. 00000110 = 00 00 00 44 00 00 00 45 00 00 00 46 00 00 00 47
    66. 00000120 = 00 00 00 48 00 00 00 49
    67. J-Link>
    Display All

    Could you please give us more (detailed) information about your setup?

    Best regards
    Arne
    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.
  • I did more test.

    During all my the test, the cpu appears to be not halted - the internal program is in execution because it print some log on the serial port and I can the traffic.

    With the commander, I have the same results of your example. When I read some memory it dumps the content.

    I tried again with the flasher to read the entire chip/sector and it gives me some error (look below) but if I read only a range of memory it works.


    I'll continue with dumping manual ranges. Thanks



    Source Code

    1. Application log started
    2. - J-Flash V6.33f (J-Flash compiled Jun 13 2018 17:11:57)
    3. - JLinkARM.dll V6.33f (DLL compiled Jun 13 2018 17:11:37)
    4. Opening project file [C:\Users\] ...
    5. - Project opened successfully
    6. Failed to open data file [C:\Users]...
    7. Reading target memory (0x0000A000 - 0x0000B000) ...
    8. - Connecting ...
    9. - Connected successfully
    10. - Start of preparing flash programming
    11. - End of preparing flash programming
    12. - Blank checking 0x0000A000 - 0x0000B003
    13. - Start of restoring
    14. - End of restoring
    15. - Target memory read successfully. (4100 bytes, 1 range) - Completed after 0.409 sec
    16. Reading entire flash chip ...
    17. - 14 sectors, 2 ranges, 0x0 - 0xBFFFF, 0x800000 - 0x80FFFF
    18. - Start of preparing flash programming
    19. - ERROR: Verification of RAMCode failed @ address 0x40000080.
    20. Write: 0x2118EEE8 0078F806
    21. Read: 0x00E03471 F05A291D
    22. - ERROR: Failed to prepare for programming.
    23. Failed to download RAMCode!
    24. - End of preparing flash programming
    25. - ERROR: Failed to read back target memory
    26. Disconnecting ...
    27. - Disconnected
    28. Reading entire flash chip ...
    29. - Connecting ...
    30. - Connected successfully
    31. - 14 sectors, 2 ranges, 0x0 - 0xBFFFF, 0x800000 - 0x80FFFF
    32. - Start of preparing flash programming
    33. - End of preparing flash programming
    34. - Blank checking 0x00000000 - 0x0001FFFF
    35. - Blank checking 0x00028000 - 0x00047FFF
    36. - Start of restoring
    37. - ERROR: CPU is not halted
    38. - End of restoring
    39. - ERROR: Failed to read back target memory
    40. Disconnecting ...
    41. - Disconnected
    42. Reading selected sectors ...
    43. - Connecting ...
    44. - Connected successfully
    45. - 14 of 14 sectors selected, 2 ranges, 0x0 - 0xBFFFF, 0x800000 - 0x80FFFF
    46. - Start of preparing flash programming
    47. - End of preparing flash programming
    48. - Blank checking 0x00000000 - 0x0001FFFF
    49. - Blank checking 0x00028000 - 0x00047FFF
    50. - Blank checking 0x00048000 - 0x00067FFF
    51. - ERROR: CPU is not halted
    52. - ERROR: ü-a|0c
    53. - ERROR: Error while blank checking.
    54. - Start of restoring
    55. - ERROR: PC of target system has unexpected value after restoring target. (PC = 0x40000010, MSR = 0x00000000)!
    56. - End of restoring
    57. - ERROR: Failed to read back target memory
    58. Disconnecting ...
    59. - Disconnected
    Display All
  • Thanks for the information. J-Flash does an additional blank check before reading memory, because that is much faster, if a sector is completely erased.

    Is the log output in J-Flash always exactly the same? Did you already try to reduce the target interface speed?
    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.
  • We could not reproduce any problems here, J-Flash is working stable and reliable with our evaluation board.

    Are you using an evaluation board too or custom hardware?
    If custom hardware, can you try with an evaluation board?

    Which debug probe do you use?

    Best regards
    Arne
    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.