It boots from usb-stick well: [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.15.5-mvebu-370xp-tld-2 (root@tldDebianVM) (arm-linux-gnueabihf-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #2 PREEMPT Sun Feb 27 00:00:28 PST 2022 [ 0.000000] CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10c5387d [ 0.000000] CPUby chkdsk88 - Debian
Hi bohdi, Thanks for updated images. It work like a charm. [ 13.057342] xhci_hcd 0000:01:00.0: assign IRQ: got 44 [ 13.057600] got firmware version: 2026. [ 14.601348] xhci_hcd 0000:01:00.0: enabling bus mastering [ 14.606050] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 14.612100] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1 [ 14.625800] xhci_hcby chkdsk88 - Debian
Hi bohdi, Blacklist from /etc/modprobe.d should work if you change CONFIG_USB_XHCI_PCI to '=m'.by chkdsk88 - Debian
bodhi Wrote: ------------------------------------------------------- > chkdsk88, > > I lost the USB 3.0 port (MVEBU XHCI controller) on > the Mirabox with the kernel configured with > CONFIG_USB_XHCI_PCI_RENESAS=m. > Does it work with =y? > Blacklisting in /etc/modprobe.d seems to be too > late. I'll try the bootargs to see if it will make > any dby chkdsk88 - Debian
bodhi Wrote: ------------------------------------------------------- > > There is one issue: PCIE doesn't reset > properly. > > It works on Openwrt 5.10 kernel: > > Quote[ 3.696353][ T1] armada-370-pinctrl > d0018000.pin-ctrl: unsupported function gpio on > pin mpp59 > [ 3.696370][ T1] pinctrl core: failed to > register map default (0):by chkdsk88 - Debian
There is one issue: PCIE doesn't reset properly. [ 3.540933][ T1] armada-370-pinctrl d0018000.pin-ctrl: registered pinctrl driver [ 3.549228][ T1] mvebu-pcie soc:pcie@82000000: host bridge /soc/pcie@82000000 ranges: [ 3.549297][ T1] mvebu-pcie soc:pcie@82000000: MEM 0x00d0040000..0x00d0041fff -> 0x0000040000 [ 3.549332][ T1] mvebu-pcie soc:pcie@8200000by chkdsk88 - Debian
My post is only supplement for complete instruction created by bohdi. How to install: (example created for Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi and linux-5.10.7-mvebu-370xp-tld-1-bodhi.tar.bz2, for newer version please adjust numbers) Steps different than regular procedure are bold. PLEASE REMEMBER TO USE mvebu-370xp SPECIAL KERNEL VERSION! For install and for update. Quotebohdi (by chkdsk88 - Debian
Ctera C200 V1 with bootloader replacement was described here: https://forum.doozan.com/read.php?2,128064 My post is only supplement for complete instruction created by bohdi. It shows how to install Debian on Ctera with original (locked) u-boot. This is solution for people, who want to stay with factory bootloader. How to install: (example created for Debian-5.13.6-kirkwood-tld-1-rootfs-bodby chkdsk88 - Debian
bodhi Wrote: ------------------------------------------------------- > > So the error was just artifact of the serial > console connected? or was it real? > Serial console causes wrong initial nand configuration. The error was an artifact. It vanish without serial adapter connected.by chkdsk88 - uBoot
It was the most stupid problem with hardware ever: UART adapter hold `Boot source[4]` in wrong state...by chkdsk88 - uBoot
hurricos Wrote: ------------------------------------------------------- > Relevant OpenWrt forum thread: > > https://forum.openwrt.org/t/adding-openwrt-support-for-ctera-c200-v2/113042 > > @chkdsk88, tomorrow I will pass by the Lab and use > `md` to dump the entire contents of NAND from my > Ctera C200 V2 (and provide the u-boot script I > used to do so). >by chkdsk88 - uBoot
Hi everybody. I have Ctera C200 V2 device. It's based on Marvell 88F6707. I got the device with invalid bootloader flash image. It fall into bootloop: BootROM 1.08 Booting from NAND flash BootROM: Invalid header checksum BootROM: Bad header at offset 00010000 BootROM: Bad header at offset 00020000 BootROM: Bad header at offset 00030000 BootROM: Bad header at offset 00040000 Boby chkdsk88 - uBoot