Cart New Account Login

HomeAbout usProductsSupportForumsBlogCustomer Service

search inside this forum
search inside all forums
PE universal FX HCS08 no BGND signal
Iko r. Aug 7, 2017 at 02:59 AM (02:59 hours)
Staff: Takao Y.

  • Hi.

    I'm working with an MC9S08DZxx on CodeWarrior 10.x (Eclipse IDE)
    I use old PE USB BDM Multilink without any issue.
    I have received an PE USB Universal FX device which seem to not work.

    There is no signal on BGND pin.

    My device is correctly identified by CodeWarrior:
    USB1: Multilink Universal FX Rev B (PEMCE1A9)

    I have update the firmware, but the result is the same.
    Could you help me to solve this issue?


    • Hi,
      i also try with CW 6.3.

      Fx device is correclty identified but the result is the same.

  • Greetings,

    First, make sure you read the quick start guide to get the latest resource CD for the multilink. The resource CD is found here:

    Use the firmware updater utility to change the firmware to support HCS08 architecture.

    Lastly, update your Codewarrior. Latest is CW10.7.

    Takao Yamada

  • Hi
    This is what i've done yesterday.

    Today, i've follow your instruction.

    1) I have re-install the driver using multilink_universal_install.exe from the link you provide to me.

    2) I launch the firmware update:
    architecture chossen is RS08/S08/S12(X)(Z)/ColdFire+/ColdFire V1
    firmware selection automatic: usbmlfxbdmens.0973
    update success

    The result is the same. no signal on BGDN pin with the FX.

  • I have also check the ribbon cable. There is no fault.

  • Greetings,

    What version of Codewarrior are you using? Did you try to update it? Go to the Help Menu -> Check for Updates.

    Takao Yamada

  • Hi 
    I was in CW 10.6.
    I have check and update only concern a "Discovery" module.
    I update it, and i lost the build process of my CW...

    I uninstall CW & all PE driver.
    I re-install CW 10.7 from NXP website: bluid and old PE work fine.
    I re-intall multilink_universal_install.exe.

    FX still doesn't work.

  • Greetings,

    Okay, next thing is to check hardware.

    First, disconnect any PEmicro hardware and power up your target board. Measure the voltage on BKGD, RESET, and VDD and report back your results.

    Then connect the PEmicro hardware to your computer and to the target board. Before you start using Codewarrior, measure the voltages on BKGD, RESET, and VDD again and see if anything changed. Report back your results.

    Takao Yamada

  • Hi
    here is the result:

    ->Board powered:
    - VDD: 5V
    - RST: 4.5V
    - BGND: 4.5V

    ->FX Plugged:
    - VDD: 5V
    - RST: 4.2V
    - BGND: 4.4V

    i used an oscilloscope to do measurement, and i saw clearly that there is absolutly no signal on BGND.

    In addition, the behavior on the RESET signal is not the same between PE MULTYLINK and PE Universal FX...

  • Greetings,

    The 4.5V is worrying when just the board is powered. VDD, Reset, and BKGD should all match.

    Could you check the schematic to see what could be the cause of the voltage drop? Do you have any current-limiting resistors on BKGD and RESET that may be preventing communication?

    Takao Yamada

  • Hi

    i'm working on production boards wich work perfertly with PE Multilink USB.

    i have re-checked. There's nothing on the board which could lead to block BKGD signals.

  • Greetings,

    Then how would you explain the drop in voltage in RESET and BKGD? There has to be a resistor in series on these 2 signals to cause the drop in voltage. Some kind of current-limiting resistor.

    Takao Yamada

  • Hi
    BKGD is directly connected to CPU Pin.
    RESET is connected to the CPU through a pull-up to Vcc resistor 10KOhms and a pull-down to GND Capasitor 100nF.

  • Greetings,

    Could you try something for me...Could you disconnect any external power and try using the power from the multilink FX. This means setting the jumper inside the multilink to be at 5V and within the codewarrior software modify the debug configurations to provide power to target. Doing so you should see the yellow LED on the multilink light up as you start the debug session. See if this improves your setup.

    Takao Yamada

  • Greetings,

    Any update on this?

    Takao Yamada

  • Hi

    I have try what you say whithout any results.
    My final test was to change the ribbon.

    Now it work perfecctly!!!

    Solution: Change the ribbon.

    It should be baddly producted.

    This is a basic test that i should think about :/

    Thank you for your support.

Add comment

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

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