My card mini2440 seems except services. Here is result when I want to install 'bootloader ': Supervivi> load ram 0x31000000 149164 u USB host is connected. Waiting a download. Now, Downloading [ADDRESS:31000000h,TOTAL:149174] RECEIVED FILE SIZE: 149174 (145KB/S, 1S) Downloaded file at 0x31000000, size = 149164 bytes Supervivi> go 0x31000000 go to 0x31000000 argument 0 = 0x00000000 argument 1 = 0x00000000 argument 2 = 0x00000000 argument 3 = 0x00000000 barebox 2011.05.0-mini2440-ptx-2011.10.0 (Jul 31 2012 - 16:59:02) Board: Mini 2440 NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit) Bad block table found at page 131008, version 0x01 Bad block table found at page 130944, version 0x01 nand_read_bbt: Bad block at 0x00340000 nand_read_bbt: Bad block at 0x01da0000 nand_read_bbt: Bad block at 0x01f60000 nand_read_bbt: Bad block at 0x0aa00000 nand_read_bbt: Bad block at 0x0e2c0000 nand_read_bbt: Bad block at 0x0f0e0000 dm9000 i/o: 0x20000300, id: 0x90000a46 eth@eth0: got MAC address from EEPROM: 00:00:00:00:00:00 refclk: 12000 kHz mpll: 405000 kHz upll: 48000 kHz fclk: 405000 kHz hclk: 101250 kHz pclk: 50625 kHz SDRAM1: CL4@101MHz SDRAM2: CL4@101MHz Malloc space: 0x33a00000 -> 0x33e00000 (size 4 MB) Stack space : 0x339f8000 -> 0x33a00000 (size 32 kB) running /env/bin/init... syntax error Hit any key to stop autoboot: Usage: timeout [OPTION]... <timeout> Wait <timeout> seconds for a timeout. Return 1 if the user intervented or 0 if a timeout occured -a interrupt on any key -c interrupt on ctrl-c -r interrupt on return -s silent mode AND NOTHING ELSE! AND IF I GO TO /ENV: mini2440:/ ls -l dev cr-------- 4294967295 zero crw------- 8865 defaultenv crw------- 4294967295 mem crw------- 268435456 nand0 cr-------- 8388608 nand_oob0 crw------- 268435456 ram0 crw------- 64 phy0 crw------- 524288 self_raw crw------- 524288 self0 crw------- 393216 env_raw crw------- 393216 env0 is it possible to repair?
My 2440 broken
this is the barebox file ls -l platform-mini2440/images/barebox-image -rw-r--r-- 1 jean jean 149164 juil. 31 16:59 platform-mini2440/images/barebox-image perhaps that the file is corrupted. In that case, how recover it simply? Thank you for your help. Happily that you are there now that Wingston disappeared..
Hi Davef, my findings: - destroyed partitions nand, - file / env / bin / init does not work any more, - ping towards the host ok. Is my case despaired?
Seems you default environment contains garbage. Just erase it. Then Barebox will fall back the the compiled in environment. Modify it to your needs and use the 'saveenv' command to store it again.
> used what is pointed out in QuickStartManuel: > 'platform-mini2440/images/barebox-image' OK, but before that you have to make a choice for 64M or "all the other RAM variants", ie 128M, 256M, etc. I was checking whether or not you had done that. Cheers, davef
Hi Davef, jean@jean-ThinkPad-T41:~/OSELAS.BSP-Pengutronix-Mini2440-2011.10.0$ ptxdist platform configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M info: selected platformconfig: 'configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M' found and using toolchain: '/opt/OSELAS.Toolchain-2011.03.1/arm-v4t-linux-gnueabi/gcc-4.5.2-glibc-2.13-binu tils-2.21-kernel-2.6.36-sanitized/bin' jean@jean-ThinkPad-T41:~/OSELAS.BSP-Pengutronix-Mini2440-2011.10.0$ ptxdist go make: Nothing to be done for `world'. After ptxdist images: Here it was necessary that I make of the place on the hard disk because it was full. C 'est perhaps the reason of my problems? Supervivi> load ram 0x31000000 149164 u USB host is connected. Waiting a download. Now, Downloading [ADDRESS:31000000h,TOTAL:149174] RECEIVED FILE SIZE: 149174 (72KB/S, 2S) Downloaded file at 0x31000000, size = 149164 bytes Supervivi> go 0x31000000 go to 0x31000000 argument 0 = 0x00000000 argument 1 = 0x00000000 argument 2 = 0x00000000 argument 3 = 0x00000000 barebox 2011.05.0-mini2440-ptx-2011.10.0 (Jul 31 2012 - 16:59:02) Board: Mini 2440 NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit) Bad block table found at page 131008, version 0x01 Bad block table found at page 130944, version 0x01 nand_read_bbt: Bad block at 0x00340000 nand_read_bbt: Bad block at 0x01da0000 nand_read_bbt: Bad block at 0x01f60000 nand_read_bbt: Bad block at 0x0aa00000 nand_read_bbt: Bad block at 0x0e2c0000 nand_read_bbt: Bad block at 0x0f0e0000 dm9000 i/o: 0x20000300, id: 0x90000a46 eth@eth0: got MAC address from EEPROM: 00:00:00:00:00:00 refclk: 12000 kHz mpll: 405000 kHz upll: 48000 kHz fclk: 405000 kHz hclk: 101250 kHz pclk: 50625 kHz SDRAM1: CL4@101MHz SDRAM2: CL4@101MHz Malloc space: 0x33a00000 -> 0x33e00000 (size 4 MB) Stack space : 0x339f8000 -> 0x33a00000 (size 32 kB) envfs: wrong magic on /dev/env0 no valid environment found on /dev/env0. Using default environment running /env/bin/init... syntax error Hit any key to stop autoboot: Usage: timeout [OPTION]... <timeout> Wait <timeout> seconds for a timeout. Return 1 if the user intervented or 0 if a timeout occured -a interrupt on any key -c interrupt on ctrl-c -r interrupt on return -s silent mode mini2440:/ mini2440:/ ls -l dev cr-------- 4294967295 zero crw------- 8865 defaultenv crw------- 4294967295 mem crw------- 268435456 nand0 cr-------- 8388608 nand_oob0 crw------- 268435456 ram0 crw------- 64 phy0 crw------- 524288 self_raw crw------- 524288 self0 crw------- 393216 env_raw crw------- 393216 env0 We are therefore in the same point and I do not know any more what to make now. Perhaps I must make one 'clean ' of something in case or a file would be corrupted? Have you an idea?
> make: Nothing to be done for `world'. Perhaps, you could do: ptxdist clean root change something in ptxdist menuconfig save as .config ptxdist go to ensure that ptxdist is building the root image correctly. Do you end up with some files in the images directory? > After ptxdist images: > Here it was necessary that I make of the place on the hard disk > because itwas full. C 'est perhaps the reason of my problems? I do not understand. Has your host machine got enough disk space to hold the images that should be generated? > go to 0x31000000 > argument 0 = 0x00000000 > argument 1 = 0x00000000 > argument 2 = 0x00000000 > argument 3 = 0x00000000 I do not have the mini2440 in front of me but I would expect to see something other than 0x00000000 for these values. > mini2440:/ ls -l dev I have never used this command. What is it suppose to do? > envfs: wrong magic on /dev/env0 I BELIEVE this is telling you that the kernel image is wrong. How big is the kernel image?
> envfs: wrong magic on /dev/env0 Okay, you removed your in-flash environment. Barebox now falls back to its compiled-in one. But it still seems your /env/config file is broken. At least the ensure the "autoboot_timeout" variable is not empty. If it is empty it results into the error message you see: > Hit any key to stop autoboot: Usage: timeout [OPTION]... <timeout> > Wait <timeout> seconds for a timeout. Return 1 if the user intervented > or 0 if a timeout occured > -a interrupt on any key > -c interrupt on ctrl-c > -r interrupt on return > -s silent mode I would recommend: restore the "configs/platform-friendlyarm-mini2440/barebox-<your-choice>m-env/config" file in your BSP (for example from the BSP archive). Then start to change this file again to adapt it to your needs. After that re-build the barebox image again ("ptxdist clean barebox; ptxdist targetinstall barebox") and use its results to continue to follow the quickstart.
Hello Juergen ! Reloaded LUBUNTU and all the mini2440 system (1 day) and yeah... ____ _______ __ | _ `_ _` `/ / | |_) || | ` / | __/ | | / ` |_| |_| /_/`_` _ _ ____ _ _ _ _ ___ _ __ ___ (_)_ __ (_)___ `| || | | || | / _ ` | '_ ` _ `| | '_ `| | __) | || |_| || |_| | | | | | | | | | | | | | |/ __/|__ _|__ _| |_| | |_| |_| |_|_|_| |_|_|_____| |_| |_| `___/ In the barebox, i make one: 'erase / dev / nand0 ' From there, i been able to recover the barebox in memory 'nand ' with defult environment. Then everything is normally. And i am very happy Thank you. Thanks a lot Juergen for for your time.