cancel
Showing results for 
Search instead for 
Did you mean: 

PSoC 5, 3 & 1 MCU

New Contributor II

Creator 3.3 works great with my MiniProg3.

Creator 4.2 builds well, but won't program the target.  ctrl F5 hangs Creator until I disconnect the USB from the MiniProg3.  I can program the hex file using Programmer 3.28.1.

I'd stick with Creator 3.3, but there's no direct interrupt support for Status Registers in UDB documents.

All this is under Windows 7.

0 Likes
Reply
1 Solution
New Contributor II

Problem solved!

base on a recommdation from another post I downloaded:

      USBDeview v2.80 (c) 2006-2019 from www.nirsoft.net

In there I found that I had five installations of my MiniProg3.  Don't know why that wasn't a problem for Programmer 3.28.1 or Creator 3.3sp2.  My company doesn't let us run as administrators, so I had to get an admin to run Deview under her credentials.  With the proper credentials, I tried many things, without success.  I think this was the successful sequence , but I wouldn't bet my life on it:

  • Pulled the USB from the MiniPorg3
  • Closed all PSoC applications
  • Uninstalled all MiniProg3 installations with USBDeview
  • Pushed the USB into the MiniProg3
  • Launched Programmer, programmed, and closed Programmer.
  • Launched Creator 4.2, couldn't attach.
  • Pulled/pushed the USB<>MiniProg3
  • Menu>Debug>(Select Target and Program)
  • Yippee!

View solution in original post

0 Likes
Reply
7 Replies
Moderator
Moderator

Hi Jim,

Could you go to Main menu->Debug->Select Debug Target and check if debugger configuration matches your hardware?

pastedImage_0.png

Thanks,

Ryan

0 Likes
Reply
New Contributor II

Thanks Ryan!

Main menu->Debug->Select Debug Target causes Creator to hang.  If I pull the USB to the MiniProg3 twice, Creator comes back to life.  To be precise in my reply, I decided to leave Creator hanging.  It turns out that I just wasn't patient enough.  The dialog box you showed comes up after about 105 sec. Clicking on any of the buttons or pulling down a menu all take a similar amount of time to resolve.  After 15 minutes of calming exercises...

My new settings are:

Active Protocol  =  SWD

Clock Speed      = 0.8 MHz

Power                = 3.3V      (changed from 10 pin)

Acquire Mode    = Reset    (changed from  Power Cycle)

Connector         = 5 pin      (changed from 10 pin)

Now it only takes 10-15 sec to present dialog boxes or accept selections.  Using Creator 3.3SP2, this is just about instant.  Even after all the waiting, it never works.  Eventually it gives me "Warning: dbg.M0039".  I went back to Programmer 3.28.1, and that wouldn't work anymore until I pulled/reconnected the USB to the MiniProg3.  After USB reconnect Programmer worked fine.  Returning to Creator 4.2, no joy.   Pulled/reconnected the USB to the MiniProg3, still no joy.

pastedImage_6.png

0 Likes
Reply
Esteemed Contributor

Hi,

May be your MiniProg3 has older version of firmware.

When you started PSoC Programmer,

003-Firmware-version.JPG

Around the red-box above, you may see MiniProg3 version x.xx expected y.yy  or something like that.

Then it means the firmware version of MiniProg3 is not up to date.

To Upgrade the firmware, select "Utilities" tab in the PSoC Programmer

then select "Upgrade Firmware"

004-Upgrade-Firmware.JPG

moto

0 Likes
Reply
New Contributor II

Thanks Motoo!

My firmware is up-to-date with MiniProg3: 2.05

0 Likes
Reply
New Contributor II

New information

On an old laptop Creator 4.2 programs fine. 

On the problem workstation, Creator 4.2 tries to program, but doesn't hold reset on the target.  The PSoC target resets several times a second, never long enough to acquire or program.  I can see the target executing a quick LED sequence from old code, but never getting to far.

Programming from Programmer 3.28.1, the old code LED goes off and stays off until the part is programmed.

0 Likes
Reply
Esteemed Contributor

Hi,

That seems to be very important information!

What I can imagine from it

(1) Inappropriate setting

From the dialog picture you paste

(1.1) Voltage(ADC) = 3.38 V

What is the VDD voltage of your board? (1.8, 3.3 or 5V?)

and is it provided from MiniProg3 or other external power supply?

If the power is provided from other power supply,

you should check External in the Power pane (of Select Debug Target Dialog)

Or you need to specify the VDD voltage.

In my experience, there was a time when MiniProg3 could not

provide enough power to the board and program and debug was not stable.

So maybe you want to add an external power supply for more stable operation.

(1.2) Frequency = 800KHz

I don't think this is a strange value, but reading your description,

maybe trying to make it lower and/or higher affect the situation.

(2) USB Driver for MiniProg3 may be corrupted

Since you are able to read the statics of MiniProg3, this is less likely the case,

but trying below may work.

(2.1) Remove driver for MiniProg3 from Windows Device Manager

(2.2) Reinstall MiniProg3 USB driver from PSoC Creator 4.2 installer

moto

0 Likes
Reply
New Contributor II

Problem solved!

base on a recommdation from another post I downloaded:

      USBDeview v2.80 (c) 2006-2019 from www.nirsoft.net

In there I found that I had five installations of my MiniProg3.  Don't know why that wasn't a problem for Programmer 3.28.1 or Creator 3.3sp2.  My company doesn't let us run as administrators, so I had to get an admin to run Deview under her credentials.  With the proper credentials, I tried many things, without success.  I think this was the successful sequence , but I wouldn't bet my life on it:

  • Pulled the USB from the MiniPorg3
  • Closed all PSoC applications
  • Uninstalled all MiniProg3 installations with USBDeview
  • Pushed the USB into the MiniProg3
  • Launched Programmer, programmed, and closed Programmer.
  • Launched Creator 4.2, couldn't attach.
  • Pulled/pushed the USB<>MiniProg3
  • Menu>Debug>(Select Target and Program)
  • Yippee!

View solution in original post

0 Likes
Reply