PXS3020 debug, password required

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

PXS3020 debug, password required

Jump to solution
1,095 Views
Phil_D1
Contributor III

Hello,

 

    I am using CodeWarrior for MCU, Version: 10.2, Build Id:120126. I have a P&E Micro Multilink Universal FX, drivers installed from packaged installation CD.

 

    I created a new bareboard project and set the connection type to P&E USB Multilink Universal. When I try to debug or program flash on my PXS3020 target, I get a window titled "Password Required" and which reads "Device may be censored. Please enter password (in hex) to uncensor:" However, when I use a P&E Cyclone Max, I am able to debug just fine--no error message. And YES, I am absolutely sure that I am setting the debugger to Multilink when I use the Multilink. I've tried swapping out the Multilink for another, swapped the target board for another and have done this on a different PC, all with the same result.

 

Any ideas?

Labels (1)
0 Kudos
1 Solution
699 Views
Phil_D1
Contributor III

Turns out that it was a problem with my early rev of target hardware. Supplying +5V at the JTAG header (oops, should have been 3.3V), while the reset line was only being pulled up to 3.3V caused problems in the MultiLink Universal-FX, but the Cyclone Max was okay with it.

View solution in original post

0 Kudos
3 Replies
699 Views
J2MEJediMaster
Specialist I

Just an idea, mind you...

 

Since the older probe works and the newer one does not, that leads me to believe that the problem lies in the probe and not the CodeWarrior installation. That and the fact that the problem moves with the probe and not the board. I would suggest the following:

 

1) Go to the P&E Microsystems site (www.pemicro.com) and download the latest drivers. Then update the drivers on the system.

2) There might actually be something wrong with the probe. If 1) doesn't work, I would recommend contacting P&E Microsystems support as to this possibility. They'll probably ask you to update the drivers first, so you might as well get that out of the way before you do.

 

---Tom

0 Kudos
699 Views
Phil_D1
Contributor III

Thanks. I agree, this does sound like a P&E problem. Since I am running the latest driver, I put a support request in with P&E. I will update this thread with the outcome.

 

Phil

0 Kudos
700 Views
Phil_D1
Contributor III

Turns out that it was a problem with my early rev of target hardware. Supplying +5V at the JTAG header (oops, should have been 3.3V), while the reset line was only being pulled up to 3.3V caused problems in the MultiLink Universal-FX, but the Cyclone Max was okay with it.

0 Kudos