MCF52233DEMO PE-BDM-USB failure + MCF52233 CFFlasher .alg .cfg files

[bytebum]

Everything worked fine yesterday at the "ethernet seminar" using MCF52233DEMO board with PE-BDM-USB and the tools loaded onto the seminar's laptops. However, when I got home, loaded the tools onto a desktop, everything works except the PE-BDM-USB, which only partially works (seems to read somewhat, runs running-1's over short address range, etc.) but when I try to use CodeWarrior 6.3beta to load a console demo program, that fails -- "Initializing" forever. Cannot erase flash, either.

I've reloaded the PE drivers. No change.
Changed USB cables. No change.
Tried alternate MCF52233DEMO board. No Change.
RS232 and Ethernet were working fine (Until I erased the interrupt vectors from flash ).

I got CFFlasher3.1 to be able to erase 1 sector at a time (up to sector 3, but no further). So, I really need .alg and .cfg files for CFFlasher3.1 for MCF52233.

Any help would be appreciated.

TIA,
-- Larry

[thm59]

---

bytebum wrote:
Everything worked fine yesterday at the "ethernet seminar" using MCF52233DEMO board with PE-BDM-USB and the tools loaded onto the seminar's laptops. However, when I got home, loaded the tools onto a desktop, everything works except the PE-BDM-USB, which only partially works (seems to read somewhat, runs running-1's over short address range, etc.) but when I try to use CodeWarrior 6.3beta to load a console demo program, that fails -- "Initializing" forever. Cannot erase flash, either.

I've reloaded the PE drivers. No change.
Changed USB cables. No change.
Tried alternate MCF52233DEMO board. No Change.
RS232 and Ethernet were working fine (Until I erased the interrupt vectors from flash ).

I got CFFlasher3.1 to be able to erase 1 sector at a time (up to sector 3, but no further). So, I really need .alg and .cfg files for CFFlasher3.1 for MCF52233.

Any help would be appreciated.

TIA,
-- Larry

---

Hello,

I had exactly the same problem. And finally:
1. I installed the BDM interface drivers from the (mini) P&E CD
2. I testet the connection with the board with the P&E program :
Test_USB_ML_CF_Hardware.exe ; it responded sucessfully
3. In installed CW6.3 on my computer (Win98). At the end of installation, I got the messge "Use WREG16 to install WDM drivers on windows 95/98/ME system"
4. I followed the seminar exercice, BUT CW 6.3 could not erase/blank chek the MCF52233 flash memory.Error message : "Flash Programmer: Internal error: Lock failed for the current protocol plugin."

I Think it is not a BDM connection problem, but a CW problem?
Could someone help me or have a solution?

Thanks
thierry

[JTech]

With regards to this problem....

I suffered it myself. It is the PC motherboard. Playing with the USB settings in CMOS setup will resolve it.

I have identified the problem to be notorious with cheap motherboards, BIOSTAR, et, al. Even some Gigabyte boards have this problem, due to the VIA chipset not being 100% USB2.0 compliant. In particular the VT8237R Plus chipset is notorious for this.

Disabling USB legacy support as mentioned, and for some obtuse motherboards, forcing the USB controller into USB1.1 mode resolves the problem completely.

[JTech]

The following will be a list I update over the coming months, as I have experience, of boards that give trouble with the COLDFIRE BDM:

Gigabyte GA-8VM800PMD775 (INTEL P4 Motherboard with VIA chipset)

Solution: In CMOS Setup, disable "USB Legacy Support", enable USB 2.0. Once changes are made, use XP "System Restore" and restore to a time when everything still worked. Then install the latest Freescale Codewarrior (v7.0 at least) ensuring that the M52233DEMO is disconnected at all times during this process. Once Codewarrior completes install, reboot and then, plug the evaluation board into the USB port, it should ask for a driver, just select "Install the software automatically" and it should work then.

BIOSTAR Motherboard (Intel P4 Chipset with Phoenix BIOS)

Solution: In CMOS Setup, set mode to "USB1.1" not "USB1.1 & 2.0". Reboot the machine with the evaluation board disconnected. Then connect the board, and it should work fine. This resolves flash and erasure errors (hanging with "Initializing......")

Forcing the controller to USB1.1 on this motherboard doesn't really, unlike the Gigabyte board which then really goes into USB1.1 mode and causes Windows to pop balloons when you plug in USB2.0 peripherals. I suspect the chipset or the BIOS code is buggy on those motherboards, or potentially, as I said above, the south bridge chip has errata.

[mjbcswitzerland]

Hi Larry
I am using the EVB and not DEMO but maybe the following could help you.
1. Be sure to be using the latest version of CFFlasher 3.1.1 (you can download it from the freescale web site). I had problems with the version delievered on the CD and they were cured with the newest version - ensure that you select the correct target (not something which looks as though it should be compatible - that also failed for me)
2. If you manage to erase, load the following code which should prove board functionality:
http://www.mjbc.ch/software/uTasker/M5223X/uTaskerV1.2beta005_m5223X.s19

See more details about the code in the following posting:
http://forums.freescale.com/freescale/board/message?board.id=CFCOMM&message.id=274

If you would like a kick start with the M5223X, the uTasker with integrated TCP/IP stack (see posting) is free for educational and other non-commercial work. It has been ported to the M5223X and the M5223X real-time simulator allows complete projects to be develped and tested on the PC before moving to final tests on the target.

There are no catches, just a highly efficient and fun solution with growing community which welcomes new users.

Regards

Mark Butcher
ww.mjbc.ch

PS If you really have a failed board the uTasker simultaor would tide you over until you get a new one!

[bytebum]

Mark,

Thanks for the reply.

I didn't see a CFFlasher 3.1.1 specifically called out, but I did download the latest version (self-identified CFFlasher 3.1 before download), it may be the 3.1.1 version with MCF52233 target.

After having no problems with CodeWarrior on another computer, we finally found a culprit -- in the boot BIOS on the failing desktop CPU, a "USB Detect Legacy Disks" was enabled. When we disabled that option, the PE-BDM-USB problems cleared up.

I will take a look at your uTasker.

Thanks,
-- Larry