dCore Import Debian Packages to Mountable SCE extensions > Allwinner A10

Native sunxi kernel compile issues

<< < (2/4) > >>

expresspotato:
If the addresses are the same how come it doesn't load?

(Downloaded)
[root@localhost tmp]# file uImage
uImage: u-boot legacy uImage, Linux-3.0.42, Linux/ARM, OS Kernel Image (Not compressed), 4484772 bytes, Fri Feb  8 21:41:39 2013, Load Address: 0x40008000, Entry Point: 0x40008000, Header CRC: 0x0BDAA54E, Data CRC: 0xB8900C9B

(Compiled)
[root@localhost linux-sunxi-g2d]# file arch/arm/boot/uImage
arch/arm/boot/uImage: u-boot legacy uImage, Linux-3.0.42, Linux/ARM, OS Kernel Image (Not compressed), 4108952 bytes, Mon Feb 16 15:40:40 2015, Load Address: 0x40008000, Entry Point: 0x40008000, Header CRC: 0xEEDFEB9F, Data CRC: 0xD087A747

patrikg:
I also get this behavior before with my guruplug, just forget to add console.

Maybe you also missed to add some console to cmdline..like bootargs for uboot.

env set bootargs 'console=ttyS0,115200'
I don't know what type of serial or another display supported in the kernel.
This line is for my guruplug and debian.

expresspotato:
Hmm didn't help for me:


--- Code: ---U-Boot SPL 2013.01 (Feb 11 2013 - 15:19:28)
Board: mk802ii
DRAM: 1024MB
SUNXI SD/MMC: 0


U-Boot 2013.01 (Feb 11 2013 - 15:19:28) Allwinner Technology

CPU:   SUNXI Family
Board: mk802ii
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   wemac
Hit any key to stop autoboot:  0
sun4i#env set bootargs 'console=ttyS0,115200'
sun4i#
sun4i#
sun4i#boot
reading uEnv.txt
117 bytes read in 3 ms (38.1 KiB/s)
Loaded environment from uEnv.txt
reading boot.scr
304 bytes read in 2 ms (148.4 KiB/s)
Jumping to boot.scr
## Executing script at 44000000
reading script.bin
42132 bytes read in 5 ms (8 MiB/s)
reading uImage
3913400 bytes read in 203 ms (18.4 MiB/s)
reading uCore
2951575 bytes read in 154 ms (18.3 MiB/s)
## Booting kernel from Legacy Image at 48000000 ...
   Image Name:   Linux-3.0.42
   Created:      2015-02-16  22:26:33 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3913336 Bytes = 3.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 43100000 ...
   Image Name:   uCore for Allwinner A10
   Created:      2014-12-26  21:12:42 UTC
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    2951511 Bytes = 2.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

--- End code ---

patrikg:
Have you some readout of the uEnv.txt and boot.scr files.
Have you seen this, i suppose it's using u-boot like this.
https://github.com/linux-sunxi/u-boot-sunxi/wiki
 

roberts:
I have only used linux-sunxi to build kernels and u-boot.

See: http://forum.tinycorelinux.net/index.php/topic,13827.msg78687.html#msg78687

You may want to use this forum's advanced search to search for code sourcery posts by roberts.

Here is why I only use linux-sunxi...

https://linux-sunxi.org/Linux_Kernel

Development for sunxi-based systems had originally begun based on an Allwinner android kernel. The linux-sunxi.org 3.4 kernel series is based on this android kernel and is maintained by a group of volunteers at linux-sunxi.org.

The mainline kernel is the "official" Linux kernel series released by Linus Torvalds. Beginning with kernel 3.8, several developers have been working on integrating sunxi support into the mainline kernel.

U-boot-sunxi is derived from the original Allwinner u-boot and is maintained by a group of volunteers at linux-sunxi.org. It contains an SPL component that takes care of the basic hardware initialization and therefore does not need the proprietary boot0/boot1 loaders from Allwinner. It can boot locally from MMC/SD card and over the network by TFTP, but it cannot access the NAND flash. The current version (as of 08/2014) has been updated to the featureset of mainline u-boot v2014.04; it does not have PSCI-, AHCI- and EHCI-support.

Mainline u-boot is the official upstream u-boot version. Work is currently in progress to integrate the sunxi-specific parts of u-boot-sunxi into mainline u-boot. When this process is completed, u-boot-sunxi can be replaced by mainline u-boot. Mainline u-boot as of release v2014.10 already supports several sunxi-based systems, although not yet all systems that are supported by u-boot-sunxi.

I have built 3.4 from linux-sunix and it also boots fine.

If your lucky and adventurous you may want to try mainline linux kernel 3.18 and mainline u-boot but first check to see if your device is in there!

Navigation

[0] Message Index

[#] Next page

[*] Previous page