Tiny Core Linux
dCore Import Debian Packages to Mountable SCE extensions => dCore Armv7 => Allwinner A10 => Topic started by: aus9 on November 22, 2012, 05:53:18 PM
-
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
-
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.
-
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
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
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
-
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.
-
Hi aus9
then I re-insert my sd card and get a bork
Did you run umount first?
-
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.
-
I found my SD card unrealible in my ASUS notebook. Was so bad that I even did not try with the Pi.
-
Oh ok. Bad SD then.
-
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
-
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.
-
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 ?
-
OK, I expected it's Core, sorry
-
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
ls -la /dev/disk/by-path
find out its device names as I have internal drive alway sda, today micro is sdb and sdb1
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
-
ok so I relook it at
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
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
fdisk /dev/sdb
fdisk: can't open '/dev/sdb'
-
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.
-
roberts
thankyou for your link and questions I will answer them soon
2) just to complete my current issues here is what I did immediately after multicard reading report with fdisk showing no partition
I pulled micro out of multi reader and into single SD reader with adaptor etc
ls -al /dev/disk/by-path
total 0
drwxr-xr-x 2 root root 180 Nov 25 07:06 .
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 07:06 pci-0000:00:1d.7-usb-0:8:1.0-scsi-0:0:0:0 -> ../../sdc
lrwxrwxrwx 1 root root 10 Nov 25 07:06 pci-0000:00:1d.7-usb-0:8:1.0-scsi-0:0:0:0-part1 -> ../../sdc1
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 07:02 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
new VERDICT
Can not use micro sd direct into multi reader
-
ok lets see what I have
connect lead to OTG port and connect usb to PC running TC and run lsusb
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse
Bus 002 Device 002: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard
Bus 001 Device 011: ID 18d1:0003 Google Inc.
ok we have 18d1:0003 Google Inc. but google search suggests thats just a Chinese company
2) so went into android and looked but could not see anything but I am not an android expert
so downloaded an app called elixir2 which can generate a report and email you (me)
here are some contents
Processor
Processor: ARMv7 Processor rev 2 (v7l)
Freq range: 30 MHz - 960 MHz
Current freq: 912 MHz
BogoMIPS: 906.46
Available processors: 1
Available processors: 1
Build
Board: crane
Bootloader: unknown
Brand: softwinners
CPU ABI: armeabi-v7a
CPU ABI2: armeabi
Device: apollo-mele
Display: apollo_mele-eng 4.0.4 IMM76D 20120910 test-keys
Hardware: sun4i
Host: pqlabs
Id: IMM76D
Manufacturer: unknown
Model: SoftwinerEvb
Product: apollo_mele
Radio:
SDK version: 15
Serial: unknown
Tags: test-keys
Time: Sep 10, 2012 9:46:33 PM
Type: eng
User: lixg
Version: 4.0.4
Version codename: REL
Version incremental: 20120910
EDIT a quick google shows
http://en.wikipedia.org/wiki/AllWinner_A1X mentions mele sunxi etc
http://en.wikipedia.org/wiki/Rockchip mentions variious processor specs
verdict....I do not have the rockchip so must have the allwinner?
-
sun4i, You have an allwinner. It should boot from a properly prepared sd card with an appropriate script.bin.
-
yeah that is what I hope too
1) Have I tried other distro images yes no success
2) Just did a rather strange test but it might lead me to believe its my android card slot that might be faulty?
Back in TC, check device pathway
dd image onto microsd
Instead of over-writing the script.bin .....which is what I have always done
I elected this test....to place my true script.bin as extra file called script0.bin
3) light tests with current sd card were
no lights for kb so ignored and mouse is as follows
power cord in...mouse on
when screen goes "blank"....mouse goes off
when android splashes re-apppear....mouse is on
4) reboot into TC with microsd card
I have lost the extra script bin
OK not much of test but something funny is happening
redo the overwrite to put correct (my) script.bin into folder
ensure umount yes
redo the tests............same negative result
Each time android completes boot....it claims usb storage is damaged
I now wonder if I have been lucky enough to get a lemon?
-
ok last test for today
I amended my "alternative way to get script.bin" post to include a md5sum check
before you copy to usb stick
after you copy to usb stick
and
after you have made a dd image to microsd carrd
Therefore I can eliminate a bad copy of the script.bin
In that other post I also copied over a number of files including one called magic.bin
file magic.bin
magic.bin: ASCII text, with very long lines, with no line terminators
strings magic.bin
a1sp9maKde37ee6c-6dc4-4d74-86f0-db32116efb53e0e40ccf-7a66-406b-88c3-415b4a62a8f7777622ab-6bd0-464f-9da5-4cc203e855ea8ce5671f-e8b5-442e-9300-2ee6836c538aabf5f481-c961-4895-8245-631f74851d0c2bbb4229-55a8-4929-a165-3f406f0ee441ab5d09a9-c4dc-44bb-a175-cfb7c978a062329ea51e-1ddc-44ff-ac09-9ef7b64e0c52a712e47d-13f7-4490-9fea-bdcd587b8a4a5ed4d4e6-0ba3-45c5-a778-3232a42d4d960a9b7466-d7b3-4087-b8ff-c51763b852a50cd78bb6-a6d5-43a8-8661-fb91abd346433e8a86ee-711e-49c1-ad54-b59dd01fe513e22b0d8b-647f-4417-a115-9806c5d64eec
I wonder if this acts like a magic cookie that some distros have?
I have just spotted its size its 512 bytes....the same size of a stage1 grub bootloader file, in other words a MBR
-
I am (almost) glad others seem to have similar issue now to peek further
http://forum.doozan.com/read.php?6,9762,9762
it concerns "MK802 - Cannot boot anything but Android"
http://comments.gmane.org/gmane.comp.hardware.netbook.arm/4181
-
I suppose an alternative would be to flash nand.
Have you explored LiveSuite ? Have you download your MK802's firmware in case you needed to re-flash via LiveSuite? If so, and are familiar with the procedure then might to possible to flash linux. I recall, some at Miniand were atempting such.
I hope that this is not a trend with other, newer, Allwinner devices. Locked down to only Android.
-
I have not had a chance to do it yet
thanks for thinking of me
I have one last test, I should have done this earlier but can't report the results to after work day
each time I have let android boot....every time in fact, it says usb storage is damaged and to reformat it
but does not give me an option in the android system settings according to my eyesight
I found this site mentioning the size limits of fat/vfat
http://www.genie9.com/support/kb/KnowledgeArticle.aspx?KBID=113+
and this link says android only supports fat32
http://www.envythisstuff.com/techtalk/mk802faq.html#microsdcard
and mentions firmware
a little bit below
as you can see the fat32 test will be easy but the firmware may bork my device
below in above link is the firmware instruction you click a button in a hole etc
2) if fat32 test fails.....I might just give this to my dad as his wife has some memory issues and I have already downloaded some free apps on android to see if they are suitable
eg
memory training games
sudoku
but will decide later
thanks for reading
-
ok before I start to test if android knows I have a working microsd slot lets format the microsd card to fat32 as per above post
Initially I got some codepage error but maro already had a work-a-round as per
http://forum.tinycorelinux.net/index.php/topic,11128.msg58340.html#msg58340
I also had some other errors saying missing files fixed in below command
so as I prefer gparted my new command is
tce-load -i gparted dosfstools mtools glibc_gconv
sudo gparted
microsd formatted as fat32 ending in cylinder boundary
with no files on storage card, boot up of android has no reports of damaged storage device for sandisk 8G microsd
-
ok so I add in linux some media files ....mp3 wav mp4 flv
repower the microsd card.....and it says damaged
I give up
I won't try the firmware as the firmware rev2 does not state any thing that might resolve issues with the microsd slot
it does mention shutdown but not as Official firmware
http://liliputing.com/2012/08/uberoid-custom-rom-for-the-mk802-android-4-0-without-any-bloat.html
does not matter as I give up
this becomes a xmas pressie for daddy