Debian on QiZhiTong 501mv2
Posted by wacke
|
Debian on QiZhiTong 501mv2 November 05, 2015 06:29AM |
Registered: 8 years ago Posts: 166 |
below is the screen output:
Thak you very much
-------------------
Moderator edit: Change the post subject to make it easier for people to find this.
Edited 1 time(s). Last edit at 02/01/2016 07:24AM by bodhi.
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: MB-302 v1.0
U-Boot 1.1.4 (Nov 11 2010 - 16:09:33) Marvell version: 3.4.27 T06
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFAC0
Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz
DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:64 MB
Flash: 0 kB
CPU : Marvell Feroceon (Rev 1)
Streaming disabled
Write allocate disabled
Module 0 is RGMII
USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME], egiga1
Hit 'Tab' key to switch the boot entry: 0
Thak you very much
-------------------
Moderator edit: Change the post subject to make it easier for people to find this.
Edited 1 time(s). Last edit at 02/01/2016 07:24AM by bodhi.
|
Re: Can this device flash "Bodhi's U-boot"? November 05, 2015 01:10PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
Most likely, yes!
But you need to tell us what brand, model. And if you have any info: link to GPL source, product advertisement,... things like that. And info such as memory, USB, HDD, LED will tell which existing u-boot image is the closest to your box.
And looks like you have serial console, you could try UART booting either the Sheevaplug or the Pogo E02 u-boot image from the u-boot release thread.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Most likely, yes!
But you need to tell us what brand, model. And if you have any info: link to GPL source, product advertisement,... things like that. And info such as memory, USB, HDD, LED will tell which existing u-boot image is the closest to your box.
And looks like you have serial console, you could try UART booting either the Sheevaplug or the Pogo E02 u-boot image from the u-boot release thread.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Can this device flash "Bodhi's U-boot"? November 05, 2015 07:48PM |
Registered: 8 years ago Posts: 166 |
Thanks for your reply.
My device is QiZhiTong 501m v2,and it's an OEM Model.I have attched picture of this model.
info of this model :
CPU:1.2 GHz ARM Marvell 88F6281
Memory:64M NAND Flash,512M DDR2 800
Storage:SDx1,SATAx1,USB 2.0x2
Network:88E6161 Switch chip with 5 gigabit port,88E1116 with 1 gigabit aux port
I have tried UART boot,but not work.
My device is QiZhiTong 501m v2,and it's an OEM Model.I have attched picture of this model.
info of this model :
CPU:1.2 GHz ARM Marvell 88F6281
Memory:64M NAND Flash,512M DDR2 800
Storage:SDx1,SATAx1,USB 2.0x2
Network:88E6161 Switch chip with 5 gigabit port,88E1116 with 1 gigabit aux port
I have tried UART boot,but not work.
|
Re: Can this device flash "Bodhi's U-boot"? November 05, 2015 10:58PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke Wrote:
-------------------------------------------------------
> Thanks for your reply.
>
> My device is QiZhiTong 501m v2,and it's an OEM
> Model.I have attched picture of this model.
>
> info of this model :
>
> CPU:1.2 GHz ARM Marvell 88F6281
> Memory:64M NAND Flash,512M DDR2 800
> Storage:SDx1,SATAx1,USB 2.0x2
> Network:88E6161 Switch chip with 5 gigabit
> port,88E1116 with 1 gigabit aux port
>
> I have tried UART boot,but not work.
Looks like the closest Kirkwood to yours is the NSA320. But it does not have SD slot. The Kirkwood boxes that have SD slot are the Pogo V4 and the one of the older plugs (Sheeva or Guru, I forgot).
I think the NSA320 is really the easiest to get working because the 512MB DDR2 memory and 1.2Ghz CPU. That if you can live without booting with the SD card. In Linux, it is easier to get the SD card working by changing DTS. But u-boot is a different matter, because we would have marry the SD card code, e.g. for Pogo V4 , to the NSA320 to get SD card working.
Not being able to boot with UART would make it a little bit more risky to try, though. So I can't really recommend any of the u-boot images. However, if you are advantureous and willing to risk temporarily bricking it, you could use one of the closest ones: sheevaplug or NSA320.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Thanks for your reply.
>
> My device is QiZhiTong 501m v2,and it's an OEM
> Model.I have attched picture of this model.
>
> info of this model :
>
> CPU:1.2 GHz ARM Marvell 88F6281
> Memory:64M NAND Flash,512M DDR2 800
> Storage:SDx1,SATAx1,USB 2.0x2
> Network:88E6161 Switch chip with 5 gigabit
> port,88E1116 with 1 gigabit aux port
>
> I have tried UART boot,but not work.
Looks like the closest Kirkwood to yours is the NSA320. But it does not have SD slot. The Kirkwood boxes that have SD slot are the Pogo V4 and the one of the older plugs (Sheeva or Guru, I forgot).
I think the NSA320 is really the easiest to get working because the 512MB DDR2 memory and 1.2Ghz CPU. That if you can live without booting with the SD card. In Linux, it is easier to get the SD card working by changing DTS. But u-boot is a different matter, because we would have marry the SD card code, e.g. for Pogo V4 , to the NSA320 to get SD card working.
Not being able to boot with UART would make it a little bit more risky to try, though. So I can't really recommend any of the u-boot images. However, if you are advantureous and willing to risk temporarily bricking it, you could use one of the closest ones: sheevaplug or NSA320.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Can this device flash "Bodhi's U-boot"? November 05, 2015 11:24PM |
Registered: 8 years ago Posts: 166 |
Thanks for reply.
I have tried the uboot.2014.07-tld-4.nsa310s.bodhi.tar u-boot img,and bricked,waiting for openjtag to get it back.
I want to boot latest openwrt with 3.18+ kernel(compile from source myself), the kernel booted,but the 88E6161 switch chip driver dosen't work,is it must get u-boot with FDT support?
I have tried the uboot.2014.07-tld-4.nsa310s.bodhi.tar u-boot img,and bricked,waiting for openjtag to get it back.
I want to boot latest openwrt with 3.18+ kernel(compile from source myself), the kernel booted,but the 88E6161 switch chip driver dosen't work,is it must get u-boot with FDT support?
|
Re: Can this device flash "Bodhi's U-boot"? November 06, 2015 12:09AM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke Wrote:
-------------------------------------------------------
> Thanks for reply.
> I have tried the
> uboot.2014.07-tld-4.nsa310s.bodhi.tar u-boot
> img,and bricked,waiting for openjtag to get it
> back.
You are too quick :) that u-boot is definitely not the one to use. It's for a different Marvell SoC.
>
> I want to boot latest openwrt with 3.18+
> kernel(compile from source myself), the kernel
> booted,but the 88E6161 switch chip driver dosen't
> work,is it must get u-boot with FDT support?
There is no need to get FDT-able u-boot. Stock u-boot should work with the DTB appended to the kernel 3.18+ uImage. For this chip, I think you must add its definition to the DTS, in a similar way that the ethernet chip is defined. I would look for it in the kernel Marvell drivers area to find the correct name. Or if you can find it in kernel 3.16 or earlier then that would be a quicker way to get it working (3.16 or earlier in my releases are non-FDT kernels).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Thanks for reply.
> I have tried the
> uboot.2014.07-tld-4.nsa310s.bodhi.tar u-boot
> img,and bricked,waiting for openjtag to get it
> back.
You are too quick :) that u-boot is definitely not the one to use. It's for a different Marvell SoC.
>
> I want to boot latest openwrt with 3.18+
> kernel(compile from source myself), the kernel
> booted,but the 88E6161 switch chip driver dosen't
> work,is it must get u-boot with FDT support?
There is no need to get FDT-able u-boot. Stock u-boot should work with the DTB appended to the kernel 3.18+ uImage. For this chip, I think you must add its definition to the DTS, in a similar way that the ethernet chip is defined. I would look for it in the kernel Marvell drivers area to find the correct name. Or if you can find it in kernel 3.16 or earlier then that would be a quicker way to get it working (3.16 or earlier in my releases are non-FDT kernels).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Can this device flash "Bodhi's U-boot"? November 06, 2015 02:13AM |
Registered: 8 years ago Posts: 166 |
|
Re: Can this device flash "Bodhi's U-boot"? November 06, 2015 03:45AM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
It looks like the kernel supports this, but the driver must be compiled to run either as module or in kernel with Debian.
For OpenWRT, you should try compiling with this kernel config
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
It looks like the kernel supports this, but the driver must be compiled to run either as module or in kernel with Debian.
For OpenWRT, you should try compiling with this kernel config
NET_DSA_MV88E6123_61_65
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Can this device flash "Bodhi's U-boot"? November 06, 2015 06:30AM |
Registered: 8 years ago Posts: 166 |
|
Re: Can this device flash "Bodhi's U-boot"? November 06, 2015 03:02PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke Wrote:
-------------------------------------------------------
> I have compiled the kernel with
> "NET_DSA_MV88E6123_61_65" config,but the kernel
> boot log shows this:
>
Problem like this could be caused by different things.
If you would like to try Debian on USB booting, I could help when there is problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/06/2015 03:02PM by bodhi.
-------------------------------------------------------
> I have compiled the kernel with
> "NET_DSA_MV88E6123_61_65" config,but the kernel
> boot log shows this:
>
> platform mv643xx_eth_port.0: Driver > mv643xx_eth_port requests probe deferral >
Problem like this could be caused by different things.
If you would like to try Debian on USB booting, I could help when there is problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/06/2015 03:02PM by bodhi.
|
Re: Can this device flash "Bodhi's U-boot"? November 08, 2015 08:28PM |
Registered: 8 years ago Posts: 166 |
Hi bodhi,
I'v got my device back,and I tried NSA320,Sheevaplug uboot,but no lucky,there was no serial console output at all.
Is there any way to get new uboot work then(by modify uboot source code)?
And I recompiled the openwrt kernel(modifed dts file),the kernel boot log:
I'v got my device back,and I tried NSA320,Sheevaplug uboot,but no lucky,there was no serial console output at all.
Is there any way to get new uboot work then(by modify uboot source code)?
And I recompiled the openwrt kernel(modifed dts file),the kernel boot log:
Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.3.0 (Wacke@HOME-Server) (gcc version 5.2.0 (OpenWrt GCC 5.2.0 r47397) ) #4 Mon Nov 9 00:06:28 CST 2015 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine model: QiZhiTong 501M V2 [ 0.000000] Memory policy: Data cache writeback [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [ 0.000000] Kernel command line: rootdelay=1 root=/dev/mmcblk0p1 noinitrd console=ttyS0,9600 [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 514292K/524288K available (3830K kernel code, 133K rwdata, 1064K rodata, 160K init, 192K bss, 9996K reserved, 0K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB) [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) [ 0.000000] .text : 0xc0008000 - 0xc04cfdc4 (4896 kB) [ 0.000000] .init : 0xc04d0000 - 0xc04f8000 ( 160 kB) [ 0.000000] .data : 0xc04f8000 - 0xc0519470 ( 134 kB) [ 0.000000] .bss : 0xc0519470 - 0xc05496dc ( 193 kB) [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns [ 0.000008] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns [ 0.000139] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584) [ 0.090081] pid_max: default: 32768 minimum: 301 [ 0.090204] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.090222] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.090710] CPU: Testing write buffer coherency: ok [ 0.091027] Setting up static identity map for 0x81e0 - 0x821c [ 0.091292] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3 [ 0.095526] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.095655] pinctrl core: initialized pinctrl subsystem [ 0.096686] NET: Registered protocol family 16 [ 0.097037] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.097842] cpuidle: using governor ladder [ 0.098179] Feroceon L2: Enabling L2 [ 0.098220] Feroceon L2: Cache support initialised. [ 0.098476] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set [ 0.098570] [Firmware Info]: /ocp@f1000000/ethernet-controller@76000/ethernet1-port@0: local-mac-address is not set [ 0.114168] SCSI subsystem initialized [ 0.114494] usbcore: registered new interface driver usbfs [ 0.114568] usbcore: registered new interface driver hub [ 0.114637] usbcore: registered new device driver usb [ 0.115524] clocksource: Switched to clocksource orion_clocksource [ 0.116490] NET: Registered protocol family 2 [ 0.117015] TCP established hash table entries: 4096 (order: 2, 16384 bytes) [ 0.117071] TCP bind hash table entries: 4096 (order: 2, 16384 bytes) [ 0.117122] TCP: Hash tables configured (established 4096 bind 4096) [ 0.117175] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 0.117197] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 0.117343] NET: Registered protocol family 1 [ 0.118138] futex hash table entries: 256 (order: -1, 3072 bytes) [ 0.121579] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.121600] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 0.122638] io scheduler noop registered [ 0.122657] io scheduler deadline registered (default) [ 0.123740] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver [ 0.124291] irq: Cannot allocate irq_descs @ IRQ34, assuming pre-allocated [ 0.124630] irq: Cannot allocate irq_descs @ IRQ66, assuming pre-allocated [ 0.125169] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00 [ 0.125186] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] [ 0.125198] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff] [ 0.125210] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.125454] PCI: bus0: Fast back to back transfers disabled [ 0.125468] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.125624] PCI: bus1: Fast back to back transfers enabled [ 0.125667] pci 0000:00:01.0: PCI bridge to [bus 01] [ 0.157477] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 0.158438] console [ttyS0] disabled [ 0.158503] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A [ 5.561615] console [ttyS0] enabled [ 5.604447] nand: device found, Manufacturer ID: 0x20, Chip ID: 0x76 [ 5.680578] nand: ST Micro NAND 64MiB 3,3V 8-bit [ 5.735875] nand: 64 MiB, SLC, erase size: 16 KiB, page size: 512, OOB size: 16 [ 5.823477] Scanning device for bad blocks [ 6.088617] 3 ofpart partitions found on MTD device orion_nand [ 6.158452] Creating 3 MTD partitions on "orion_nand": [ 6.220012] 0x000000000000-0x000000100000 : "u-boot" [ 6.317435] 0x000000100000-0x000000300000 : "uImage" [ 6.378027] 0x000000300000-0x000000800000 : "rootfs" [ 6.438627] mtd: device 2 (rootfs) set to be root filesystem [ 6.506553] mtdsplit: no squashfs found in "rootfs" [ 6.566107] libphy: orion_mdio_bus: probed [ 6.616825] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 6.699421] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:90:0b:1d:38:44 [ 7.875555] mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC address 00:90:0b:1d:38:45 [ 7.979852] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 8.058032] ehci-pci: EHCI PCI platform driver [ 8.111313] ehci-platform: EHCI generic platform driver [ 8.173993] ehci-orion: EHCI orion driver [ 8.222114] orion-ehci f1050000.ehci: EHCI Host Controller [ 8.287826] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1 [ 8.379680] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000 [ 8.465544] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00 [ 8.538073] hub 1-0:1.0: USB hub found [ 8.583164] hub 1-0:1.0: 1 port detected [ 8.630473] usbcore: registered new interface driver usb-storage [ 8.702959] mvsdio f1090000.mvsdio: Got CD GPIO [ 8.796190] NET: Registered protocol family 10 [ 8.850751] NET: Registered protocol family 17 [ 8.903960] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. [ 9.055169] Distributed Switch Architecture driver version 0.1 [ 9.126218] mv643xx_eth_port mv643xx_eth_port.0 eth0: [0]: could not detect attached switch [ 9.226304] mv643xx_eth_port mv643xx_eth_port.0 eth0: [0]: couldn't create dsa switch instance (error -22) [ 9.342075] 8021q: 802.1Q VLAN Support v1.8 [ 9.395896] mv643xx_eth_port mv643xx_eth_port.0 eth0: [0]: could not detect attached switch [ 9.495972] mv643xx_eth_port mv643xx_eth_port.0 eth0: [0]: couldn't create dsa switch instance (error -22) [ 9.611702] usb 1-1: new high-speed USB device number 2 using orion-ehci [ 9.692411] hctosys: unable to open rtc device (rtc0) [ 9.755496] Waiting 1 sec before mounting root device... [ 9.842182] mmc0: host does not support reading read-only switch, assuming write-enable [ 9.938174] mmc0: new SD card at address a9b7 [ 9.990797] mmcblk0: mmc0:a9b7 SU02G 1.89 GiB [ 10.045255] mmcblk0: p1 [ 10.076245] mv643xx_eth_port mv643xx_eth_port.0 eth0: [0]: could not detect attached switch [ 10.176360] mv643xx_eth_port mv643xx_eth_port.0 eth0: [0]: couldn't create dsa switch instance (error -22) [ 10.292709] hub 1-1:1.0: USB hub found [ 10.337809] hub 1-1:1.0: 2 ports detected [ 10.386712] mv643xx_eth_port mv643xx_eth_port.0 eth0: [0]: could not detect attached switch [ 10.486845] mv643xx_eth_port mv643xx_eth_port.0 eth0: [0]: couldn't create dsa switch instance (error -22) [ 10.825592] UBIFS error (pid: 1): cannot open "ubi0:rootfs", error -19 [ 10.902343] EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature incompatibilities [ 11.002086] EXT4-fs (mmcblk0p1): mounting ext2 file system using the ext4 subsystem [ 11.108769] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null) [ 11.198484] VFS: Mounted root (ext2 filesystem) readonly on device 179:1. [ 11.280257] Freeing unused kernel memory: 160K (c04d0000 - c04f8000) [ 11.621496] init: Console is alive [ 12.662736] init: - preinit -
|
Re: Can this device flash "Bodhi's U-boot"? November 09, 2015 05:07PM |
Admin Registered: 13 years ago Posts: 18,543 |
So did you try Uart booting with any of the new u-boot images?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Can this device flash "Bodhi's U-boot"? November 09, 2015 09:20PM |
Registered: 8 years ago Posts: 166 |
|
Re: Can this device flash "Bodhi's U-boot"? November 10, 2015 12:09AM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke Wrote:
-------------------------------------------------------
> Uart booting don't work,and I tried new u-boot
> images with openjtag,both NSA320,Sheevaplug
> uboot,no serial console output at all.
That's not good news. But since you have JTAG, it is safe to try new u-boot. If you could use JTAG to backup mtd0 and write it back, then you have a recovery path.
Do they provide GPL source somewhere? To build new u-boot, we would need it. Otherwise, you would have to backup your MTD0 and flash the closest u-boot to see if it works. If you can't find GPL source, then that's the only way, trial an error. Once you found a u-boot image that can boot then other things could be changed to make it a specific "QiZhiTong 501M V2" u-boot.
QiZhiTong 501M V2 serial bootlog:
NSA320 serial bootlog:
However,
The LAN chip is same as other plugs (eg. Dockstar, Pog E02), not the NSA320:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/10/2015 12:17AM by bodhi.
-------------------------------------------------------
> Uart booting don't work,and I tried new u-boot
> images with openjtag,both NSA320,Sheevaplug
> uboot,no serial console output at all.
That's not good news. But since you have JTAG, it is safe to try new u-boot. If you could use JTAG to backup mtd0 and write it back, then you have a recovery path.
Do they provide GPL source somewhere? To build new u-boot, we would need it. Otherwise, you would have to backup your MTD0 and flash the closest u-boot to see if it works. If you can't find GPL source, then that's the only way, trial an error. Once you found a u-boot image that can boot then other things could be changed to make it a specific "QiZhiTong 501M V2" u-boot.
QiZhiTong 501M V2 serial bootlog:
** MARVELL BOARD: MB-302 v1.0 U-Boot 1.1.4 (Nov 11 2010 - 16:09:33) Marvell version: 3.4.27 T06 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFAC0 Soc: 88F6281 A1 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 256MB DRAM CS[1] base 0x10000000 size 256MB DRAM Total size 512MB 16bit width Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done NAND:64 MB Flash: 0 kB CPU : Marvell Feroceon (Rev 1)
NSA320 serial bootlog:
** MARVELL BOARD: RD-88F6281A LE U-Boot 1.1.4 (Mar 18 2010 - 23:12:09) Marvell version: 3.4.19 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFEE0 Soc: 88F6281 A1 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 256MB DRAM CS[1] base 0x10000000 size 256MB DRAM Total size 512MB 16bit width Addresses 10M - 0M are saved for the U-Boot usage. Mem malloc Initialization (10M - 7M): Done NAND:128 MB Flash: 0 kB CPU : Marvell Feroceon (Rev 1)
However,
The LAN chip is same as other plugs (eg. Dockstar, Pog E02), not the NSA320:
88E1116 with 1 gigabit aux port
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/10/2015 12:17AM by bodhi.
|
Re: Can this device flash "Bodhi's U-boot"? November 10, 2015 10:56AM |
Registered: 8 years ago Posts: 166 |
With the openjtag,I tried the sheevaplug uboot from openwrt trunk openrt sheevaplug uboot
And here is the log(run only from ram with resume command):
I set 88E1116 ipaddr and ethaddr,but don't work,can't ping any ip.
And I found that my device have hardware CRC(or something like that), I attached the nand dump from my device,and the modified uboot image file(can run from ram use openjtag).
Thanks anyway.
And here is the log(run only from ram with resume command):
U-Boot 2014.10 (Nov 08 2015 - 02:48:12)
Marvell-Sheevaplug
SoC: Kirkwood 88F6281_A1
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: 64 MiB
MMC: MVEBU_MMC: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: egiga0
Error: egiga0 address not set.
PHY reset timed out
88E1116 Initialized on egiga0
IDE: ide_preinit failed
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Wrong Image Format for bootm command
ERROR: can't get kernel image!
I set 88E1116 ipaddr and ethaddr,but don't work,can't ping any ip.
And I found that my device have hardware CRC(or something like that), I attached the nand dump from my device,and the modified uboot image file(can run from ram use openjtag).
Thanks anyway.
|
Re: Can this device flash "Bodhi's U-boot"? November 10, 2015 12:25PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
Nice :) Try the same thing with uboot.2014.07-tld-2.sheevaplug.mtd0.kwb.
At the prompt, set your ethaddr to the right one, and then ping.
And this is normal:
Try booting the new rootfs on USB twith the uboot.2014.07-tld-2.sheevaplug.mtd0.kwb u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/10/2015 12:27PM by bodhi.
Quote
> U-Boot 2014.10 (Nov 08 2015 - 02:48:12)
> Marvell-Sheevaplug
>
> SoC: Kirkwood 88F6281_A1
> DRAM: 512 MiB
> WARNING: Caches not enabled
> NAND: 64 MiB
> MMC: MVEBU_MMC: 0
> *** Warning - bad CRC, using default environment
>
> In: serial
> Out: serial
> Err: serial
> Net: egiga0
> Error: egiga0 address not set.
>
> PHY reset timed out
> 88E1116 Initialized on egiga0
> IDE: ide_preinit failed
> Hit any key to stop autoboot: 0
Nice :) Try the same thing with uboot.2014.07-tld-2.sheevaplug.mtd0.kwb.
At the prompt, set your ethaddr to the right one, and then ping.
And this is normal:
> *** Warning - bad CRC, using default environment
Try booting the new rootfs on USB twith the uboot.2014.07-tld-2.sheevaplug.mtd0.kwb u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/10/2015 12:27PM by bodhi.
|
Re: Can this device flash "Bodhi's U-boot"? November 11, 2015 09:47AM |
Registered: 8 years ago Posts: 166 |
I tried uboot.2014.07-tld-2.sheevaplug.mtd0.kwb,still need remove data from head,and can run in ram.and also can't ping any ip when I set the ipaddr and ethaddr.
But all these images can't flash to NAND,won't boot at all(even I tried add data from nand-dump).Is there anyway to skip or crack the uboot CRC(I think)?
But all these images can't flash to NAND,won't boot at all(even I tried add data from nand-dump).Is there anyway to skip or crack the uboot CRC(I think)?
|
Re: Can this device flash "Bodhi's U-boot"? November 12, 2015 06:06PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke Wrote:
-------------------------------------------------------
> I tried
> uboot.2014.07-tld-2.sheevaplug.mtd0.kwb,still need
> remove data from head,and can run in ram.and also
> can't ping any ip when I set the ipaddr and
> ethaddr.
Some assumption we've made was not right. Please boot into stock, and capture the entire log in serial console (from u-boot banner until you can log into the stock OS).
>
> But all these images can't flash to NAND,won't
> boot at all(even I tried add data from
> nand-dump).Is there anyway to skip or crack the
> uboot CRC(I think)?
There is no need to to this. You just need the right u-boot, the Sheevaplug u-boot seems to be very close to it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> I tried
> uboot.2014.07-tld-2.sheevaplug.mtd0.kwb,still need
> remove data from head,and can run in ram.and also
> can't ping any ip when I set the ipaddr and
> ethaddr.
Some assumption we've made was not right. Please boot into stock, and capture the entire log in serial console (from u-boot banner until you can log into the stock OS).
>
> But all these images can't flash to NAND,won't
> boot at all(even I tried add data from
> nand-dump).Is there anyway to skip or crack the
> uboot CRC(I think)?
There is no need to to this. You just need the right u-boot, the Sheevaplug u-boot seems to be very close to it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Can this device flash "Bodhi's U-boot"? November 13, 2015 09:24AM |
Registered: 8 years ago Posts: 166 |
I've back to the stock.
Here is the serial console output:
And the kernel boot log from message:
Here is the serial console output:
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: MB-302 v1.0
U-Boot 1.1.4 (Nov 11 2010 - 16:09:33) Marvell version: 3.4.27 T06
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFAC0
Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz
DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:64 MB
*** Warning - bad CRC or NAND, using default environment
Flash: 0 kB
CPU : Marvell Feroceon (Rev 1)
Streaming disabled
Write allocate disabled
Module 0 is RGMII
USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME], egiga1
Hit 'Tab' key to switch the boot entry: 0
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
Device 0 @ 0 0:
Model: Hitachi HTS545025B9A300 Firm: PB2OC64G Ser#: 100513PBN2003SD6K8AT
Type: Hard Disk
Supports 48-bit addressing
Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
2724488 bytes read
## Booting image at 02000000 ...
Image Name: Linux-2.6.31.8QZT_100505_3461
Created: 2010-08-10 10:50:44 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2724424 Bytes = 2.6 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing Linux......................................................................................................................................................................... done, booting the kernel.
INIT: version 2.86 booting
Configuring kernel parameters: [ OK ]
Setting clock : Fri Nov 13 23:08:13 CST 2015 [ OK ]
Setting hostname qzt.localdomain: [ OK ]
Checking root filesystem
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/sda2
/dev/sda2: clean, 13567/262144 files, 148650/1048576 blocks
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
system has 12 partitions
start rcinit_12 ..............................
check www partition [ OK ]
check var partition [ OK ]
check var_backup partition [ OK ]
check database partition [ OK ]
check database_backup partition [ OK ]
check data partition [ OK ]
check L2 partition [ OK ]
Enabling swap space: [ OK ]
INIT: Entering runlevel: 3
Entering non-interactive startup
Flushing firewall rules: [ OK ]
Setting chains to policy ACCEPT: raw nat mangle filter [FAILED]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Setting 802.1Q VLAN parameters: [ OK ]
Bringing up interface ath0: [ OK ]
Bringing up interface bridge: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
Bringing up interface eth3: [ OK ]
Bringing up interface eth4: [ OK ]
Bringing up interface eth5: [ OK ]
Bringing up interface eth6: [ OK ]
Bringing up interface eth7: [ OK ]
Bringing up interface eth8: [ OK ]
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
Starting mpp_daemon:[ OK ]
Starting sshd:[ OK ]
Starting xinetd: [ OK ]
Starting pg: [ OK ]
Starting tomcat: execvp: No such file or directory
[FAILED]
Starting crond: [ OK ]
Starting BEAP GW daemon: [ OK ]
Starting BEAP GW daemon: [ OK ]
Starting BEAP WD daemon: [ OK ]
Starting anacron: [ OK ]
Starting watchdog:[ OK ]
the board is MB302
KuanGuang Linux release 3.4.6.7
qzt.localdomain login:
And the kernel boot log from message:
Nov 13 23:08:28 qzt syslog: syslogd startup succeeded Nov 13 23:08:28 qzt kernel: klogd 1.5.0, log source = /proc/kmsg started. Nov 13 23:08:28 qzt kernel: Cannot find map file. Nov 13 23:08:28 qzt kernel: Loaded 33140 symbols from 2 modules. Nov 13 23:08:28 qzt syslog: klogd startup succeeded Nov 13 23:08:28 qzt kernel: Linux version 2.6.31.8QZT_100505_3461 (root@localhost.localdomain) (gcc version 4.3.2 (sdk3.2rc1-ct-ng-1.4.1) ) #1 Tue Aug 10 18:50:30 CST 2010 Nov 13 23:08:28 qzt kernel: CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 Nov 13 23:08:28 qzt kernel: CPU: VIVT data cache, VIVT instruction cache Nov 13 23:08:28 qzt kernel: Machine: Feroceon-KW Nov 13 23:08:28 qzt kernel: Using UBoot passing parameters structure Nov 13 23:08:28 qzt kernel: Memory policy: ECC disabled, Data cache writeback Nov 13 23:08:28 qzt kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Nov 13 23:08:28 qzt kernel: Kernel command line: ro root=/dev/sda2 console=ttyS0,9600 mv_net_config=(00:90:0b:1d:38:45,0:1:2:3)(00:90:0b:1d:38:46,4),mtu=1500 quiet Nov 13 23:08:28 qzt kernel: PID hash table entries: 2048 (order: 11, 8192 bytes) Nov 13 23:08:28 qzt kernel: Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Nov 13 23:08:28 qzt kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Nov 13 23:08:28 qzt kernel: Memory: 256MB 256MB = 512MB total Nov 13 23:08:28 qzt kernel: Memory: 514048KB available (4812K code, 429K data, 140K init, 0K highmem) Nov 13 23:08:28 qzt kernel: NR_IRQS:128 Nov 13 23:08:28 qzt kernel: Console: colour dummy device 80x30 Nov 13 23:08:28 qzt kernel: Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776) Nov 13 23:08:28 qzt kernel: Mount-cache hash table entries: 512 Nov 13 23:08:28 qzt kernel: CPU: Testing write buffer coherency: ok Nov 13 23:08:28 qzt kernel: NET: Registered protocol family 16 Nov 13 23:08:28 qzt kernel: Feroceon L2: Enabling L2 Nov 13 23:08:28 qzt kernel: Feroceon L2: Cache support initialised. Nov 13 23:08:28 qzt kernel: Nov 13 23:08:28 qzt kernel: CPU Interface Nov 13 23:08:28 qzt kernel: ------------- Nov 13 23:08:28 qzt kernel: SDRAM_CS0 ....base 00000000, size 256MB Nov 13 23:08:28 qzt kernel: SDRAM_CS1 ....base 10000000, size 256MB Nov 13 23:08:28 qzt kernel: SDRAM_CS2 ....disable Nov 13 23:08:28 qzt kernel: SDRAM_CS3 ....disable Nov 13 23:08:28 qzt kernel: PEX0_MEM ....base e8000000, size 128MB Nov 13 23:08:28 qzt kernel: PEX0_IO ....base f2000000, size 1MB Nov 13 23:08:28 qzt kernel: INTER_REGS ....base f1000000, size 1MB Nov 13 23:08:28 qzt kernel: NFLASH_CS ....base fa000000, size 2MB Nov 13 23:08:28 qzt kernel: SPI_CS ....base f4000000, size 16MB Nov 13 23:08:28 qzt kernel: BOOT_ROM_CS ....no such Nov 13 23:08:28 qzt kernel: DEV_BOOTCS ....no such Nov 13 23:08:28 qzt kernel: CRYPT_ENG ....base f0000000, size 2MB Nov 13 23:08:28 qzt kernel: Nov 13 23:08:28 qzt kernel: Marvell Development Board (LSP Version KW_LSP_5.0.3)-- MB-302 Soc: 88F6281 A1 LE Nov 13 23:08:28 qzt kernel: Nov 13 23:08:28 qzt kernel: Detected Tclk 200000000 and SysClk 400000000 Nov 13 23:08:28 qzt kernel: MV Buttons Device Load Nov 13 23:08:28 qzt kernel: Marvell USB EHCI Host controller #0: df837740 Nov 13 23:08:28 qzt kernel: PEX0 interface detected no Link. Nov 13 23:08:28 qzt kernel: PCI: bus0: Fast back to back transfers enabled Nov 13 23:08:28 qzt kernel: bio: create slab <bio-0> at 0 Nov 13 23:08:28 qzt kernel: SCSI subsystem initialized Nov 13 23:08:28 qzt kernel: usbcore: registered new interface driver usbfs Nov 13 23:08:28 qzt kernel: usbcore: registered new interface driver hub Nov 13 23:08:28 qzt kernel: usbcore: registered new device driver usb Nov 13 23:08:28 qzt kernel: Sangoma WANPIPE Router v1.1 (c) 1995-2000 Sangoma Technologies Inc. Nov 13 23:08:28 qzt kernel: cfg80211: Calling CRDA to update world regulatory domain Nov 13 23:08:28 qzt kernel: NET: Registered protocol family 2 Nov 13 23:08:28 qzt kernel: IP route cache hash table entries: 16384 (order: 4, 65536 bytes) Nov 13 23:08:28 qzt kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes) Nov 13 23:08:28 qzt kernel: TCP bind hash table entries: 65536 (order: 6, 262144 bytes) Nov 13 23:08:28 qzt kernel: TCP: Hash tables configured (established 65536 bind 65536) Nov 13 23:08:28 qzt kernel: TCP reno registered Nov 13 23:08:28 qzt kernel: NET: Registered protocol family 1 Nov 13 23:08:28 qzt kernel: rtc mv_rtc: rtc core: registered kw-rtc as rtc0 Nov 13 23:08:28 qzt kernel: RTC registered Nov 13 23:08:28 qzt kernel: cpufreq: Init kirkwood cpufreq driver Nov 13 23:08:28 qzt kernel: XOR registered 4 channels Nov 13 23:08:28 qzt kernel: XOR 2nd invalidate WA enabled Nov 13 23:08:28 qzt kernel: cesadev_init(c000df18) Nov 13 23:08:28 qzt kernel: mvCesaInit: sessions=640, queue=64, pSram=f0000000 Nov 13 23:08:28 qzt kernel: MV Buttons Driver Load Nov 13 23:08:28 qzt kernel: JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. Nov 13 23:08:28 qzt kernel: msgmni has been set to 1004 Nov 13 23:08:28 qzt kernel: alg: No test for cipher_null (cipher_null-generic) Nov 13 23:08:28 qzt kernel: alg: No test for ecb(cipher_null) (ecb-cipher_null) Nov 13 23:08:28 qzt kernel: alg: No test for digest_null (digest_null-generic) Nov 13 23:08:28 qzt kernel: alg: No test for compress_null (compress_null-generic) Nov 13 23:08:28 qzt kernel: alg: No test for stdrng (krng) Nov 13 23:08:28 qzt kernel: alg: No test for hmac(digest_null) (hmac(digest_null-generic)) Nov 13 23:08:28 qzt kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) Nov 13 23:08:28 qzt kernel: io scheduler noop registered Nov 13 23:08:28 qzt kernel: io scheduler anticipatory registered Nov 13 23:08:28 qzt kernel: io scheduler deadline registered Nov 13 23:08:28 qzt kernel: io scheduler cfq registered (default) Nov 13 23:08:28 qzt kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled Nov 13 23:08:28 qzt kernel: serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A Nov 13 23:08:28 qzt kernel: console [ttyS0] enabled Nov 13 23:08:28 qzt kernel: brd: module loaded Nov 13 23:08:28 qzt kernel: loop: module loaded Nov 13 23:08:28 qzt kernel: Integrated Sata device found Nov 13 23:08:28 qzt kernel: IRQ 21/mvSata: IRQF_DISABLED is not guaranteed on shared IRQs Nov 13 23:08:28 qzt kernel: scsi0 : Marvell SCSI to SATA adapter Nov 13 23:08:28 qzt kernel: scsi1 : Marvell SCSI to SATA adapter Nov 13 23:08:28 qzt kernel: scsi 0:0:0:0: Direct-Access Hitachi HTS545025B9A300 PB2O PQ: 0 ANSI: 5 Nov 13 23:08:28 qzt kernel: sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512. Nov 13 23:08:28 qzt kernel: sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB) Nov 13 23:08:28 qzt kernel: sd 0:0:0:0: [sda] 0-byte physical blocks Nov 13 23:08:28 qzt kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Nov 13 23:08:28 qzt kernel: Loading Marvell Ethernet Driver: Nov 13 23:08:28 qzt kernel: o Cached descriptors in DRAM Nov 13 23:08:28 qzt kernel: o DRAM SW cache-coherency Nov 13 23:08:28 qzt kernel: o 2 Giga ports supported Nov 13 23:08:28 qzt kernel: o Multi RX Queue support - 4 RX queues Nov 13 23:08:28 qzt kernel: o Multi TX Queue support - 2 TX Queues Nov 13 23:08:28 qzt kernel: o TCP segmentation offload (TSO) supported Nov 13 23:08:28 qzt kernel: o Large Receive offload (LRO) supported Nov 13 23:08:28 qzt kernel: o Receive checksum offload supported Nov 13 23:08:28 qzt kernel: o Transmit checksum offload supported Nov 13 23:08:28 qzt kernel: o Driver ERROR statistics enabled Nov 13 23:08:28 qzt kernel: o Driver INFO statistics enabled Nov 13 23:08:28 qzt kernel: o Proc tool API enabled Nov 13 23:08:28 qzt kernel: o Gateway support enabled Nov 13 23:08:28 qzt kernel: o Using Marvell Header Mode Nov 13 23:08:28 qzt kernel: o Rx descripors: q0=128 q1=128 q2=128 q3=128 Nov 13 23:08:28 qzt kernel: o Tx descripors: q0=532 q1=532 Nov 13 23:08:28 qzt kernel: o Loading network interface(s): Nov 13 23:08:28 qzt kernel: sd 0:0:0:0: [sda] Write Protect is off Nov 13 23:08:28 qzt kernel: o eth0, ifindex = 2, GbE port = 1 Nov 13 23:08:28 qzt kernel: o Loading Gateway interface(s): Nov 13 23:08:28 qzt kernel: o Using command line network interface configuration Nov 13 23:08:28 qzt kernel: o MTU set to 1500. Nov 13 23:08:28 qzt kernel: o mac_addr 00:90:0b:1d:38:45, VID 0x100, port list: port-0 port-1 port-2 port-3 Nov 13 23:08:28 qzt kernel: o mac_addr 00:90:0b:1d:38:46, VID 0x200, port list: port-4 Nov 13 23:08:28 qzt kernel: o register under mv88fx_eth platform Nov 13 23:08:28 qzt kernel: o eth1, ifindex = 3, GbE port = 0 Nov 13 23:08:28 qzt kernel: o register under mv88fx_eth platform Nov 13 23:08:28 qzt kernel: o eth2, ifindex = 4, GbE port = 0 Nov 13 23:08:28 qzt kernel: Nov 13 23:08:28 qzt kernel: PPP generic driver version 2.4.2 Nov 13 23:08:28 qzt kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA Nov 13 23:08:28 qzt kernel: sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512. Nov 13 23:08:28 qzt kernel: PPP Deflate Compression module registered Nov 13 23:08:28 qzt kernel: PPP BSD Compression module registered Nov 13 23:08:28 qzt kernel: PPP MPPE Compression module registered Nov 13 23:08:28 qzt kernel: NET: Registered protocol family 24 Nov 13 23:08:28 qzt kernel: PPPoL2TP kernel driver, V1.0 Nov 13 23:08:28 qzt kernel: tun: Universal TUN/TAP device driver, 1.6 Nov 13 23:08:28 qzt kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> Nov 13 23:08:28 qzt kernel: Using Hamming 1-bit ECC for NAND device Nov 13 23:08:28 qzt kernel: NAND device: Manufacturer ID: 0x20, Chip ID: 0x76 (ST Micro NAND 64MiB 3,3V 8-bit) Nov 13 23:08:28 qzt kernel: Scanning device for bad blocks Nov 13 23:08:28 qzt kernel: Using static partition definition Nov 13 23:08:28 qzt kernel: Creating 4 MTD partitions on "nand_mtd": Nov 13 23:08:28 qzt kernel: 0x000000000000-0x0000000a0000 : "u-boot" Nov 13 23:08:28 qzt kernel: sda: Nov 13 23:08:28 qzt kernel: 0x0000000bc000-0x0000000dc000 : "u-boot environment parameters" Nov 13 23:08:28 qzt kernel: 0x000000100000-0x000000400000 : "uImage" Nov 13 23:08:28 qzt kernel: 0x000000400000-0x000004000000 : "root" Nov 13 23:08:28 qzt kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Nov 13 23:08:28 qzt kernel: ehci_marvell ehci_marvell.70059: Marvell Orion EHCI Nov 13 23:08:28 qzt kernel: ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1 Nov 13 23:08:28 qzt kernel: ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100 Nov 13 23:08:28 qzt kernel: sda1 sda2 sda3 sda4 < Nov 13 23:08:28 qzt kernel: ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00 Nov 13 23:08:28 qzt kernel: usb usb1: configuration #1 chosen from 1 choice Nov 13 23:08:28 qzt kernel: hub 1-0:1.0: USB hub found Nov 13 23:08:28 qzt kernel: hub 1-0:1.0: 1 port detected Nov 13 23:08:28 qzt kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Nov 13 23:08:29 qzt mpp_button: true startup succeeded Nov 13 23:08:29 qzt kernel: uhci_hcd: USB Universal Host Controller Interface driver Nov 13 23:08:29 qzt kernel: Initializing USB Mass Storage driver... Nov 13 23:08:29 qzt kernel: usbcore: registered new interface driver usb-storage Nov 13 23:08:29 qzt kernel: USB Mass Storage support registered. Nov 13 23:08:29 qzt kernel: usbcore: registered new interface driver usbserial Nov 13 23:08:29 qzt kernel: USB Serial support registered for generic Nov 13 23:08:29 qzt kernel: usbcore: registered new interface driver usbserial_generic Nov 13 23:08:29 qzt kernel: usbserial: USB Serial Driver core Nov 13 23:08:29 qzt kernel: USB Serial support registered for GSM modem (1-port) Nov 13 23:08:29 qzt kernel: usbcore: registered new interface driver option Nov 13 23:08:29 qzt kernel: option: v0.7.2:USB Driver for GSM modems Nov 13 23:08:29 qzt kernel: mice: PS/2 mouse device common for all mice Nov 13 23:08:29 qzt kernel: i2c /dev entries driver Nov 13 23:08:29 qzt kernel: sdhci: Secure Digital Host Controller Interface driver Nov 13 23:08:29 qzt kernel: sdhci: Copyright(c) Pierre Ossman Nov 13 23:08:29 qzt kernel: mmc0: mvsdio driver initialized, using GPIO 28 for card detection Nov 13 23:08:29 qzt kernel: NET: Registered protocol family 26 Nov 13 23:08:29 qzt kernel: GACT probability on Nov 13 23:08:29 qzt kernel: Mirror/redirect action on Nov 13 23:08:29 qzt kernel: Simple TC action Loaded Nov 13 23:08:29 qzt kernel: sda5 Nov 13 23:08:29 qzt kernel: netem: version 1.2 Nov 13 23:08:29 qzt kernel: u32 classifier Nov 13 23:08:29 qzt kernel: Performance counters on Nov 13 23:08:29 qzt kernel: input device check on Nov 13 23:08:29 qzt kernel: Actions configured Nov 13 23:08:29 qzt kernel: TC_HASH_LO will be loading Nov 13 23:08:29 qzt kernel: WFILTER MEM POOL NUMBER 16384 ALLOC SUCCEEDED Nov 13 23:08:29 qzt kernel: Netfilter messages via NETLINK v0.30. Nov 13 23:08:29 qzt kernel: nf_conntrack version 0.5.0 (8192 buckets, 32768 max) Nov 13 23:08:29 qzt kernel: CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use Nov 13 23:08:29 qzt kernel: nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or Nov 13 23:08:29 qzt kernel: sysctl net.netfilter.nf_conntrack_acct=1 to enable it. Nov 13 23:08:29 qzt kernel: ctnetlink v0.93: registering with nfnetlink. Nov 13 23:08:29 qzt kernel: xt_time: kernel timezone is -0000 Nov 13 23:08:29 qzt kernel: IPv4 over IPv4 tunneling driver Nov 13 23:08:29 qzt kernel: GRE over IPv4 tunneling driver Nov 13 23:08:29 qzt kernel: ip_tables: (C) 2000-2006 Netfilter Core Team Nov 13 23:08:29 qzt kernel: IPP2P v0.8.2 loading Nov 13 23:08:29 qzt kernel: WHASH MEM POOL NUMBER 8192 ALLOC SUCCEEDED Nov 13 23:08:29 qzt kernel: WHASH v0.0.3 loading Nov 13 23:08:29 qzt kernel: ClusterIP Version 0.8 loaded successfully Nov 13 23:08:29 qzt kernel: arp_tables: (C) 2002 David S. Miller Nov 13 23:08:29 qzt kernel: TCP cubic registered Nov 13 23:08:29 qzt kernel: NET: Registered protocol family 17 Nov 13 23:08:29 qzt kernel: NET: Registered protocol family 15 Nov 13 23:08:29 qzt kernel: Bridge firewalling registered Nov 13 23:08:29 qzt kernel: Ebtables v2.0 registered Nov 13 23:08:29 qzt kernel: RPC: Registered udp transport module. Nov 13 23:08:29 qzt kernel: RPC: Registered tcp transport module. Nov 13 23:08:29 qzt kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> Nov 13 23:08:29 qzt kernel: All bugs added by David S. Miller <davem@redhat.com> Nov 13 23:08:29 qzt kernel: rtc mv_rtc: setting system clock to 2015-11-13 23:08:11 UTC (1447456091) Nov 13 23:08:29 qzt kernel: sda6 sda7 sda8 sda9 sda10 sda11 > Nov 13 23:08:29 qzt kernel: sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512. Nov 13 23:08:29 qzt kernel: sd 0:0:0:0: [sda] Attached SCSI disk Nov 13 23:08:29 qzt kernel: kjournald starting. Commit interval 5 seconds Nov 13 23:08:29 qzt kernel: EXT3-fs: mounted filesystem with ordered data mode. Nov 13 23:08:29 qzt kernel: VFS: Mounted root (ext3 filesystem) readonly on device 8:2. Nov 13 23:08:29 qzt kernel: Freeing init memory: 140K Nov 13 23:08:29 qzt kernel: usb 1-1: new high speed USB device using ehci_marvell and address 2 Nov 13 23:08:29 qzt kernel: usb 1-1: configuration #1 chosen from 1 choice Nov 13 23:08:29 qzt kernel: hub 1-1:1.0: USB hub found Nov 13 23:08:29 qzt kernel: hub 1-1:1.0: 2 ports detected Nov 13 23:08:29 qzt kernel: EXT3 FS on sda2, internal journal Nov 13 23:08:29 qzt kernel: kjournald starting. Commit interval 5 seconds Nov 13 23:08:29 qzt kernel: EXT3-fs: mounted filesystem with ordered data mode. Nov 13 23:08:29 qzt kernel: kjournald starting. Commit interval 5 seconds Nov 13 23:08:29 qzt kernel: EXT3 FS on sda5, internal journal Nov 13 23:08:29 qzt kernel: EXT3-fs: mounted filesystem with ordered data mode. Nov 13 23:08:29 qzt kernel: kjournald starting. Commit interval 5 seconds Nov 13 23:08:29 qzt kernel: EXT3 FS on sda6, internal journal Nov 13 23:08:29 qzt kernel: EXT3-fs: mounted filesystem with ordered data mode. Nov 13 23:08:29 qzt kernel: kjournald starting. Commit interval 5 seconds Nov 13 23:08:29 qzt kernel: EXT3 FS on sda11, internal journal Nov 13 23:08:29 qzt kernel: EXT3-fs: mounted filesystem with ordered data mode. Nov 13 23:08:29 qzt kernel: kjournald starting. Commit interval 5 seconds Nov 13 23:08:29 qzt kernel: EXT3 FS on sda7, internal journal Nov 13 23:08:29 qzt kernel: EXT3-fs: mounted filesystem with ordered data mode. Nov 13 23:08:29 qzt kernel: kjournald starting. Commit interval 5 seconds Nov 13 23:08:29 qzt kernel: EXT3 FS on sda9, internal journal Nov 13 23:08:29 qzt kernel: EXT3-fs: mounted filesystem with ordered data mode. Nov 13 23:08:29 qzt kernel: kjournald starting. Commit interval 5 seconds Nov 13 23:08:29 qzt kernel: EXT3 FS on sda8, internal journal Nov 13 23:08:29 qzt kernel: EXT3-fs: mounted filesystem with ordered data mode. Nov 13 23:08:29 qzt kernel: kjournald starting. Commit interval 5 seconds Nov 13 23:08:29 qzt kernel: EXT3 FS on sda10, internal journal Nov 13 23:08:29 qzt kernel: EXT3-fs: mounted filesystem with ordered data mode. Nov 13 23:08:29 qzt kernel: Adding 524280k swap on /dev/sda3. Priority:-1 extents:1 across:524280k Nov 13 23:08:29 qzt kernel: Driver code for MB-301A... Nov 13 23:08:29 qzt kernel: Watchdog Driver Version 0.0.1 2009-11-19 is loaded Nov 13 23:08:29 qzt kernel: eth0: started Nov 13 23:08:29 qzt kernel: device eth0 entered promiscuous mode Nov 13 23:08:29 qzt kernel: mv_gateway: starting eth1 Nov 13 23:08:29 qzt kernel: device eth1 entered promiscuous mode Nov 13 23:08:29 qzt kernel: bridge: port 2(eth1) entering learning state Nov 13 23:08:29 qzt kernel: mv_gateway: starting eth2 Nov 13 23:08:29 qzt kernel: device eth2 entered promiscuous mode Nov 13 23:08:29 qzt kernel: bridge: port 3(eth2) entering learning state Nov 13 23:08:29 qzt sshd[1384]: Server listening on 0.0.0.0 port 22. Nov 13 23:08:29 qzt sshd: succeeded Nov 13 23:08:29 qzt xinetd: xinetd startup succeeded Nov 13 23:08:29 qzt xinetd[1396]: xinetd Version 2.3.14 started with loadavg options compiled in. Nov 13 23:08:29 qzt xinetd[1396]: Started working: 0 available services Nov 13 23:08:29 qzt rc: Starting pg: succeeded Nov 13 23:08:29 qzt tomcat: execvp: No such file or directory Nov 13 23:08:29 qzt rc: Starting tomcat: failed Nov 13 23:08:29 qzt crond: crond startup succeeded Nov 13 23:08:29 qzt gd: gwhelper startup succeeded Nov 13 23:08:30 qzt ud: updhelper startup succeeded Nov 13 23:08:30 qzt wd: wdhelper startup succeeded Nov 13 23:08:30 qzt anacron: anacron startup succeeded Nov 13 23:08:30 qzt watchdog: true startup succeeded Nov 13 23:08:30 qzt kernel: Device: 987136.0 Nov 13 23:08:30 qzt kernel: Lanner Watchdog Driver Opened Nov 13 23:08:42 qzt kernel: bridge: port 2(eth1) entering forwarding state Nov 13 23:08:42 qzt kernel: bridge: port 3(eth2) entering forwarding state Nov 13 23:08:50 qzt : normal state Nov 13 23:10:20 qzt shutdown[1499]: shutting down for system halt Nov 13 23:10:20 qzt init: Switching to runlevel: 0 Nov 13 23:10:21 qzt killall: Stopping crond: Nov 13 23:10:21 qzt crond: crond shutdown succeeded Nov 13 23:10:21 qzt killall: [ Nov 13 23:10:21 qzt killall: Nov 13 23:10:21 qzt killall: Stopping sshd: Nov 13 23:10:21 qzt sshd[1384]: Received signal 15; terminating. Nov 13 23:10:21 qzt sshd: sshd -TERM succeeded Nov 13 23:10:21 qzt killall: [ Nov 13 23:10:21 qzt killall: Nov 13 23:10:21 qzt killall: Shutting down kernel logger: Nov 13 23:10:21 qzt kernel: Kernel logging (proc) stopped. Nov 13 23:10:21 qzt kernel: Kernel log daemon terminating. Nov 13 23:10:22 qzt syslog: klogd shutdown succeeded Nov 13 23:10:22 qzt killall: [ Nov 13 23:10:22 qzt exiting on signal 15
|
Re: Can this device flash "Bodhi's U-boot"? November 13, 2015 12:50PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
From what you described, and the kernel log, it looks just like other Kirkwood boxes (sheevaplug, dockstar, nsa320,...).
1 .Your serial console log was cut off for some reason, is that all you have?
2. Is the rootfs also stock condition? it is on sda2. What is on sda1?
3. Interrupt serial console:
- ping the router or other boxes, see if you have ethernet in stock u-boot.
- And then
So your sheevaplug uboot booted in JTAG console, and the envs area is bad with crc, you can restore the internals envs by doing a
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
From what you described, and the kernel log, it looks just like other Kirkwood boxes (sheevaplug, dockstar, nsa320,...).
1 .Your serial console log was cut off for some reason, is that all you have?
2. Is the rootfs also stock condition? it is on sda2. What is on sda1?
Nov 13 23:08:28 qzt kernel: Kernel command line: ro root=/dev/sda2 console=ttyS0,9600 mv_net_config=(00:90:0b:1d:38:45,0:1:2:3)(00:90:0b:1d:38:46,4),mtu=1500 quiet
3. Interrupt serial console:
- ping the router or other boxes, see if you have ethernet in stock u-boot.
- And then
printenvto see what stock internal envs looks like
So your sheevaplug uboot booted in JTAG console, and the envs area is bad with crc, you can restore the internals envs by doing a
saveenvBy doing a saveenv, if the NAND is bad, then you will see it, if it is just a bad checksum because it was written over, then you will have restore it. It could not hurt, because it is booting with the internal default envs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Can this device flash "Bodhi's U-boot"? November 15, 2015 07:41AM |
Registered: 8 years ago Posts: 166 |
Hi bodhi,
1. The serial console log was all I have,the stock os was just made this by the O.E.M(I think).
2. sda1 is the uImage partition(monted as /boot in stock os)
3. The ping output:
The bad crc was just because I got u-boot back to stock,after I saveenv,it was just fine.
1. The serial console log was all I have,the stock os was just made this by the O.E.M(I think).
2. sda1 is the uImage partition(monted as /boot in stock os)
3. The ping output:
MB302>> ping 192.168.1.2 Using egiga0 device host 192.168.1.2 is aliveAnd the pri output:
MB302>> pri bootdelay=5 baudrate=9600 loads_echo=0 rootpath=/mnt/ARM_FS/ netmask=255.255.255.0 run_diag=yes console=console=ttyS0,9600 CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_root=mem=512M root=/dev/ram bootargs_end=:::DB88FXX81:eth0:none image_name=uImage bootcmd1=ide reset; ext2load ide 0:1 0x2000000 /uImage;setenv bootargs ro root=/dev/sda2 $(console) $(mvNetConfig) quiet;bootm 0x2000000 boottitle1=QiZhiTong Bootup bootcmd2=ide reset; ext2load ide 0:c 0x2000000 /boot/uImage;setenv bootargs ro root=/dev/sda12 $(console) $(mvNetConfig) quiet;bootm 0x2000000 boottitle2=QiZhiTong Restore password=$1$F5w1D$nzHGehkXN8JlDdjraKy1n/ bootdefault=1 bootcmd=nand read.e 0x2800000 0x400000 0x700000; nand read.e 0x2000000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root) $(mvNetConfig);bootm 0x2000000 0x2800000 standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000; ethaddr=00:90:0b:1d:38:44 ethmtu=1500 eth1addr=00:90:0b:1d:38:45 eth1mtu=1500 mvNetConfig=mv_net_config=(00:90:0b:1d:38:45,0:1:2:3)(00:90:0b:1d:38:46,4),mtu=1500 usb0Mode=host nandEcc=1bit netretry=no rcvrip=169.254.100.100 loadaddr=0x02000000 autoload=no ethact=egiga0 ipaddr=192.168.1.200 serverip=192.168.1.2 stdin=serial stdout=serial stderr=serial mainlineLinux=no enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes enaICPref=yes enaDCPref=yes sata_dma_mode=yes netbsd_en=no vxworks_en=no disaMvPnp=no enaAutoRecovery=no pcieTune=no Environment size: 1560/131068 bytes
The bad crc was just because I got u-boot back to stock,after I saveenv,it was just fine.
|
Re: Can this device flash "Bodhi's U-boot"? November 15, 2015 06:36PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
> Network:88E6161 Switch chip with 5 gigabit
> port,88E1116 with 1 gigabit aux port
If you are sure about this, then the network should work with uboot.2015.10-tld-1.sheevaplug.mtd0.kwb from the u-boot thread:
http://forum.doozan.com/read.php?3,12381
And it should boot the latest Debian rootfs on USB from the rootfs thread:
http://forum.doozan.com/read.php?2,12096
What I think you could do is to create that Debian rootfs on a USB drive (follow instruction closely), and then
- download uboot.2014.07-tld-3.environment.bodhi.tar from the u-boot thread
- extract and copy the env text file to the Debian rootfs (assuming it is mount at /media/sdb1)
- boot and load uboot.2015.10-tld-1.sheevaplug.mtd0.kwb like you did before
- interrupt serial console and
- If you like, get the listing of envs and post here to see if everything is good.
- And then
See how far it will go. Please capture serial console and post here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Network:88E6161 Switch chip with 5 gigabit
> port,88E1116 with 1 gigabit aux port
If you are sure about this, then the network should work with uboot.2015.10-tld-1.sheevaplug.mtd0.kwb from the u-boot thread:
http://forum.doozan.com/read.php?3,12381
And it should boot the latest Debian rootfs on USB from the rootfs thread:
http://forum.doozan.com/read.php?2,12096
What I think you could do is to create that Debian rootfs on a USB drive (follow instruction closely), and then
- download uboot.2014.07-tld-3.environment.bodhi.tar from the u-boot thread
- extract and copy the env text file to the Debian rootfs (assuming it is mount at /media/sdb1)
cp -a uboot.2014.07-tld-3.environment /media/sdb1/boot/uEnv.txt
- boot and load uboot.2015.10-tld-1.sheevaplug.mtd0.kwb like you did before
- interrupt serial console and
run bootcmd_uenv- After this, you should have a good set of envs to boot the Debian rootfs.
- If you like, get the listing of envs and post here to see if everything is good.
printenv
- And then
boot
See how far it will go. Please capture serial console and post here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Can this device flash "Bodhi's U-boot"? November 16, 2015 07:25AM |
Registered: 8 years ago Posts: 166 |
I've tried uboot.2015.10-tld-1.sheevaplug.mtd0.kwb,still no lucky,can't flash to the NAND,won't boot.
And I tried this uboot with openjtag,set the ipaddr and serverip,still can't ping any ip,shows ping failed(88E1116 is the wan port,aux port is in the 88E6161 Switch chip).
When I follow the instruction to create USB Debian rootfs,I can't find the "initrd.img-4.2.0-kirkwood-tld-1".
Then the output of run bootcmd_uenv:
pri output:
output of boot:
And I tried this uboot with openjtag,set the ipaddr and serverip,still can't ping any ip,shows ping failed(88E1116 is the wan port,aux port is in the 88E6161 Switch chip).
When I follow the instruction to create USB Debian rootfs,I can't find the "initrd.img-4.2.0-kirkwood-tld-1".
Then the output of run bootcmd_uenv:
Sheevaplug> run bootcmd_uenv Unknown command 'ide' - try 'help' Unknown command 'for' - try 'help' Unknown command 'do' - try 'help' Unknown command 'do' - try 'help' Unknown command 'done' - try 'help' Unknown command 'done' - try 'help' Unknown command 'if' - try 'help' Unknown command 'then' - try 'help' Unknown command 'fi' - try 'help'
pri output:
Sheevaplug> pri arcNumber=2097 baudrate=115200 bootcmd=run bootcmd_uenv; run bootcmd_usb; reset bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot; bootdelay=10 console=ttyS0,115200 device=0:1 ethact=egiga0 ethaddr=b6:d0:5e:0f:a1:17 ipaddr=192.168.1.200 led_error=orange blinking led_exit=green off led_init=green blinking mainlineLinux=yes mtdids=nand0=orion_nand partition=nand0,2 rootdelay=10 rootfstype=ext2 serverip=192.168.1.3 set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts stderr=serial stdin=serial stdout=serial uenv_import=echo importing envs ...; env import -t 0x810000 uenv_load=usb start; ide reset; setenv uenv_loaded 0; for devtype in usb ide; do for disknum in 0; do run uenv_read_disk; done; done uenv_loaded=0 uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi uenv_read_disk=if $devtype part $disknum; then run uenv_read; fi usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi usb_init=usb start usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd usb_root=/dev/sda1 Environment size: 1434/131068 bytes
output of boot:
Sheevaplug> boot Unknown command 'ide' - try 'help' Unknown command 'for' - try 'help' Unknown command 'do' - try 'help' Unknown command 'do' - try 'help' Unknown command 'done' - try 'help' Unknown command 'done' - try 'help' Unknown command 'if' - try 'help' Unknown command 'then' - try 'help' Unknown command 'fi' - try 'help' ** Bad device specification usb $device ** Unknown command 'if' - try 'help' Unknown command 'then' - try 'help' Unknown command 'else' - try 'help' Unknown command 'fi' - try 'help' resetting ...
|
Re: Can this device flash "Bodhi's U-boot"? November 17, 2015 11:57AM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
It seems something is missing in my sheevaplug build. Let me take a look and come back with a different build later. Thanks for testing it!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
It seems something is missing in my sheevaplug build. Let me take a look and come back with a different build later. Thanks for testing it!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Can this device flash "Bodhi's U-boot"? November 22, 2015 10:27PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
Please try this attached u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Please try this attached u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Can this device flash "Bodhi's U-boot"? November 23, 2015 07:09AM |
Registered: 8 years ago Posts: 166 |
I've tried the new uboot,and the 88e1116 port don't work(the port led is on,but ping faild).
I can't create the Debian rootfs on a USB drive,because there is no "initramfs-4.2.0-kirkwood-tld-1" in the "linux-4.2.0-kirkwood-tld-1-bodhi.tar.bz2",and i don't have Debian on my pc.(or if you can tell me how to compile the rootfs,i'll compile it myself).
After all,thank you very much for your work.
I can't create the Debian rootfs on a USB drive,because there is no "initramfs-4.2.0-kirkwood-tld-1" in the "linux-4.2.0-kirkwood-tld-1-bodhi.tar.bz2",and i don't have Debian on my pc.(or if you can tell me how to compile the rootfs,i'll compile it myself).
After all,thank you very much for your work.
|
Re: Can this device flash "Bodhi's U-boot"? November 23, 2015 12:12PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
You've used the wrong section to create the USB rootfs.
The kernel 3.18.5 is inside this rootfs. This is all you need for a new rootfs (and you can upgrade it later to the latest kernel 4.2, but don't need to now).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
You've used the wrong section to create the USB rootfs.
Quote
Latest kernel: linux-4.2.0-kirkwood-tld-1-bodhi.tar.bz2 (05 Sept 2015)
Latest rootfs: Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (24 Feb 2015)
Quote
Updated 24 Feb 2015:
This rootfs is the first Debian jessie rootfs in my Kirkwood kernel/rootfs release series, and to keep in sync with kernel Linux-3.18.5-kirkwood-tld-1.
The kernel 3.18.5 is inside this rootfs. This is all you need for a new rootfs (and you can upgrade it later to the latest kernel 4.2, but don't need to now).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Can this device flash "Bodhi's U-boot"? November 24, 2015 06:34AM |
Registered: 8 years ago Posts: 166 |
Hi bodhi,
I've treid the debian,and here is the boot log:
I've treid the debian,and here is the boot log:
Sheevaplug> boot
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Partition Map for USB device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 2048 3966976 00017378-01 83
loading envs from usb 0 ...
Unknown command 'load' - try 'help'
2875924 bytes read in 536 ms (5.1 MiB/s)
6535284 bytes read in 825 ms (7.6 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.18.5-kirkwood-tld-1
Created: 2015-11-24 12:25:47 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2875860 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.18.5-kirkwood-tld-1
Created: 2015-02-19 1:49:36 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6535220 Bytes = 6.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.18.5-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Thu Feb 5 17:58:07 PST 2015
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine model: Globalscale Technologies SheevaPlug
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 504784K/524288K available (5640K kernel code, 365K rwdata, 1920K rodata, 268K init, 305K bss, 19504K reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc076a240 (7561 kB)
[ 0.000000] .init : 0xc076b000 - 0xc07ae000 ( 268 kB)
[ 0.000000] .data : 0xc07ae000 - 0xc08096fc ( 366 kB)
[ 0.000000] .bss : 0xc08096fc - 0xc0855d84 ( 306 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000017] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[ 0.000420] Console: colour dummy device 80x30
[ 0.000450] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[ 0.090123] pid_max: default: 32768 minimum: 301
[ 0.090273] Security Framework initialized
[ 0.090383] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090405] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.091153] Initializing cgroup subsys devices
[ 0.091187] Initializing cgroup subsys freezer
[ 0.091222] Initializing cgroup subsys net_cls
[ 0.091244] Initializing cgroup subsys blkio
[ 0.091352] CPU: Testing write buffer coherency: ok
[ 0.091805] Setting up static identity map for 0x557418 - 0x557470
[ 0.092109] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.094615] devtmpfs: initialized
[ 0.097297] prandom: seed boundary self test passed
[ 0.101368] prandom: 100 self tests passed
[ 0.101397] pinctrl core: initialized pinctrl subsystem
[ 0.101901] regulator-dummy: no parameters
[ 0.106008] NET: Registered protocol family 16
[ 0.106478] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.130123] cpuidle: using governor ladder
[ 0.160123] cpuidle: using governor menu
[ 0.160552] Feroceon L2: Enabling L2
[ 0.160601] Feroceon L2: Cache support initialised.
[ 0.160985] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[ 0.165354] No ATAGs?
[ 0.201811] vgaarb: loaded
[ 0.202190] usbcore: registered new interface driver usbfs
[ 0.202280] usbcore: registered new interface driver hub
[ 0.202346] usbcore: registered new device driver usb
[ 0.203423] Switched to clocksource orion_clocksource
[ 0.241938] NET: Registered protocol family 2
[ 0.242689] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.242747] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.242800] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.242866] TCP: reno registered
[ 0.242880] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.242902] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.243106] NET: Registered protocol family 1
[ 0.243511] RPC: Registered named UNIX socket transport module.
[ 0.243524] RPC: Registered udp transport module.
[ 0.243531] RPC: Registered tcp transport module.
[ 0.243538] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.243810] Unpacking initramfs...
[ 0.798342] Freeing initrd memory: 6384K (c1100000 - c173c000)
[ 0.798477] NetWinder Floating Point Emulator V0.97 (double precision)
[ 0.799846] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.799879] Initialise system trusted keyring
[ 0.799979] audit: initializing netlink subsys (disabled)
[ 0.800033] audit: type=2000 audit(0.790:1): initialized
[ 0.800840] zpool: loaded
[ 0.800858] zbud: loaded
[ 0.801165] VFS: Disk quotas dquot_6.5.2
[ 0.801226] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.801838] NFS: Registering the id_resolver key type
[ 0.801881] Key type id_resolver registered
[ 0.801890] Key type id_legacy registered
[ 0.801918] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.801933] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.802158] jffs2: version 2.2. (NAND) (SUMMARY) 漏 2001-2006 Red Hat, Inc.
[ 0.802492] msgmni has been set to 998
[ 0.802657] Key type big_key registered
[ 0.805700] alg: No test for stdrng (krng)
[ 0.805744] Key type asymmetric registered
[ 0.805762] Asymmetric key parser 'x509' registered
[ 0.805856] bounce: pool size: 64 pages
[ 0.805951] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.805982] io scheduler noop registered
[ 0.805999] io scheduler deadline registered
[ 0.806059] io scheduler cfq registered (default)
[ 0.807376] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 0.808029] irq: Cannot allocate irq_descs @ IRQ33, assuming pre-allocated
[ 0.808436] irq: Cannot allocate irq_descs @ IRQ65, assuming pre-allocated
[ 0.808973] mv_xor f1060800.xor: Marvell shared XOR driver
[ 0.843515] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[ 0.883493] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[ 0.883674] mv_xor f1060900.xor: Marvell shared XOR driver
[ 0.923490] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[ 0.963490] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[ 0.963923] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.965258] console [ttyS0] disabled
[ 0.965321] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[ 1.568844] console [ttyS0] enabled
[ 1.573749] nand: device found, Manufacturer ID: 0x20, Chip ID: 0x76
[ 1.580134] nand: ST Micro NAND 64MiB 3,3V 8-bit
[ 1.584801] nand: 64MiB, SLC, page size: 512, OOB size: 16
[ 1.590316] Scanning device for bad blocks
[ 1.819006] 4 cmdlinepart partitions found on MTD device orion_nand
[ 1.825324] Creating 4 MTD partitions on "orion_nand":
[ 1.830495] 0x000000000000-0x000000100000 : "u-boot"
[ 1.835962] 0x000000100000-0x000000500000 : "uImage"
[ 1.841409] 0x000000500000-0x000002500000 : "rootfs"
[ 1.847216] 0x000002500000-0x000004000000 : "data"
[ 1.853652] libphy: Fixed MDIO Bus: probed
[ 1.858063] libphy: orion_mdio_bus: probed
[ 1.862504] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 1.869776] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 1.878184] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.884798] ehci-pci: EHCI PCI platform driver
[ 1.889333] ehci-orion: EHCI orion driver
[ 1.893562] orion-ehci f1050000.ehci: EHCI Host Controller
[ 1.899101] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 1.906966] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[ 1.923463] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 1.929702] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.936549] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.943823] usb usb1: Product: EHCI Host Controller
[ 1.948721] usb usb1: Manufacturer: Linux 3.18.5-kirkwood-tld-1 ehci_hcd
[ 1.955472] usb usb1: SerialNumber: f1050000.ehci
[ 1.960907] hub 1-0:1.0: USB hub found
[ 1.964764] hub 1-0:1.0: 1 port detected
[ 1.969602] mousedev: PS/2 mouse device common for all mice
[ 1.975857] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[ 1.982932] i2c /dev entries driver
[ 1.987767] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.993602] drop_monitor: Initializing network drop monitor service
[ 2.000129] TCP: cubic registered
[ 2.003505] NET: Registered protocol family 17
[ 2.008095] Key type dns_resolver registered
[ 2.013197] Loading compiled-in X.509 certificates
[ 2.018068] registered taskstats version 1
[ 2.023140] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 2.031695] rtc-mv f1010300.rtc: setting system clock to 2000-01-01 15:53:58 UTC (946742038)
[ 2.042429] Freeing unused kernel memory: 268K (c076b000 - c07ae000)
Loading, please wait...
[ 2.118902] systemd-udevd[55]: starting version 215
[ 2.135759] random: systemd-udevd urandom read with 3 bits of entropy available
[ 2.283602] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 2.329466] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 2.443993] usb 1-1: New USB device found, idVendor=04cc, idProduct=1520
[ 2.450752] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.474543] hub 1-1:1.0: USB hub found
[ 2.478736] hub 1-1:1.0: 2 ports detected
[ 2.483774] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 2.499420] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 2.763734] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
[ 2.876103] usb 1-1.1: New USB device found, idVendor=0bda, idProduct=0109
[ 2.883023] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.890403] usb 1-1.1: Product: USB2.0-CRW
[ 2.894539] usb 1-1.1: Manufacturer: Generic
[ 2.898825] usb 1-1.1: SerialNumber: 20090815198100000
[ 2.918171] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 2.938881] SCSI subsystem initialized
[ 2.947117] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[ 2.953852] scsi host0: usb-storage 1-1.1:1.0
[ 2.959214] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 2.968417] usbcore: registered new interface driver usb-storage
[ 2.977482] usbcore: registered new interface driver uas
[ 3.954711] scsi 0:0:0:0: Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 0 CCS
[ 3.971384] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 4.635649] sd 0:0:0:0: [sda] 3970048 512-byte logical blocks: (2.03 GB/1.89 GiB)
[ 4.643882] sd 0:0:0:0: [sda] Write Protect is off
[ 4.649381] sd 0:0:0:0: [sda] No Caching mode page found
[ 4.654844] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 4.667380] sda: sda1
[ 4.673384] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 4.683110] sd 0:0:0:0: Attached scsi generic sg0 type 0
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevd[ 14.199439] systemd-udevd[250]: starting version 215
. ok
[ ok ] Synthesizing the initial hotplug events...done.
[....] Waiting for /dev to be fully populated...[ 14.585908] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 14.684143] orion_wdt: Initial timeout 21 sec
[ 14.688729] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 14.759291] USB Power: 5000 mV
[ 14.774479] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
done.
[ ok ] Activating swap...done.
[ 15.821908] random: nonblocking pool is initialized
[....] Checking root file system...fsck from util-linux 2.25.2
/run/rootdev was not cleanly unmounted, check forced.
/run/rootdev: 14298/124160 files (6.0% non-contiguous), 137780/495872 blocks
fsck exited with status code 1
failed (code 1).
[ ok ] Activating lvm and md swap...done.
[....] Checking file systems...fsck from util-linux 2.25.2
done.
[ ok ] Loading kernel modules...done.
[ ok ] Cleaning up temporary files....
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables ...done.
[ 24.861034] NET: Registered protocol family 10
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Cannot find device "eth0"
Bind socket to interface: No such device
If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug. These pages explain the proper
process and the information we find helpful for debugging..
exiting.
Failed to bring up eth0.
done.
[ ok ] Starting rpcbind daemon....
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1149 (syslogd)
. ok
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Starting system message bus: dbus.
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1152 (klogd)
. ok
Debian GNU/Linux 8 debian ttyS0
debian login:
|
Re: Can this device flash "Bodhi's U-boot"? November 24, 2015 12:29PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
> Network:88E6161 Switch chip with 5 gigabit
> port,88E1116 with 1 gigabit aux port
>
I cannot recall if you have verified that this box actually uses the 88E1116 or not? look at the stock boot log closely, it might say another driver was used, or a different chip?
So far the sheevaplug seems very close to this box.
Did 2 SATA drives work?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 11/24/2015 12:32PM by bodhi.
> Network:88E6161 Switch chip with 5 gigabit
> port,88E1116 with 1 gigabit aux port
>
I cannot recall if you have verified that this box actually uses the 88E1116 or not? look at the stock boot log closely, it might say another driver was used, or a different chip?
So far the sheevaplug seems very close to this box.
Did 2 SATA drives work?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 11/24/2015 12:32PM by bodhi.
|
Re: Can this device flash "Bodhi's U-boot"? November 24, 2015 10:09PM |
Registered: 8 years ago Posts: 166 |
