[Arm-netbook] A new MK802 failing to boot from SD

[Alejandro Mery]

On 27 July 2012 20:20, Roman Mamedov <rm at romanrm.ru> wrote:
> Hello,
>
> On Thu, 26 Jul 2012 04:10:46 +0600
> Roman Mamedov <rm at romanrm.ru> wrote:
>
>> I've got a new MK802 here, it's an 1GB model, ordered from TomTop.
>>
>> It works fine in the Android from its internal flash. But so far I haven't
>> been able to make it boot anything from an SD card. Not even the pre-made
>> images from Miniand and Rikomagic, which are supposed to work on all MK802s.
>> I do not have a serial console at the moment, so can't tell what's happening
>> there.
>
> I've now successfully booted a 3.0.38 kernel. Couldn't get SD booting to work,
> so the only way to do that was to put a kernel with hardcoded
> "root=/dev/mmcblk0p2" as bImage into nanda.
>
> The kernel is booted directly, not via u-boot (as mentioned on
> http://elinux.org/Hack_A10_devices ), in linux/linux.ini
>
>     [segment]
>     img_name = c:\linux\bImage
>     img_size = 0x2000000
>     img_base = 0x40008000
>
> I suppose this leads to a lack of certain initializations that the kernel
> came to expect from u-boot. So I am attaching the dmesg. Some highlights:
>
> [    0.000000] Total Detected Memory: 16MB with 1 banks
> [    0.000000] 64 MB reserved for MALI
>
> [    0.000000] Memory: 640MB 16776528MB = 16777168MB total
> [    0.000000] Memory: 511960k/511960k available, 143404k reserved, 0K highmem
>
> This one is supposed to be a 1GB unit, but not even the stock android sees
> 1GB, so I wonder if this is just a fraud by the supplier (TomTop).

please try with IGNORE_ATAG_MEM enabled