mirror of https://github.com/OpenIPC/wiki.git
Update xm510/xm530 docs
parent
a0e7cda9ea
commit
20336ee69c
|
@ -44,10 +44,3 @@ to format jffs2 partition used to store settings.
|
|||
cd /lib/modules/3.0.101\+/xiongmai/
|
||||
/usr/bin/load_xiongmai
|
||||
```
|
||||
|
||||
### Known issues
|
||||
|
||||
For Linux kernel built with the original toolchain (gcc 4.9.2) everything works
|
||||
as expected, but for the same .config built with OpenIPC toolchain (gcc 7.5.0)
|
||||
pty (and only pty) doesn't work. That is weird, and we also ran out of ideas how
|
||||
to fix that. https://t.me/openipc/20225
|
||||
|
|
|
@ -9,8 +9,12 @@ For XM vendor boards with XM530/XM550 SoC ONLY !!!
|
|||
```
|
||||
setenv bootargs 'mem=35M console=ttyAMA0,115200 panic=20 root=/dev/mtdblock3 rootfstype=squashfs init=/init mtdparts=xm_sfc:256k(boot),64k(env),2048k(kernel),5120k(rootfs),-(rootfs_data)'
|
||||
setenv bootcmd 'sf probe 0; sf read 0x80007fc0 0x50000 0x200000; bootm 0x80007fc0'
|
||||
setenv uk 'mw.b 0x80007fc0 ff 1000000; tftp 0x80007fc0 uImage.${soc} && sf probe 0; sf erase 0x50000 0x200000; sf write 0x80007fc0 0x50000 ${filesize}'
|
||||
setenv ur 'mw.b 0x80007fc0 ff 1000000; tftp 0x80007fc0 rootfs.squashfs.${soc} && sf probe 0; sf erase 0x250000 0x500000; sf write 0x80007fc0 0x250000 ${filesize}'
|
||||
setenv uk1 'mw.b 0x80007fc0 ff 1000000; tftp 0x80007fc0 uImage.${soc}'
|
||||
setenv uk2 'sf probe 0; sf erase 0x50000 0x200000; sf write 0x80007fc0 0x50000 ${filesize}'
|
||||
setenv uk 'run uk1 ; run uk2'
|
||||
setenv ur1 'mw.b 0x80007fc0 ff 1000000; tftp 0x80007fc0 rootfs.squashfs.${soc}'
|
||||
setenv ur2 'sf probe 0; sf erase 0x250000 0x500000; sf write 0x80007fc0 0x250000 ${filesize}'
|
||||
setenv ur 'run ur1 ; run ur2'
|
||||
saveenv
|
||||
|
||||
setenv soc xm530 # Your SoC. xm530 for both xm530 and xm550.
|
||||
|
@ -40,5 +44,3 @@ to format jffs2 partition used to store settings.
|
|||
cd /lib/modules/3.10.103\+/xiongmai/
|
||||
/usr/bin/load_xiongmai
|
||||
```
|
||||
|
||||
NB! As of today, video support is still in development.
|
||||
|
|
Loading…
Reference in New Issue