M52233DEMO: Can't connect to PEMicro USB

[okalex]

Hello all,

I had my M52233DEMO working fine and was able to run code in RAM and ROM. Using CF Flasher, I was programming an s19 file with the "Verify after program" setting enabled. The programming stage completed fine, but when it came time to verify, I received an error message saying "Error: BDM established, but cannot write D0". I tried reprogramming the device to no avail. After trying everything with CF Flasher, I tried using the flash programmer within CodeWarrior, but I'm not even able to connect to the BDM (I get an error message saying "PEMicroProtocolPlugin: Can't connect to PEMicro via USB". I'm also unable to communicate with the BDM using gdb.

I didn't change any settings or jumpers between when the BDM worked and when it didn't work. The BDM_EN jumper is installed, the board is receiving power and when I plug and unplug the BDM, I hear the 'bedoop' sound Windows makes when a USB device is plugged in, so it seems to be communicating with Windows fine. To be sure, I reinstalled the drivers, and that didn't work either.

What could have happened to my BDM? Is there anything I can do to rescue it? Just as I was starting to be satisfied with myself for getting everything working (CodeSourcery, Eclipse, GDB, etc.), this happened and now I'm lost. Please help.

Thanks,
Alex P.

[mcp]

Just ran into a similar problem.  I have several M52235EVB boards and,
having such good luck getting the uTasker server software running on them,
attempted to do the same on my M52233DEMO boards. 

From the CW 6.4 IDE, I could attach to the on-board BDM interface but,
when I attempted to erase flash, prior to loading the uTasker srec file,
it complained that it could not write to memory.

-target processor was 5223x
-connection was PEMICRO-USB
-target initialization cfg file was C:\Program Files\Freescale\CodeWarrior for ColdFire V6.4\E68K_Support\Initialization_Files\M52235EVB_PnE.cfg

But, I noticed that the right flash xml plugin file was not set (via LoadSettings button).
You have to navigate to these files in C:\Program Files\Freescale\CodeWarrior for ColdFire V6.4\bin\Plugins\Support\Flash_Programmer\Coldfire\???.xml.......(of course!)

That did the trick...flash erased, uTasker loaded, app runs just as on the M52235EVB.

Of course it didn't help that whoever manufactured these kits for Freescale put the
wrong documentation in both kits (what's a MPC5566EVB manual doing in a M52233DEMO kit?)
and left out CW registration cards on BOTH M52235EVB kits....but guess I'm just being picky.

Cheers,
McP

[okalex]

Yeah, that's all correct. As I mentioned, everything was set up and working fine, and it stopped working in the middle of programming the chip with CF Flasher. The device is detected by windows, but it fails the test program provided by P&E. I've contacted Freescale and P&E technical support, but haven't come to a resolution yet.

Thanks,
Alex

[Ale]

I have the same problem, my PEMicro first time work  without problem, when I have upgraded the firmware(CodeWarrior IDE Upgrade PEM firmware without request confirmation) PEM stopped to work and now if I try to program I see this message ("Could not force processor into background mode. Check your connection, power, and specified parallel port")

What you suggest?

Thank you

[okalex]

Further update: After reading a previous post regarding a similar problem, I took the recommended steps of changing the USB speed. This had no effect. I also reinstalled CodeWarrior with no luck. I then fully uninstalled the drivers, rebooted, then reinstalled the drivers and rebooted again, just to be sure. Nothing worked. I then noticed the test program on the P&E CD. My BDM failed the test with the following explanation:

"Could not force the processor into background mode. Check your connections, power, and specified parallel port (set to lpt1)."

I'm not sure why it talks about a parallel port since it's a USB Multilink, but I think that's probably just an oversight in the test program. The real problems seems to be that the BDM's firmware is not running correctly. Perhaps it was corrupted somehow while I was reprogramming the application processor. Is there a way to update the BDM processor's firmware so I can test this theory? If not, then I'll have to assume that it's a hardware issue and send my board back to Freescale.

Alex

[J2MEJediMaster]

In CodeWarrior 6.3, go to the Flash Programmer (Tools > Flash Programmer). In the Flash Programmer, select the Target Configuration panel. Check that:

1) You've got the correct processor selected.
2) You've got the PE Micro USB connection selected (PEMICRO_USB).
3) You've got the correct Target Initialization file selected for your board.

---Tom