Cart New Account Login

HomeAbout usProductsSupportForumsBlogCustomer Service

Please accept the use of cookies on our site

At PEmicro we use web browser cookies in order to provide you with an enhanced experience and in order to be able to do things like shopping cart processing and identify you when you login to our website.

Click here to accept

search inside this forum
search inside all forums
PKG32Z-USB-UNIVERSAL-FX and EN360 Chip - Hardware Breakpoint
Nathan W. Nov 18, 2015 at 07:08 PM (19:08 hours)
Staff: Gerardo R.

  • Attempting to use ICD32Z to program external flash through the M68EN360 MCU to target CCA.

    Operating System: Win7 32-bit
    USB Multilink Universal FX Rev. B
    Firmware: Rev. C (downloaded from website but unable to prove good install)

    Subsequent to invoking macro, receiving the following message:
    "Waiting for keystroke or breakpoint ...
    Hardware breakpoint signal received from ICD cable."

    The same hardware setup works on another chip 683xx.

    The same macro will work when using the LPT interface on an Windows XP machine.


    • Other than the message being printed, is there anything wrong with your debug session?

  • The only other thing I noticed is that when invoking the macro, a keystroke is required to start running the macro after selecting the file, which I don't have to do on the Windows XP machine using the LPT interface.

  • I only ask because this is a known issue in the firmware and the message doesn't actually indicate a problem. What exactly does the macro intend to accomplish? Do you see "Waiting for keystroke or breakpoint" on the WinXP setup? My concern would be if the reason you have enter a key stroke is because you have to force halt the part.

  • I copied the macro below.  I do see "Waiting for keystroke or breakpoint ..." on the WinXP setup, but if I don't hit any key, it will finish loading the flash.  On the Win7 setup, I don't hit any key but it immediately comes up with the message "Hardware breakpoint signal received from ICD cable."

    Here is the script...


    DEBUGGER_DFC 7 ; DFC - Go to CPU space
    MM.L 0003FF00 10000001 ; MBAR - Set internal DPR base to 0x10000000
    DEBUGGER_DFC 5 ; DFC - Go to default space

    mm.l 10001000 00004cbf
    MM.L 10001040 00001200 ; GMR

    MM.B 10001022 07 ; SYPCR - Disable watchdog
    MM.W 10001016 0080 ; PEPAR - Enable WE and OE

    ; setup FLASH
    MM.L 10001054 FFF00004 ; OR0 - set flash size to 1MB (8 bits wide)
    MM.L 10001050 00000001 ; BR0 - set flash base to 0x00000000

    ; setup RAM
    MM.L 10001064 FFF00062 ; OR1 - set RAM size to 1MB (16 bits wide)
    MM.L 10001060 01000001 ; BR1 - set RAM base to 0x01000000

    ; setup CPLD
    MM.L 10001074 FFFE0002 ; OR2 - set CPLD size to 1K (16 bits wide)
    MM.L 10001070 02000001 ; BR2 - set CPLD base to 0x02000000

    ; Load the s19 file into SRAM. This will take about 2 minutes.
    LOAD fc360lcstest.s19

    ; Set the program counter to 01001008 to start the flash procedure
    PC 01001008

    ; Start flashing. This will take about 1 minute and stop automatically.
    ; When complete, the BDM will stop and display a message in D0. If the value
    ; in D0 = 600DF00D, the flash was successful. If the value in D0 = 8BADF00D,
    ; the flash failed.

  • This suggests that for some reason the part is going immediately into a halted state. Do you mind submitting a support request so we can look at this in more detail?

  • Thanks for your help.  I submitted a support request with the same title.

Add comment

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

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