Hi to all! I've bought Tiny6410 board and met some problems. I want to update kernel and rootfs in NAND or just run any OS from SD. Anyway I have problem with any booting from SD card. I use SD flasher (with 2 different cards and using winxp and Win7), try to flash superboot or uboot there, but all I achived is message in terminal U-Boot 1.1.6 (Oct 18 2011 - 15:36:18) for FriendlyARM MINI6410 CPU: S3C6410@532MHz Fclk = 532MHz, Hclk = 133MHz, Pclk = 66MHz, Serial = CLKUART (SYNC Mode) Board: MINI6410 DRAM: 256 MB Flash: 0 kB NAND: 1024 MB MMC: 0 MB And nothing after. No running or installing OS from SD, nothing at all!!! How can I fix it? Is it possible to connect with bootloader in NAND ( I suppose it also run when I boot from NAND)?
Tiny6410 SD loading
Hi, Do you have a tiny6410 or mini6410? I've not seen a tiny6410, but your messages are similar to those that I get on my mini6410. However, The messages you are getting are while the board is trying to boot, not trying to flash. Make sure you have the SDCard / NAND switch to SDCard. Check your FriendlyArm.ini file. Make sure it is in /Images and is in DOS format. Mine looks like this: (CommandLine is on one line, not wrapped as shown here) #This line cannot be removed. by FriendlyARM(www.arm9.net) LCD-Mode = No LCD-Type = N43 CheckOneButton=No Action=Install OS= Android VerifyNandWrite=No StatusType = Beeper| LED ################### Android #################### Android-BootLoader = Android/u-boot_nand-ram256.bin Android-Kernel = Android/azImage_n43 Android-CommandLine = root=ubi0:FriendlyARM-root ubi.mtd=2 rootfstype=ubifs init=/linuxrc console=ttySAC0,115200 Android-RootFs-InstallImage = Android/rootfs_android.ubi Android-RootFs-RunImage = Android/rootfs_android.ext3
Hi Colin. Thanks for your answer. I have Tiny6410 bot mini. I am sure that SD/NAND switch is in SD position. Otherwise it successfuly loads Linus image from NAND which was burn in manufacture by FriendlyARM. The problem in loading from SD mode. The message I see is the message from bootloader from SD card as if I pull out the card and press reset message disappears. But this message is everything I have, nothing goes after. I tried to modify FriendlyARM.ini many times, also I had it like yours, changed SD card, changed PC where I burned SD bootloader, danced around the bourd... but nothing helps me.
So can I interrupt loading from NAND and get comand line mode of bootloader thich loads image in NAND?
If you connect a serial cable between your pc and tiny6410, what output do you get on the serial port when attempting to Flash?
jorikdima, What size SD card are you using? Try using a card <= 4GB. I currently am using 4GB cards. SD-Flasher modifies the partition table on the SD card adding a partition at the end of the card. Larger cards have cause some people problems. From the serial interface you can interupt the NAND boot process.
Colin, I caonnected serial cable to COM port of Tiny and saw message which I wrote in the fist message. I used SDHC 8Gb card and SD 1Gb card. "From the serial interface you can interupt the NAND boot process." How??? Thanks
jorikdima, When I power-on my Mini6410 I get the following on my serial interface: --Start Here-- OK U-Boot 1.1.6 (Aug 2 2012 - 11:37:56) for FriendlyARM MINI6410 CPU: S3C6410@532MHz Fclk = 532MHz, Hclk = 133MHz, Pclk = 66MHz, Serial = CLKUART (SYNC Mode) Board: MINI6410 DRAM: 256 MB Flash: 0 kB NAND: 1024 MB In: serial Out: serial Err: serial MAC: 08:90:90:90:90:90 Hit any key to stop autoboot: 0 --Stop Here-- When I hit a key, it stops the countdown, and then I get --Start Here ##### FriendlyARM U-Boot(2010-09, NAND) for 6410 ##### [f] Format the nand flash [v] Download u-boot.bin [k] Download Linux/Android kernel [y] Download root yaffs2 image [a] Download Absolute User Application [n] Download Nboot.nb0 for WinCE [w] Download WinCE NK.nb0 [s] Set the boot parameter of Linux [b] Boot Linux [q] Quit to shell NAND: 1024 MiB, RAM: 256 MiB Enter your Selection: --Stop Here-- I notice that your u-boot U-Boot 1.1.6 (Oct 18 2011 - 15:36:18) for FriendlyARM MINI6410 and my u-boot U-Boot 1.1.6 (Aug 2 2012 - 11:37:56) for FriendlyARM MINI6410 are the same version, but mine is dated 2012, while yours is 2011, which reminded me that I compiled my own u-boot from the source provided at the FriendlyArm download site. I can make available to you my u-boot_nand-ram256.bin if you are unable to compile your own to see if it makes any difference. Whilst considering versions, what version of SD-Flasher.exe are you using? (Bottom right corner)
Oopps, Didn't dowload u-boot from FriendlyArm download site, downloaded it from http://mini6410-debian.googlecode.com/files/u-boot-mini6410-20101106.tar.gz
Hi Colin, thanks for your help. Looks like you replace all FriendlyARM support :) One question. "When I power-on my Mini6410 I get the following on my serial interface:" Is it when you use SD booting mode of switch? Or even when loading from NAND? Also I only now understood your comment about Mini6410 and Tiny6410. Seems both of these boards use the same bootloader. Because I took my from DVD on FriendlyARM download server. And this DVD (image) was for Tiny, but contains uboot with output like for mini. I suppose they are the same as schematic of boards is similar. My UBOOT (when loading from SD) stops after Flash: 0 kB NAND: 1024 MB MMC: 0 MB Seems 0MB of MMC (from which it runs :) :) ) confuses UBOOT. I also see that your UBOOT do not print out MMC size. Ok, I'll try to compile UBOOT you attached today evening. Because I didn't see any uboot sources on FA DVD (or I forget, do not have that PC now here). I use SD-Flasher from Download section of this site. Can write is only at evening as have no that PC here. Thanks again!
jorikdima, "Is it when you use SD booting mode of switch? Or even when loading from NAND?" This is when booting from NAND only. When booting from SD I get : --Start Here-- Superboot-6410 Ver: 1150 CPU: S3C6410 533MHz RAM: 256MB NAND: 1GB(SLC) ID:ECD35195 Touch Device: 1-wire LCD Type: H43(Auto) Installing OS 'LINUX' Installing bootloader... file: /images/Linux/u-boot_nand-ram256.bin: 192 KB(196608 Byte) Installing bootloader succeed Installing kernel... file: /images/Linux/zImage_n43: 2 MB(3000204 Byte) Installing kernel succeed Installing yaffs-image... --Stop Here--
Colin, you have already uboot burned to NAND. But I have superboot as after manufacture. So I do not have such menu. So... I am shoked from FA SW! Today is the first day I moved from freezed point. First of all. SDFlasher on WinXP can not work correctly. Win7 allows to relayout and burn superboot. But only after I remooved all partitions by Partition Manager from SD. If make relayout SDFlasher make additional partitin in the end equal to 130Mb. If pull out and then inserd SD card again it will create one more partition!! Not instead of old one! So after several times I had n*130MB partition and SD flasher wrote data not in the last one. But tiny reads the last sectors as I understand. So need to clear SD by partition manager. Now I have superboot bootloader works from SD. Can run Linux from SD. But!!! After burning SD bootloader in SD I can not erase it!!! U-Boot 1.1.6 (Oct 18 2011 - 15:36:18) for FriendlyARM MINI6410 which I wrote in the first message is shown even if I format the whole SD. Even after schredering SD (filling all sectors zeros)!!! Miracle! And this is on the both SD! Also I can not burn UBOOT to NAND. After burning (took from DVD and build which you attach me) UBOOT shows just OK to COM port :) And nothing else. Burned uboot to nand by DNW tool.
Hmm I was wrong about uboot OK message. I used uboot image for SD loading but run it from NAND. Sorry. But only for this. :)
I wrote Linux image to NAND and UBOOT!!! But during loading uboot wrotes NET: Registered protocol family 17 VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5 s3c-rtc s3c64xx-rtc: setting system clock to 2013-05-08 23:44:03 UTC (1368056643) Freeing init memory: 1408K mount: mounting ubi0:FriendlyARM-root on /r failed: No such device 1Wire touchscreen OK /init: line 103: can't open /r/dev/console: no such file Kernel panic - not syncing: Attempted to kill init! Why he can not mount rootfs to /r ?? I have Linux command line Linux-CommandLine = root=ubi0:FriendlyARM-root ubi.mtd=2 rootfstype=ubifs init=/linuxrc console=ttySAC0,115200
Solved. SLC rootfs image should be used. No I have only problems with SD bootloader. I do not know how to erase it :) And how to write new one :)
I have Mini 6410. When I was booting SD I only get: Superboot6410 Ver:120725 CPU: S3C6410 533MHz RAM:256MB NAND: 1GB(SLC) ID:ECD35195 Touch Device:no1-wire LCD Type: S70(Manu) there is nothing else
I resolved my problem. problem was my-superboot I used 20110405.bin but touch screen not working FRIENDLYARM.ini -7'touch screen ---------------------- LDC-Type=S70