Hi all, I just started to download the Linux images that came with the CD for friendlyArm board. I followed the normal procedures as follows:- 1-bon part 0 320k 2368k 2-Download VIVI 3-Download the linux kernel 4-Download the file system. And them power off the board ,then move the switch to the NAND side,then power on once again ,And here's the message I see :- load Image of Linux... Wrong Linux Kernel Anyone has any clue on that ????
Wrong version of Supervivi? Download the latest version of Supervivi, zImage and root Qtopia off the downloads page and JTAG in the latest version of Supervivi (for your machine, 64M?). Then try again.
I did all of that but still the same message :- load Image of Linux... Wrong Linux Kernel Any Idea!!!!!!!!!!
Did it ever work? Which variant of the mini2440 dev board do you have? Verify the flash size by reading the part number on the flash chip. Does "Wrong Linux kernel" come up right away or much later in the boot process. Copy/paste the entire output as seen on minicom or whatever you are using.
The flash size is 64 MB
this is copy/paste the Minicom screen after putting the switch on NAND
flash and powering on the board.
Welcome to minicom 2.3
OPTIONS: I18n
Compiled on Sep 25 2009, 23:40:20.
Port /dev/ttyS0
Press CTRL-A Z for help on special keys
��load Image of Linux...
Wrong Linux Kernel
Have you tried the exact steps from the Download Manual? http://www.friendlyarm.net/dl.php?file=download.pdf
I guess you are loading wrong image assuming that it is kernel. check the size of your kernel it should be around 1.8 to 2.2 MB.
@ George :- Yes I did exact @Vivek :- the size of the kenel Image I use =1.9 MB ,and I'm using it from the shipped CD came with the board . Does the partion table has an effect in that,as I reset it to the default settings !!!!!!!!!!!
tarek, yes partition table has effect in u-boot. When you boot your board with switch to NAND position, u-boot is loaded into ram and executed first. u-boot also has environment variables and tries to load kernel as defined in the environment variables. Are you monitoring this using DNW ?? if yes, then please stop autoboot by pressing any key in DNW. then print the environment variables from u-boot and pls paste those here.
I'm not using the u-boot boot loader,I'm using super-vivi ,now I'm just trying to make all the default from the CD ,,just follwoing the steps from the manual,but still stuck in this probelm?? Should I switch to the u-boot ?
Have you updated Superivi, like davef suggested? Also did you try only the files from your CD/DVD or also the ones from the download section?
no i don know how to update supervivi on the nor flash i tried both from the cd and also from the download section.
> no i don know how to update supervivi on the nor flash Download Manual -> section Using H-JTAG
But I dun have the JTAG cable or debugger ,,so what sould I do for that? Would the U-boot solve the issue if I downloaded it instead of the supervivi??
Now I'm sure that the problem is from the boot-loader ,however when I download the super-vivi64M using the USB cable the folloing error is arisen Enter your selection: v USB host is connected. Waiting a download. Length of file is too big : 256416 > 163840 Failed downloading file However when uploading the vBoot.bin it doesn't generate errors but when switching to the NAND flash it doesn't load the boot-loader ?!!!!!!!!!!!! Any Idea???
Now I changed installed the U-boot ,but after installing it I got this message Supervivi> go 0x32000000 go to 0x32000000 argument 0 = 0x00000000 argument 1 = 0x00000000 argument 2 = 0x00000000 argument 3 = 0x00000000 U-Boot 1.3.2-mini2440 (Mar 23 2010 - 14:59:45) I2C: ready DRAM: 64 MB Flash: 2 MB NAND: Bad block table not found for chip 0 Bad block table not found for chip 0 64 MiB *** Warning - bad CRC or NAND, using default environment USB: S3C2410 USB Deviced In: serial Out: serial Err: serial U-Boot 1.3.2-mini2440 (Mar 23 2010 - 14:59:45) I2C: ready DRAM: 64 MB Flash: 2 MB NAND: nand_scan(): Cannot allocate oob_buf 0 MiB
I believe u 've done all that but im making them only to be sure of ur self. I made it for my 64MB nand......u 'll have to change some addresses (get them from the manual on the cd)...although im sure u did it too.. so if this steps are the same as yours....i can send u the u-boot i used..it wasn't from the cd. Turn the boot selection switch to NOR flash on the board. Connect mini2440 with PC using minicom via RS232. Power on the board and you shall see this boot-up menu: ##### FriendlyARM BIOS for 2440 ##### [x] bon part 0 320k 2368k [v] Download vivi [k] Download linux kernel [y] Download root_yaffs image [c] Download root_cramfs image [a] Absolute User Application [n] Download Nboot [e] Download Eboot [i] Download WinCE NK.nb0 [w] Download WinCE NK.bin [d] Download & Run [f] Format the nand flash [p] Partition for Linux [b] Boot the system [s] Set the boot parameters [t] Print the TOC struct of wince [u] Backup NAND Flash to HOST through USB(upload) [r] Restore NAND Flash from HOST through USB [q] Goto shell of vivi Enter your selection: q Press q and Enter at the prompt and switch to vivi promp. Now connect PC with mini2440's USB device port, via a USB cable. Make the compiled u-boot image handy. Tell vivi that you need 239016 Bytes space in the RAM to load something from the USB, starting at 0x31000000 Supervivi> load ram 0x31000000 239016 u USB host is connected. Waiting a download. On another shell window, use following command to download u-boot into the RAM of mini2440 $ sudo ./s3c2410_boot_usb u-boot.bin //whatever its name is Enter root password when prompted, and you shall see this output on the shell csum = 0xd542 send_file: addr = 0x33f80000, len = 0x0003a5a8 Error downloading program Please ignore the error. Now go back to vivi. You shall see follows Now, Downloading [ADDRESS:31000000h,TOTAL:239026] RECEIVED FILE SIZE: 239026 (233KB/S, 1S) Downloaded file at 0x31000000, size = 239016 bytes Now we are ready to write u-boot from the RAM to NAND flash. Execute the code starting at RAM location 0x31000000: Supervivi> go 0x31000000 go to 0x31000000 argument 0 = 0x00000000 argument 1 = 0x00000000 argument 2 = 0x00000000 argument 3 = 0x00000000 U-Boot 1.3.2-dirty-moko12 (Apr 16 2009 - 18:14:52) I2C: ready DRAM: 64 MB Flash: 2 MB NAND: Bad block table not found for chip 0 Bad block table not found for chip 0 64 MiB Found Environment offset in OOB.. USB: S3C2410 USB Deviced In: serial Out: serial Err: serial MAC: 08:08:11:18:12:27 Hit any key to stop autoboot: 0 ///////////////////////////////////////////// hope u find a solution
tarek, You have been a busy lad (?) overnight. Let's summarise things: If you can't get the tutorial at: http://narnia.cs.ttu.edu/drupal/node/131 working then I'd suspect that your Supervivi in NOR is corrupt. That is why I asked if it ever worked. Answer please! If you can't get the above working you have to JTAG in Supervivi (64M version). I would suggest leaving u-boot until later. Done that and now I am back in Supervivi-land.
Thank you,,but I guess something is missing,as I did all of that,and also I've used uboot.bin that wasn't in the CD ,I've built it manually ,but the problem occurs after the line of Supervivi> go 0x32000000 go to 0x32000000 argument 0 = 0x00000000 argument 1 = 0x00000000 argument 2 = 0x00000000 argument 3 = 0x00000000 U-Boot 1.3.2-mini2440 (Mar 23 2010 - 14:59:45) I2C: ready DRAM: 64 MB Flash: 2 MB NAND: Bad block table not found for chip 0 Bad block table not found for chip 0 64 MiB *** Warning - bad CRC or NAND, using default environment USB: S3C2410 USB Deviced In: serial Out: serial Err: serial U-Boot 1.3.2-mini2440 (Mar 23 2010 - 14:59:45) I2C: ready DRAM: 64 MB Flash: 2 MB NAND: nand_scan(): Cannot allocate oob_buf Concerning changing the addresses,what addresses you mean here??,,and where to change them? Did you get superVivi working properly,also did you get U-boot ,linux kernel and filesystem working properly ,which distribution ?
what i meant by the addresses ...that was only in case u use a 128 MB nand ....(sorry i forgot to mention). according to the kernel and the file system........yes they all worked file system--->(GPE). but i think you have a problem with ur u-boot....so,if there is no hope you will have to do what "davef" said...to re-put your supervivi(got a JTAG ..right?) or as a final trial...as i told u i can give u my u-boot regards
YES ,I guess I'll try "GIVEIO" to reflash the NOR flash with the supervivi however I dun see a problem in it ,my problem is in NAND flash ,but I'l' figure it out ,,thank you :) BTW:-Did you try to download supedrVivi on the flash using the normal procedures??,,and did it work with you ?
I thought you could only JTAG into NOR. What has GIVEIO got to do with this platform? NAND: nand_scan(): Cannot allocate oob_buf Goto: http://bliterness.blogspot.com/ and you'll have to search through his blog for the reason for the above. Sorry I can't remember the details. Got to go to work.
OK I check it and it has something to do with believing you have a 64M board when you really have a 128M board. Give us the part number on the flash.
No it's 64MB NAND flash memory Here's the part number :- HY27US08121A
Not the usual NAND flash chip. See the doownloads page. In HTAG you can select different flash chips, but it looks like you are going to need that JTAG cable. All it is a 25 D range plus one IC and the JTAG connector on it. Surprised one didn't come with the board, looks like someone is cutting corners. Good luck.
Yes you are riteio,,it's not the usual NAND flash,,I got the JTAG board ,and want to update the NOR flash,however I dunno either to use the H-jTAG or using the sjflash with the GIVEIO as it says the it for the NOR flash,,and in somewhere else it says its for the NAND flash :( So what should I do for accomplishing updating the NOR flash with the BIOs and also what image is it vBoot.bin??
I have only used H-JTAG. I have no idea of how GIVEIO applies to this situation. I have never used vboot.bin and don't even know what it is for. Think you want Download Manual (BIOS 2.0) on the downloads page to use H-JTAG.
The problem was in the BIOS on the NOR Flash,,after reinstalling the Bios Using H-JTAG ,and the JTAG dongle ,it worked properly and downloaded the normal super-vivi and quotpia :))
Great! Looks like everyone who were encouraging you to JTAG a new copy of Supervivi were right. Hope the rest of your Linux development proceeds at a quicker pace :)
Tarek, (sorry I speak Spanish) I The same thing happens to you ... I want to know what you did after installing the BIOS with H-JTAG ... procedure that you did? ... as you install Qtopia?... My NANDFLASH(KF91208UOB) ... I would appreciate your help Thanks
I also had that problem. I used the vivi image from dvd in vivi.tgz
I am facing the same problem. I followed the same steps as he mentioned here. I have kit with 3.5" screen and 64 MB nand. I am loading supervivi-64M, zImage_N35 and root_qtopia_64M in this order only. Please help...!
Change the order of your procedures as follows:- 1-bon part 0 320k 2368k 2-Download VIVI 3-Download the file system. 4-Download the linux kernel Try it.Then it will work fine.
Hi, I installed wince5 in mini2440 kit via NOR flash after finishing this installation i can see the OS is getting run in mini2440.after that i switched of the mini kit then i select NAND flash, This time the OS is not getting run but i can see the wince logo image is keep on loading.. My question is; 1. How can i install the OS in NAND flash? 2. if i can see the boot logo image in NAND flash then why the OS is not getting run? 3. Give the exact file name and the file format of Wince5.0 to install the OS in NAND flash? 4. while using this command"bon part 0 320k 2368k",the memory size is get divided in to three part and each part has the different size of memory. in that last partition says "badblock=2"..Do u thing becaz of this NAND get booting problem? 5. We are using this command for partitioning but what the meaning of this command "bon part 0 320k 2368k"? 6. Give the exact steps to install wince5 image in mini2440?
Hi
I have installed wince in mini2440(x35)kit via NOR flash after
finishing this installation (boot loader,zimagx35 & root file system),i
changed the mode from NOR to NAND am getting error
Loading Linux ..
Wrong kernel
Anybody can you help me thanks in advance...
its urgent . . . . . .