u-boot erased on M54455EVB

[alainrohou]

Hi

I accidentally erased u-boot.

I tried to flash u-boot.bin by CFflasher with the simple supplied USB cable and with the PE's driver.

I can see the contents of the memory flash (ie : 0400-0000 ...), but when I want to flash CFFlasher freezes and I've got a time-out.

I tried to flash by another soft. Impossible.

Any idea?

Thanks by advance.

[alainrohou]

Hi Tom

Thanks for your help.

I bought my from Digi-key Electronic two weeks ago.

It's a new product.

CFflasher runs on Win-XP - SP3

I tried the compatibility mode (Win2000).

I can erase  0000-0000 -> 00FF-FFFF    (Intel 28F128J3D - 1*8 - Flash1(code))

I can't erase 0400-0000 -> xxxx    (Amtel AT49BV04A - 1*8 - Flash0(boot))

I can't fill Flash1 Flash0.

I can't program Flash1 Flash0

Impossible to write anything to flash-memory (bad data in one of the multuple registers of the µC).

Bad algo ... Don't know.

To be continued ...

[TomE]

In order for any debug-connected flash programmer to work, it has to "know" (meaning that someone has to properly configure it to understand):

• Exactly which CPU model it is connected to and running on, including
• How to set up various CPU control registers
• How to set up the RAM (to load the flasher into), and what address it is at
• How to set up the CPU Clocking system (depends on supplied clock sources)
• How to set up any other memory controllers
• How to disable or pat any internal CPU watchdogs
• How to set up the chip select decoders for the external FLASH chips
• That was the CPU-specific stuff. Then there's the board specific stuff, like
• What clock sources are available, and what frequency the crystals are
• What other peripherals might be present, like an FPGA that might need to be handled.
• Are there any external watchdogs?
• What external Flash chips are connected to what chip select decoders
• How wide the Flash chips are (8/16/32 bit)
• Exactly what brand and model the Flash chips are, so as to use the right algorithm

This is very hard to set up unless you're the designer of the board. You can only really trust this to work if the board was provided with a working flasher setup and the proper configuration files to allow a specific programmer to run.

If the board came with all of that, then it should work. If it didn't, then unless you have a working one from someone else, there's a lot of things to get right.

I think you're better calling "warranty".

Tom

[TomE]

> I bought my from Digi-key Electronic two weeks ago.

> It's a new product.

Send it back. It doesn't work. It isn't supported any more.

Tom

[alainrohou]

Hi Fang li,

Same error "time-out"

I program .bin file.
I tried to convert .bin to .srec by an utility found on the net "bin2srec.exe".
I'm not sure it's a good utility.

I can't fill memory.
I send you screen copies.

Alain

[miduo]

Hi,

No, I do not think that the Cfflasher will work with WIN 7, for lack of the USB driver. And sorry we will not update this tool to Win 7 or Win 8. Actually the Cfflasher is EOL and we do not support it any more.

[TomE]

Alain bought the MCF54455EVB this year. He didn't say who he bought it from (from NXP or eBay? "-). It is still for sale on NXP's web site, or seems to be. So it should still be supported by current software on current computers and operating systems. Searching this forum finds questions from nearly 10 years ago, so it is quite old.

Why is he trying to program it with a tool (CFflasher) that hasn't been supported since WIN7 came out in 2009, or maybe even since Vista came out in 2006? Maybe the documentation that came with it said to do that. Except I've just read through the documentation, and it doesn't mention programming it at all! It does say it comes with U-Boot pre-installed, but nothing as to what to do if it gets erased.

It has an on-board P&E USB Multilink. P&E's PROGCFZ might support it, but that's $199. CodeWarrior should support it. Alain, how were you going to program this thing?

I think you should keep trying with the Win XP you have. If the erase works, but the programming doesn't, then you've probably got something set up wrong. Make sure you're addressing the right devices at the right addresses. Make sure the image you're trying to program is set to target the right address.

> When updating linux image, system crashed and erased the boot loader.

The Boot and Linux Image are in different FLASH chips at different addresses. I think you must have selected the wrong chip to work on somehow. Too bad the hardware doesn't have a jumper to protect the boot flash in hardware against "accidents". That's always a good thing to add to the design.

Tom

[alainrohou]

Hi,

I've got a reply from NXP support.

My contact said me to use CFFasher on Win-XP.

I do so.

Erasing flash works fine, but programming no.

Have you a solution for me.

If I'll buy a licence for Codewarrior, my problem will be solved?

[TomE]

Did it ever work on that computer? Can you go back to the last computer it worked on?

You may need to go back to an older machine running a 32-bit version of Windows. Maybe Win-7. Maybe XP.

Tom

[alainrohou]

Hi Tom,

CFFlasher runs on Win7-32 bits.

Some screen copies:

config CFFlasher:

view memory:

view "logs"

before flashing:

flashing :

error flashing:

logs:

If you've ideas ...

I just bought this EVB (in 2017 ...) - When updating linux image, system crashed and erased the boot loader.

Thanks by advance.

Alain