Cart New Account Login

HomeAbout usProductsSupportForumsBlogCustomer Service

search inside this forum
search inside all forums
I have connected Multilink UnivarsalFX to MPC5604B, but progppcnexus does not recognize it
Yukihiro H. May 31, 2020 at 11:22 AM (11:22 hours)
Staff: Takao Y.

  • Multilink Univarsal FX was connected to MPC5604B.
    I started progppcnexus.
    PEMICRO Connection Manager's Debug Shift Speed ​​selected the slowest number 31.
    Then I clicked Connect.
    I have selected NXP_MPC5604B_1x32x128k_CFlash.pcp.
    However, the Status Window displays Error Loading .pcp file: C: / ******.
    At this time, the TGTPWR and USB LEDs are lit.
    I do not know the cause.
    if you'd kindly teach me. Please.




    Comments

  • Greetings,

    YOu need to check for a system bus chip or external watchdog that is probably interrupting communication. Check RESET line with an oscilloscope and you will probably see it toggling often and consistently. You need to figure out how to disable it on your own.


    Takao

    • Greetings, Mr.Takao

      This message when reading the PCP file of MPC5604B is as follows.
      Please confirm.

      ------------------------------------------------------------------------------------

      Initializing. - Device IDCODE is $00000241 Device ID revision is $00000004 Initializing Ram Block 0x40000000-0x40007FFF. MPC560xx Device detected. Initialized. version 1.02, 12/08/2016, Copyright P&E Microcomputer Systems, www.pemicro.com (560X_16k_dflash_test_sector) device NXP, MPC5604B, 1x32x4k, desc-Dflash_Test_Sector begin as device=$00000000, length=$00004000, ram=$40000000 Loading programming algorithm ... Error loading .PCP file : C:\PEMicro\PROGPPCNEXUS\Algorithms NXP MPC5604B_1x32x4k Dflash_Test_Sector.pop at address 400001c1
      Error loading .PCP file : C:\PEMicro\PROGPPCNEXUS\Algorithms NXP MPC5604B 1x32x4k Dflash Test Sector.pop at address 400001c1 Selected command is not active for this module. Initializing. - Device IDCODE is $00000241 Device ID revision is $00000004 Initializing Ram Block Ox 40000000-0x40007FFF. MPC560xx Device detected.
      Initialized. version 1.15, 03/30/2017, Copyright P&E Microcomputer Systems, www.pemicro.com (560x_256k cflash 64k_dflash) ;device NXP, MPC5602b, Cflash_Dflash ;begin os device-$00000000, length=$00810000, ram-$40000000 Loading programming algorithm ... Error loading .PCP file : C:\PEMicro\PROGPPCNEXUS\Algorithms NXP MPC5602b_cflash_Dflash.pcp at address 40000374
      Error loading .PCP file : C:\PEMicro\PROGPPCNEXUS\Algorithms\NXP_MPC5602b_Cflash Dflash.pcp at address 40000374

      ------------------------------------------------------------------------------------

  • Greetings, Mr.Takao

    Thank you for your reply.

    When I checked RESET on the oscilloscope, I could confirm that it was Lo once every about 100ms.
    However, I thought this behavior was a ""Startup Reset Sequence".
    Should RESET always be Lo?
    Why does it often toggle? I also don't know why and how to disable it.

    ###Excerpt from the manual###

    7 Troubleshooting - Startup Reset Sequence
    Note that if the Multilink does not enter debug mode, the program issues the error message “Cannot enter background mode.” If
    you receive this message you should check your hardware with a scope, logic analyzer or logic probe. First check for power on,
    then check to make sure the processor oscillator is running. Finally, look for the startup sequence for your microprocessor that
    is listed below.
    Port A – JTAG/ONCE – MPC55xx-57xx & STMicroelectronics SPC5, DSC, S32 (Power)
    a. RESET (Pin-9) is driven low (to processor).
    b. Activity appears on TCK (Pin-5), TDI (Pin-1) and TDO (Pin-3). (PC software instructs the processor to enable debug
    mode).
    c. RESET (Pin-9) is released by the interface and will go high.
    d. Activity appears on TCK (Pin-5), TDI (Pin-1) and TDO (Pin-3). (Debug activity).

    Yukihiro.H

  • Greetings,

    If RESET line is toggling more than 2 times and always repeating with same pattern, then it is a watchdog from a system bus chip or external watchdog. You need to disable it or the PEmicro hardware cannot function. You will need to check the schematic of the board to disable it. I cannot help you there.


    Takao

Add comment


   Want to comment? Please login or create a new PEmicro account.







© 2021 P&E Microcomputer Systems Inc.
Website Terms of Use and Sales Agreement