mini6410 is unable to boot from SD

Hi all. There's a problem with my mini6410. It doesn't want to boot from
any SD card at all. I tried to use SD and SDHC cards (8GB, 4GB, 256MB).

On some computers SD-Flasher doesn't work properly - it showing error
(Readonly media?) and SD card stay without filesystem. On others it seems
to be working. Relayouting successfully completes (it creates new section
130MB), fusing superboot too. But mini6410 still can't boot: nor LED1
blinking neither booting...

What could went wrong?

Also computer does not see any new devices when I connect mini via USB
(Driver already was installed).

Hi Kshatriya Kharikesha,

First question i have are you logged on the computer as administrator? This
can help a loot if you are using Win7.

To flash your SD cards do you use an external SD card reader?
Sometimes can happen that just before you try to flash, this is caused by
the card reader (i had the same problems).  

3rd problem "But mini6410 still can't boot" check this two links, maybe it
will help you with the setup of the SD card.

http://www.sasabremec.com/wordpress/arm11-my-friendlyarm/ultimate-guide-...

http://www.sasabremec.com/wordpress/arm11-my-friendlyarm/ultimate-guide-...


Good luck, Sasa

Thanks for replying Sasa!

1. I used winXP, Vista and 7 with administrator rights.

2. I used two external card readers.
this: http://www.ixbt.com/short/images/KingstonMobileLiteReader.jpg
and this: 3Q All-in-one card reader (no picrelated)

3. Nice links, thanks. Btw, there's little inaccuracy in "Ultimate
guide...", in simple steps to create partitions and burn bootloader into SD
card. Without relayouting SD card Flasher just skips fusing.

P.S. Seems to be I used all of possible sequences of writing on card,
fusing before and after placing there ini and image files. And nothing
happened. It's strange...

Device turns on but not booting. SD inserted.
http://i23.fastpic.ru/big/2011/0612/6b/e6eddc96ce4c3a3b1570781d986d016b.jpg

mini6410 with it's card
http://i23.fastpic.ru/big/2011/0612/72/45d2627615b1ef7aee2014ab2e5cd272.jpg

Hi,

This pics are quite common. :) when the board does not start.

OK try with Serial cable you get in the package. You will have all the
necessary debug information(like missing files etc..) and the second thing
I would do is to check the ini file.

I had problem with the image folder and configuration of the ini file.
you have to have files in X:/images/android or linux,Wince and ini in the
root.

But as i said 1. thing connect the serial ports this will help you.

Good luck, Sasa

> ini in the root.
FriendlyARM.ini must be in images folder, as guide said.

Ok, I'll try to find a computer with COM-port. There's only one COM in
motherboard, and it's internal. :(

Thank you for help!

It's me again.
I recently tried to connect mini6410 to PC via COM-port. And I got strange
results. While mini boots from NAND (there's u-boot and Android 2.2) DNW
gets a huge log of events. All is ok.
But when switch is on SD_BOOT position there is a complete silence in
serial port. No matter was SD inserted or not - mini6410 doesn't send
anything to port.
What does it mean?

PS Can anyone show me what mini must send to serial port if it booting from
SD (and what it sending if SD card isn't inserted)?

I have the exact same problem.
We got a mini6410 and a mini2440 a couple of days ago.

The mini6410 miniusb port is not working.
When switching to SDBOOT and restarting the screen goes white (most of the
times, on some cases it has random colors). All 4 leds are permanently on.

I tried with different brands and sizes of SD/SDHC, same behavior.

During NAND boot I get all the boot dump from linux.
During SDBOOT (with and without an SD) I get nothing.

Any clue of what is going on?

Hi, i have also the same problem :) 

From Nand it works to start the Windows CE.. but i want to get Android
working on my Mini6410.. I have flashed successful the superboot.bin to the
device and copyed the images folder with android inside to the sdcard..
than i have edited the friendlyarm.ini to fit to my board..
Than i pluged in the sdcard into the board and started.. But nothing
happens.. Only 1 red LED near the Cardreader is permanantly ON.. 

What can i do???

2All
I have also the same SD boot problem with superboot.

After flashing u-boot-256m.bin from DVD-B/images/Android folder my mini6410
boots :) I think problem in superboot loader, it doesn't work :(

Just seems to be bootloader is half-dead (or maybe half-live). I have no
idea how I got him killed.

<donotread>&#1063;&#1105;
&#1076;&#1077;&#1083;&#1072;&#1090;&#1100;-&#1090;&#1086;,
&#1073;&#1083;&#1103;?!</donotread>

PS Thank you translate.google.com. I know english. With you. :\

I also had the same problem, but I got it resolved:

1. If you lost your SD card file system, first you need to go to disk
manager and give a "new volume."

2. Introduce your SD card

3. You need to start "SD-Flasher.exe" with admistrador rights (right click
mouse). upload file "superboot-20101223.bin" or "superboot-xxxxxxxx.bin."
Click "Scan" and should detect any your SD. Then click "Fuse".

4. If you have any problems, you will have to format your card with the
"relayout" but still if you have started the program as administrator.

5. Then you only have to copy the folder "images" of the DVD 2 (with the
operating system folder that want to install, no need to compete all) in
the root directory. For example;

With Android

FRIENLYARM (X) -> Images -> Android & FriendlyARM.ini
                                                                         

6. Modify the "FriendlyARM.ini" to install or run the operating system


I hope you have been helpful

regards

Hello everyone!

My problem is still unresolved. mini6410 fixedly can't boot from my flash
card (Qumo SDHC 8Gb class:10). We have tried lots of things, nothing
happend.
I also tested slower card (Transcend SDHC 8Gb class:2). And it worked
without any issue. We also tried to byte-to-byte clone working card to fast
Qumo's card and it not worked again (cards is byte-to-byte same). Isn't it
strange?

There is two reasons, as we think:
1. Samsung processor may has a bug that prevents it from booting some
cards?!
2. Some SD cards doesn't support some modes like SPI.

BTW, Jose Enrique, thanks captain.

Yes, I have same issue, it seems like there's a problem with some kind of
SDHC cards. All is going ok except it don't want to boot. Just black screen
on mini6410. It looks like superboot is trying to boot but something stops
it.

Hi all. I have the same issue after installing an Android image from SD
card. I don't know why, but the boot process only goes until some specific
point. 
Checking the serial output I can see that event the touch events are being
logged. However, only a blank (white) screen is shown. 

Attached are the logs I got.

Any help will be appreciated. :)

Regards.

@Fox Paws: Can you try to boot with an 'SD' card instead an 'SDHC' card?
Everything below 2 GiB should be 'SD' only.
The S3C6410 internal iROM code expects a different data layout on 'SDHC'
cards compared to 'SD' cards. Maybe the "SD-Flasher.exe" does not honor
this difference.

Hi Vicente,
Does it mean you have no problems with other OSes?

Hi Juergen,

   I'll try to use a SD card tomorrow... Today, even using a micro SD card
I got the same result.

Hi vib,

   No... Same behavior (white screen) when I used a LinuxQtopia image :(
(this is the end of my log messages):

TCP cubic registered
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
s3c2410-rtc s3c2410-rtc: setting system clock to 2001-11-04 05:43:48 UTC
(1004852628)
Freeing init memory: 908K
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs_read_super: isCheckpointed 0
[03/Nov/2001:21:43:55 +0000] boa: server version Boa/0.94.13
[03/Nov/2001:21:43:55 +0000] boa: server built Apr  8 2010 at 15:40:06.
[03/Nov/2001:21:43:55 +0000] boa: starting server pid=649, port 80
                        
Try to bring eth0 interface up......eth0: link down
Done

Please press Enter to activate this console. 

Regards.

Hi Juergen/vib...

   I've tried to install an Android/qtopia image using a 1G SD card.
However, same problem occurs. :-/
   I'm suspecting that my superboot is not ok. Do you have a guaranteed
superboot.bin to send me?

Thanks in advance.

I tried here with a 512 MiB and a 1 GiB card. I used the
"superboot-20101223.bin" and the sd-flasher.exe and my Mini6410 booted with
these cards. No problems.

Attached is the superboot that came with my DVDs. Hope this helps.

Hi all,
I am having tiny6410 and got the same problem below are the lines I got
from serial port

mount: mounting /sdcard on /r/sdcard failed: No such file or directory
TouchDevice: /dev/touchscreen-1wire
xres = 480, yres = 272


These are the steps I followed
1. Fused SD Card using SD-Flasher.exe
2. Then I got two partitions one with 130Mb and the remaining is visible as
user space.
3. Copied the image from the system to SD Card.
4. Turned the switch to S2 mode
5. Power ON the board and I got above screen

I am having doubt in handling the ini file on to give install or run option
in action variable. I tried both but failed and I got screen in white and
can't get anything form serial.

Hi Venkatraman,

    Your steps are the same taken by me. I'm now suspecting that this error
could be related to my environment (where I ran the SDFlasher). 
    I'm running it into a WinXP image inside a virtual machine (don't know
if it makes sense...) . Moreover, I'm also using an usb card reader/reader.
Could you describe your card creation environment? 

Regards,

I experienced this same issue, and found that while nothing worked with a
Lexar 8GB SDHC Level 4 SD card, it all started to work with an older Kodak
2GB SD card.

Make an images directory in the root of the SD card. The .ini file goes in
this /images. Make another folder (inside /images) called /linux (or
whatever you are using). Put your images in the new directory.

Edit the .ini file and choose install, the OS you want, and the kernel that
matches your LCD, like zImage_N43 or zImage_A70. Make sure the Superboot
version in the images folder matches the version number in the .ini file.

There are now several versions of superboot. Early one just beeps at start
and end. The next one shows a list of options and must have your LCD type
listed in the .ini. The options are chosen by buttons on the board. The
most recent can be set to do a single OS and the lines to choose are
deleted. It also requires push buttons IIRC.

OS's directories you are not using do not have to be present.

SDCard
   /images
      Superboot
      /linux
         zImage_XY
         Root FS Qtopia (or you your stuff)
         Superboot (Duplicated here - don't know if it is needed)
      /android
         android stuff
      /ubuntu
         ubuntu stuff

......

Hi, i've the same problem. White screen and coloured line with tiny6410.
Ideas?

Also the same situation with a Tiny6410. I'm also trying to install
Android.

Using:

1GB SD Card;
WinXP;
superboot-20110727.bin;

I'm attaching the log I obtained through DNW while the S2 Switch was in
NAND position. In SD, there's no log.

The SD Structure:

+images
__+Android
_____Android Stuff..
___FriendlyArm.ini
___superboot-20110727.bin

While fusing my sd, it shows the sucessfull message, but the two buttons
"Reformat" and "Relayout" are both disabled.

My next attempt is trying to use another SD Card Reader...
Any suggestions?

Sorry the bad english.

Sorry.. I forgot to attach the log. Here it is!

Finnally it worked.
After trying the same process with three different SD cards without sucess,
I downloaded the latest version of the superboot (Download Session -> FTP
Server) fused the SD on Win7, and the board booted correctly.

I guess that most of the problems occurs just because the card is
incompatible with superboot...

That's my tip. Worked for me. Hope that it works for you too guys.

The more powerful Superboot6410 is built in about 2011.11.
 It can work well on most SD cards.

Later I will paste its link.
Regards 

Minded

I've had the same issues. For me changing card reader to external resolved
the problem.