Posts: 24
Joined: Jan 2013
Reputation:
0
As suggested,
I'm starting a thread in order to collect information available for those of us interested in booting linux in our f16ref based devices.
j1nx suggested creating a vfat partition on an SD and copying a kernel renamed as uImage_recovery, and running the device in "recovery mode", by starting it with the reset button pressed. This has not worked for me, so i did follow a tutorial on creating a recovery card for meson 3 processors, which includes burning a u-boot image, creating a partition starting on cylinder 3 and creating a fat filesystem, restoring the partition table (destroyed after burning the uboot image) and copying a kernel image in the vfat partitions.
I've used both u-boot binary "u-boot-aml-ucl.bin" and kernel binary "uImage" found on google, but i can't get them to work.
System boots up normally with android as if no card was on the slot.
Is there any specific source to get binaries for this board or will i have to compile them myself?
I case only sources are available, where can I get the u-boot sources for this board?
Thanks a lot!
Posts: 11,582
Joined: Feb 2008
Reputation:
84
davilla
Retired-Team-XBMC Developer
Posts: 11,582
hint: tfpt boot the kernel and nfs the file system. it's much, much faster than playing the SD card game.
Posts: 11,582
Joined: Feb 2008
Reputation:
84
davilla
Retired-Team-XBMC Developer
Posts: 11,582
hint: Rename /etc/init.d/S95xbmc /etc/init.d/not-S95xbmc until you can boot and get the file system up, then you can kick off xbmc.bin directly from an ssh command-line and see the actual reason why it crashes.
Bonus points for running XBMC under gdb which is present in the buildroot-linux filesystem.
Posts: 6,743
Joined: Oct 2008
Reputation:
317
noggin
Posting Freak
Posts: 6,743
2013-01-17, 22:17
(This post was last modified: 2013-01-18, 14:38 by noggin.)
Thanks Davilla. Still very much learning about this stuff. Thought the Sxx files in /etc/init.d/ were important - just not quite sure how! Your help is greatly appreciated.
Cheers!
So far I've been compiling in a VM under OS X (my fastest machine is a Sandy Bridge i7 Hackintosh) - but I've just ordered an SSD and 2TB HD to give me a native Linux dev environment I can boot into on that machine. Should make developing slightly easier.
Davilla - would you suggest I fork the Pivos or J1nx depository for my work on this? I'm new to this - and will need to make some changes - and knowing the best way to contribute would be useful.
Posts: 666
Joined: Aug 2011
(2013-01-17, 22:17)noggin Wrote: Davilla - would you suggest I fork the Pivos or J1nx depository for my work on this? I'm new to this - and will need to make some changes - and knowing the best way to contribute would be useful.
I try/tried to setup my fork in such a way that any patch/bug fix/Change worth to Pivos can be pushed "upstream". As soon as I catched up on Pivos (if I ever will), all bug reports and fixes can then be pushed as soon as the arise.
Whatever repository you are going to fork, try to do the same.
Posts: 11,582
Joined: Feb 2008
Reputation:
84
davilla
Retired-Team-XBMC Developer
Posts: 11,582
2013-01-20, 23:02
(This post was last modified: 2013-01-20, 23:04 by davilla.)
m3:
setenv serverip 192.168.2.202
setenv gatewayip 192.168.2.1
setenv ipaddr 192.168.2.214
setenv temp logo=osd1,${loadlogoaddr},full,${outputmode},full androidboot.resolution=720p resolution_size=1280,720
setenv temp1 nohltmem=${memsize} mac=${ethaddr}
setenv bootargs rw noinitrd root=/dev/nfs nfsroot=192.168.2.202:/opt/aml-rootfs-m3,nfsvers=3 init=/sbin/init ip=192.168.2.215:192.168.2.202:192.168.2.1:255.255.255.0:target:eth0:off console=ttyS0,115200 a9_clk=800M clk81=187500k ${temp1} ${temp}
nand read logo ${loadlogoaddr} ${logo_start} ${logo_size}
tftpboot 0x82000000 uImage-m3;bootm 0x82000000
The 2nd part is the actual kernel boot.
you might do a 'printenv' to get the uboot command-line
Posts: 1
Joined: Jan 2013
Reputation:
0
2013-01-21, 00:13
(This post was last modified: 2013-01-21, 00:14 by Static_.)
Extracted this from the uboot-wyst-a11.bin:
bootcmd=run nandboot bootdelay=1 baudrate=115200 ethaddr=00:01:02:65:04:75 ipaddr=10.18.9.97 serverip=10.18.9.113 gatewayip=10.18.9.1 netmask=255.255.255.0 hostname=arm_m3 bootfile=uImage loadaddr=0x82000000 testaddr=0x82400000 usbtty=cdc_acm console=ttyS2,115200n8 mmcargs=setenv bootargs console=${console} boardname=m3-oplay chipname=8726m outputmode=720p 720poutputwidth=1280 720poutputheight=720 bootargs=root=/dev/cardblksd2 rw rootfstype=ext3 androidboot.resolution=720p rootwait init=/init console=ttyS0,115200n8 nohlt a9_clk=600M clk81=187500000 mem=1024m mac=${ethaddr} nandargs=setenv bootargs rootfstype=ext3 androidboot.resolution=${outputmode} rootwait init=/init console=ttyS0,115200n8 nohlt logo=osd1,0x84100000,loaded,${outputmode} a9_clk=600M clk81=187500000 mem=1024m mac=${ethaddr} nandboot=run nandargs;
nand read ${normal_name} ${loadaddr} 0 ${normal_size};
bootm ${loadaddr} recoveryboot=echo Enter recovery mode...;
mmcinfo;
fatload mmc 0 ${loadaddr} ${recovery_path};
bootm ${loadaddr} bootloader_start=0 bootloader_size=60000 bootloader_path=uboot-wyst-a11.bin normal_name=boot normal_start=0x8800000 normal_size=0x800000 recovery_name=recovery recovery_start=0x6800000 recovery_size=0x800000 recovery_path=uImage_recovery logo_name=logo logo_start=0x4800000 logo_size=0x400000 aml_logo_name=aml_logo aml_logo_start=0x5800000 aml_logo_size=0x400000
Could you tell me why you added 200M to your a9_clk ?