topic Re: TWR-MCF5441X U-Boot Destroyed in ColdFire/68K Microcontrollers and Processors

TWR-MCF5441X U-Boot Destroyed

Deleted — Mon, 29 Aug 2011 21:21:39 GMT

Hi,

I have a TWR-MCF5441X and did U-Boot upgrade in MRAM with:

-> set u-boot u-boot.bin

-> run upd

But now it won't start up anymore.

I have been trying to program U-Boot through the USB multilink with the CFFlasher tool in the M54418Tower_Linux_BSP_20110422_ltib, without any luck.

when running the commands:

C:\CFFlasher-nand>cf nand erase m54418twr_nand 0 80000

C:\CFFlasher-nand>cf nand write m54418twr_nand 0 80000 1 flash_M54418TWR_uboot.bin

I get the message: Could not initialize BDM device.

The following I already tried:

Running commands on win7 with CW 10.1 installed.

Running commands on winXP SP3 with CW 10.1 installed. (also virtual)

Running commands on winXP SP2 with CW 10.1 / 2.5 and P&E version 10 drivers. installed

Replacing unit_cfz.dll with other versions(from MQX and CW) and alse placing it in system32

Putting/Removing jumper on J10.

All jumpers are on the default places. (j5 is on 3-4) SW1.1 is on ON

I'm out of idea's, any help is appreciated.

Re: TWR-MCF5441X U-Boot Destroyed

Deleted — Sat, 03 Sep 2011 04:46:12 GMT

Solution:

Using CW10.1 to update U-boot for TWR-MCF5441X
1. Create a project with the project wizard for TWR-MCF5441X board and change the build configuration to TWR-MCF5441X_External_Flash
2. Launch Flash Programmer
  
  Use Flash File to Target and configure the Flash Programmer
  
  The Flash Configuration file can be found from within “CW MCU v10.1\MCU\bin\plugins\support\TargetTask\Flash_Programmer\ColdFire”
  
  Click Erase and Program to flash the U-boot to NAND Flash.

Re: TWR-MCF5441X U-Boot Destroyed

yibbidy — Thu, 26 Dec 2013 07:31:24 GMT

Thanks for this solution. I had the same problem and just used CW 10.2 to update to a newer U-Boot version. For some reason the version that came with the TWR-MCF5441x board was not able to TFTP a file across.

Shaun

Re: TWR-MCF5441X U-Boot Destroyed

yibbidy — Sat, 04 Jan 2014 01:38:24 GMT

Oops, forget that about U-Boot TFTP, the problems was with the host setup. The host had two IP addresses, asking for TFTP to one IP address resulted in being given a socket on the other IP address. My mistake. Other TFTP clients could handle this, but not U-Boot, hence initially why I thought the problem was with U-Boot.