[Project cancelled] my microsd card and my failures

[aus9]

Hi

your dd images

Can you advise what format you prefer the sd card to be made please?

Can you advise what was the size of your partition that you used to create the dd image?

--- I am thinking I have done something wrong again....because I tried it with 8G microSD card formatted as ext3

cheers

[bmarkus]

Originally piCore image was created on 4G card. dd overwrites partition table, so it doesn't matter how it is partioned and formatted before dd'ing. Didn't try but It must be OK with a 8G or 2G card. Image contains first 40M sectors including partition table and a vfat partition, check with fdisk after copying to SD card.

[aus9]

bmarkus.....split off this post if it causes you any concerns

thats great to know and I am thinking I have a faulty microsd card that fits into the allwinner

after redoing an image I can mount the sd card and see its contents and copy over my script.bin

Code: [Select]

dd if=image.img of=/dev/sdd bs=10M
0+1 records in
0+1 records out
9437184 bytes (9.4 MB) copied, 0.0232707 s, 406 MB/s
root@box:/home/tc/android# mount /dev/sdb1 /tmp/android/
root@box:/home/tc/android# cd /tmp/android/
root@box:/tmp/android# ls
LOST.DIR  boot.scr  script.bin uCore  uImage
root@box:/tmp/android# cp -f /home/tc/android/script.bin /tmp/android/
root@box:/tmp/android# ls -al
total 6116
drwxr-xr-x 3 root root   16384 Jan  1  1970 .
drwxrwxrwt 8 root root     320 Nov 23 16:28 ..
drwxr-xr-x 2 root root    4096 Jan  1  1980 LOST.DIR
-rwxr-xr-x 1 root root     256 Jan  1  2010 boot.scr
-rwxr-xr-x 1 root root   44440 Nov 23 16:32 script.bin
-rwxr-xr-x 1 root root 2903396 Nov  5 01:06 uCore
-rwxr-xr-x 1 root root 3287928 Aug 31 05:02 uImage

but after trying it, I get a blank screen and then the android splashes

then I re-insert my sd card and get a bork

Code: [Select]

ls -al /dev/disk/by-path
total 0
drwxr-xr-x 2 root root 140 Nov 23 16:34 ./
drwxr-xr-x 6 root root 120 Nov 23 15:56 ../
lrwxrwxrwx 1 root root   9 Nov 23 16:34 pci-0000:00:1d.7-usb-0:7.4:1.0-scsi-0:0:0:0 -> ../../sde
lrwxrwxrwx 1 root root   9 Nov 23 15:57 pci-0000:00:1f.1-scsi-0:0:0:0 -> ../../sr0
lrwxrwxrwx 1 root root   9 Nov 23 15:57 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root  10 Nov 23 15:57 pci-0000:00:1f.2-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root  10 Nov 23 15:57 pci-0000:00:1f.2-scsi-0:0:0:0-part2 -> ../../sda2

will lash out and buy another card and see if I have the same error

[bmarkus]

Few weeks ago a purchased a brand new 4G Class 4 Verbatim card. It was unrealible, showing a strange behavior, missing or false partition info, etc. Spent hours than took out a 4G A-Data card from my digital camera. It is perfect, all problems gone.

[Rich]

Hi aus9

then I re-insert my sd card and get a bork

Did you run  umount  first?

[curaga]

Few weeks ago a purchased a brand new 4G Class 4 Verbatim card. It was unrealible, showing a strange behavior, missing or false partition info, etc. Spent hours than took out a 4G A-Data card from my digital camera. It is perfect, all problems gone.

On rpi or some other hw? The reader in rpi is known to be bad, but if it's in a Mele etc, hearing it would be good too.

[bmarkus]

I found my SD card unrealible in my ASUS notebook. Was so bad that I even did not try with the Pi.

[curaga]

Oh ok. Bad SD then.

[aus9]

guys

removed last post, I just bought a sandisk class 10 8G for aussie $20. did a dd image, ran gparted on it and it claims allwinner image is fat16!

but still nothing loading, just android

The problem with fat16 apart from it being junky, is the mk802 has NO power off button. I pull the power cord out and that may be the reason for my problem
I know it must be me, as other users have got TC image for allwinner working

1st partition is formatted as FAT32 containing MLO, u-boot.img, uImage files
2nd partition is formatted as ext3 where the filesystem is extracted in root

ref is http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User's_Guide

another page for rescue for allwinner uses fat32
http://forum.doozan.com/read.php?6,8904,8904

[bmarkus]

The problem with fat16 apart from it being junky, is the mk802 has NO power off button. I pull the power cord out and that may be the reason for my problem

Wrong practice. Use shutdown command and wait till system is halted before unplugging power.

Nothing wrong with FAT boot partition as long as you are reading it only or just storing tcz's and backup.

[aus9]

bmarkus

sound advice but I have not touched the android and I can't get any linux to boot to get to a linux shutdown. As you have the RPi and forgive me if you have a MK802 here is a quote and link

Shutdown and Sleep
Though the Android 4.0 Mini PC can go to sleep and dim your screen, it has no shutdown option because it has no power button. By using a third-party app called Quick Boot, we were able to restart the system without yanking the plug. Quick Boot also has a Power Off option, but it doesn't actually turn the power off; it just freezes the screen until you pull the plug.

http://www.laptopmag.com/review/tablets/android-4.0-mini-pc.aspx

as you can see....in android there is no true power off ?

[bmarkus]

OK, I expected it's Core, sorry

[aus9]

So the first thing is, that each time I dd a dd image, I have done stacks,
each and every time, eventually I see no bootloader image for linux AND android starts
if I let it boot and click bottom hand corner its says usb is damaged

2) In order to dd my microsd I have 3 options

micro card inserted into sd card adapter  inserted into single SD usb card reader
ditto...........................................................inserted into an usb multi card reader
micor card inserted directly ....................................into usb multi card reader

3)  Today I decided to stop trying dd and investigate my micro sd a bit, a sandisk 4G

first insert it directly as a micro into multi reader

Code: [Select]

ls -la /dev/disk/by-path

find out its device names  as I have internal drive alway sda, today micro is sdb and sdb1

Code: [Select]

sudo umount /dev/sdb1
gparted

When I tried to format it said some kind of error and then continued and reported it as fat16 and not fat32
hmmm

[aus9]

ok so I relook it at

Code: [Select]

fdisk /dev/sdb

Command (m for help): p

Disk /dev/sdb: 7948 MB, 7948206080 bytes
81 heads, 10 sectors/track, 19165 cylinders, total 15523840 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000a54e0

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048    15523839     7760896    b  W95 FAT32

let android boot up completely and it says usb is damaged, kinda felt that was going to happen based on above

VERDICT
don't use micro sd direct in card reader or don't use gparted in micro sd reader

EDIT

reboot computer into TC to clear anything that might be interfering....I will do anything!

relook at microsd in direct into usb multi reader, yep its lost it partition just like the old micro sd card

Code: [Select]

root@box:~# ls -al /dev/disk/by-path
total 0
drwxr-xr-x 2 root root 140 Nov 25 06:54 .
drwxr-xr-x 6 root root 120 Nov 25 06:55 ..
lrwxrwxrwx 1 root root   9 Nov 25 06:55 pci-0000:00:1d.7-usb-0:7.4:1.0-scsi-0:0:0:0 -> ../../sdb
lrwxrwxrwx 1 root root   9 Nov 25 06:55 pci-0000:00:1f.1-scsi-0:0:0:0 -> ../../sr0
lrwxrwxrwx 1 root root   9 Nov 25 06:55 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root  10 Nov 25 06:55 pci-0000:00:1f.2-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root  10 Nov 25 06:55 pci-0000:00:1f.2-scsi-0:0:0:0-part2 -> ../../sda2

and so

Code: [Select]

fdisk /dev/sdb
fdisk: can't open '/dev/sdb'


[roberts]

I use a USB card reader to dd the Allwinner image without issue.

1. Are you sure your mk802 is allwinner? I see that newer ones are Rockchip.
2. Does your mk802 boot other Linux distros?
3. If you have, then best to zero out any uboot code by the following:
    dd if=/dev/zero of=/dev/sdX bs=512 count=2047
    before attempting to dd a different image.
4. When attempting to boot does the light on keyboard or mouse become visible?
5. If your device always goes to Android, then it may be a faulty sdreader in mk802.

Suggest to go to http://www.miniand.com/wiki/MK802 and try some other images. Let us know.