[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Flash problems with MCM



What is your kernelconfig file?
Try copying the devboard_82 kernelconfig file on e100lx_mcm directory,
recompiling the kernel by "make kernel" and "make images" and doing
./flashit
(This should be works with 2.4.19 at least)

Be careful with ptablespec file. There is information on this file about
size of parts (rescue, kernel, jffs)

For Axis82/83 should be:

rescue    0x010000    ro    rescue    rescue.img
flash1     0x350000    rw    kernel    flash1.img
flash2     0x2a0000    rw    jffs         flash2.img
  ____________________________________________
\
/   Unai García Amaro
\   Mondragon Unibertsitatea
/   unai.garcia@xxxxxxx.edu
\_____________________________________________



----- Original Message ----- 
From: "Eric Lane" <elane@xxxxxxx.us>
To: "Dev-Etrax" <dev-etrax@xxxxxxx.com>
Sent: Thursday, July 10, 2003 2:32 PM
Subject: Flash problems with MCM


> I have a devboard 82 as well as our prototype board with an MCM.  Our
> prototype board has the same SDRAM configuration that the Devboard 82 has.
> However, our prototype does not have any external flash.
>
> I am able to get the devboard 82 software to flash without a problem.
> However, I am unable to flash with the e100LX_MCM_1_0 software(unchanged)
to
> either board.  I am not getting anything out of the debug ports.  This is
> what is showing up in the terminal window:
>
> Using internal boot loader: INTERNAL_NW - Network boot (default).
> Starting boot...
> We're doing a flash write, this may take up to a few minutes...
>
>
> Device ID = 0x0000506f
> This bootloader was built by root on Wed Jul 9 13:25:13 EDT 2003.
> Checksum of bootloader is 0x00097d9d
> Waiting for load info.
> Checksum of file is 0x00001e04
> Got load info.
> SET_REGISTER
> 0xb0000000
> 0x000095f8
> SET_REGISTER
> 0xb0000004
> 0x00000104
> SET_REGISTER
> 0xb000000c
> 0x00601515
> SET_REGISTER
> 0xb0000008
> 0x8000c002
> PAUSE_LOOP
> 0x00020000
> SET_REGISTER
> 0xb0000008
> 0x8000c602
> SET_REGISTER
> 0xb0000008
> 0x8000c002
> SET_REGISTER
> 0x38001f00
> 0x00000007
> SET_REGISTER
> 0xb0000008
> 0x8000c402
> SET_REGISTER
> 0xb0000008
> 0x8000c002
> LOOP
> 0x38001f00
> 0x38001f5c
> SET_REGISTER
> 0xb0000008
> 0x8000c402
> SET_REGISTER
> 0xb0000008
> 0x8000c002
> LOOP
> 0x38001f00
> 0x38001f5c
> SET_REGISTER
> 0xb0000008
> 0x8000c402
> SET_REGISTER
> 0xb0000008
> 0x8000c002
> LOOP
> 0x38001f00
> 0x38001f5c
> SET_REGISTER
> 0xb0000008
> 0x8000c402
> SET_REGISTER
> 0xb0000008
> 0x8000c002
> LOOP
> 0x38001f00
> 0x38001f5c
> SET_REGISTER
> 0xb0000008
> 0x8000c402
> SET_REGISTER
> 0xb0000008
> 0x8000c002
> LOOP
> 0x38001f00
> 0x38001f5c
> SET_REGISTER
> 0xb0000008
> 0x8000c402
> SET_REGISTER
> 0xb0000008
> 0x8000c002
> LOOP
> 0x38001f00
> 0x38001f5c
> SET_REGISTER
> 0xb0000008
> 0x8000c402
> SET_REGISTER
> 0xb0000008
> 0x8000c002
> LOOP
> 0x38001f00
> 0x38001f5c
> SET_REGISTER
> 0xb0000008
> 0x8000c402
> SET_REGISTER
> 0xb0000008
> 0x8000c002
> LOOP
> 0x38001f00
> 0x38001f5c
> SET_REGISTER
> 0xb0000008
> 0x8060c202
> SET_REGISTER
> 0xb0000008
> 0x8000c002
> SET_REGISTER
> 0xb0000008
> 0x80008002
> SET_REGISTER
> 0xb0000030
> 0x0000ff00
> SET_REGISTER
> 0xb0000038
> 0x0000ff00
> PACKET_INFO
> 0xc0004000
> 0x00200018
> Checksum of file is 0x1316a3e3
> FLASH
> 0xc0014000
> 0x00010000
> 0x001f0000
> Found 1 x 16Mb BB at 0x80000000
> Found 1 x CFI at 0x84000000
> 0x80010000: Erasing 0x001f0000 bytes...done, verifying...OK
> 0x80010000: Writing 0x001f0000 bytes...Verify error at 0x800fc004
> Timed out!
> Verify error at 0x800fc004
> Timed out!
> Verify error at 0x800fc004
> Timed out!
> Verify error at 0x800fc004
> Timed out!
> Verify error at 0x800fc004
> Timed out!
> Verify error at 0x800fc004
> Timed out!
> Verify error at 0x800fc004
> Timed out!
> Verify error at 0x800fc004
> Timed out!
> Verify error at 0x800fc004
> Timed out!
> Fatal verify error.
> 0x80010000: Erasing 0x00010000 bytes...
>
> At this point it locks up.  What would you recommend that I do?
>
> Thanks,
>
> Eric
>