Jáder, > TTL directly to USB in something like this > https://www.mercadolivre.com.br/modulo-conversor-usb-20-p-rs232-ttl-uart-5-pinos-cp2102/p/MLB35506431#polycard_client=search-nordic&wid=MLB3714413881&sid=search&searchVariation=MLB35506431&position=3&search_layout=grid&type=product&tracking_id=52fa0d3d-2481-4408-bd71-9ff96f3a158b That's the correby bodhi - Debian
> What to do now? May I move forward without a > usable original OS ? > May I boot from new USB pendrive and had it > working? Yes. It is best to boot from USB rootfs. Once it is working, you can move the rootfs to the internal 16GB SSD, if you want to. You don't need the original OS. > (tomorrow I'll try to get a serial cable from a > spare part store)by bodhi - Debian
Gabriel, It's in the Wiki thread https://forum.doozan.com/read.php?2,23630 Quote Kirkwood plugs Basic steps to install Debian and new u-boot on Kirkwood boxes Boot Kirkwood rootfs with stock u-boot Since we don't have new u-boot for this box, the box must be booted with stock u-boot. If OpenWrt has new u-boot, and you have installed it, still treat it as stock u-boot.by bodhi - Rescue System
> So it might've been an oversight by me by not > giving the box enough power, but I was unable to > get a stable kwboot previously, which made me skip > trying to use the power supply in the first > place. The moral of the story is that old hardware tend to have bad power supply! when all remedies fail, check it. > > I've went through the uboot flashingby bodhi - Debian
> I'm thinking the nand is flaky or there's some > other hardware issue because I still have > problems; For example using JTAG most of the times > I get an "unknown NAND flash device found, > manufacturer id: 0x00 device id: 0x00" error. OK. I'm convinced that this box's NAND is bad. > But the good Dockstar hasn't got the original fby bodhi - Rescue System
Jáder, Use this tarball: Latest released rootfs: Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (01 Nov 2023) > When tryiing to follow the section > B. Installation without serial console of > https://forum.doozan.com/read.php?2,61344,90019#msg-90019 > on step about to use mkimage binary it tell me one > of those options: > 1) there are no such file > 2) ifby bodhi - Debian
Jáder, Did you foloow the installation instruction here? https://forum.doozan.com/read.php?2,61344,90019#msg-90019 Also connect serial console. Installation is a lot easier if you have serial console.by bodhi - Debian
bluzfanmr1, > It was 100% my issue and nothing where you stopped > helping or forgot anything and I didn't mean to > imply that and I'm sorry if it sounded that way.. Oh, no worries, I did not take it that way at all! In fact, there was a recent period when I was very busy so I just gloss over a lot of posts, and only payed attention to the hard ones (eg. bricked boxes)by bodhi - Debian
cdlenfert, > Using an Ext3 formatted drive worked for booting. Cool! > I'm probably OK sticking with this, but any ideas > why Ext4 would fail when Ext3 works. I also used a > different device and tool to format as Ext4, but > the same tool made a bootable Ext4 drive for my > Pogo V4. Hard to tell why withthout serial console.by bodhi - Debian
bluzfanmr1, >I believe there's a few posts here > where we attempted to get it to work, but I never > was able to get it working. I've just stayed at > 4.14.198-oxnas-tld-1 so I can use it. I probably forgot all about those posts, must have been while I was very busy :) If you want to try again, please do so. I always boot and run new kernel and rootfs for a fewby bodhi - Debian
cdlenfert, You can solve it with serial console.by bodhi - Debian
cdlenfert, It would have been easier if you had a rootfs backup that you can restore from. And then look at the current one to fix any possible problem. > When I plug the fresh rootfs in, and power it on, > the light alternates between solid yellow, a > series of a couple/few yellow rapid flashes, then > exactly 6 slower orange flashes. It means the kernel has not completby bodhi - Debian
Zasshi, > Will the attached file do? I assume the log was the boot log from the bricked unit. And you have installed the new u-boot on NAND and can boot USB Debian rootfs with it. The problem now is: the new u-boot cannot boot the old stock FW. So to go back to factory, you also need to flash back stock u-boot. If you had waited for my instruction, you could have saved a lot ofby bodhi - Rescue System
SimonMcS, > So it seems like the USB controller is bugged in > some way, like you said. > Is booting from the SATA backplane an option? I'd > like to avoid flashing and booting from NAND, but > if that's an option, I wouldn't mind trying it > out. Yes, it's best to move on to booting with SATA rootfs. Also avoiding booting from NAND too, it'sby bodhi - Debian
SimonMcS, Please use Kingston Traveller USB 3.0 flash drive while testing. Make sure you do the EXT4 file system finalization (see dhargens reminder above). But as I saw you mentioned that you've tried Ext3 unsuccessfully too. Also, you've did not label the partition as rootfs (this is reason for kernel panics). Here is the correct format command for Ext3 and Ext4 rootfs. mby bodhi - Debian
SimonMcS, > I've never been able to boot into a Debian prompt. > There has always been a kernel panic, This has nothing to do with u-boot. The kernel panic has something to do with your USB rootfs. For example, you did not label the partition as rootfs, or not being root user when extracting the tarball. > freeze/crash when scanning the drive, or an EHCI > timeoutby bodhi - Debian
Zasshi, Your NAND is not damaged. > You wrote that I should post the log "from u-boot > banner until the box stop booting", and that's > what I posted. I'm very precise. I've asked to see the complete log after you loaded the image from tftp, and run 2 commands: printenv boot The list of all current envs (output of printenv) is what I'm lookinby bodhi - Rescue System
Please do exactly what I asked above QuoteWith serial console connected, power up and interrupt the count down. At u-boot prompt, printenv If you have saved the envs previously then go ahead, boot. If not, repeat what you done to prepare the envs for booting, and then boot. boot Post the entire serial console log here. Don't post excerpt, I need to see the whole log (what you enteby bodhi - Rescue System
Zasshi, With serial console connected, power up and interrupt the count down. At u-boot prompt, printenv If you have saved the envs previously then go ahead, boot. If not, repeat what you done to prepare the envs for booting, and then boot. boot Post the entire serial console log here. Don't post excerpt, I need to see the whole log (what you entered at u-boot prompt, and the logby bodhi - Rescue System
Zasshi, > I managed to recover the "dead unit" bootloader > and now I can boot to Linux. > How should I proceed to re-install the original > firmware? You reinstall the original firmware in the steps below. The boot loader is apparently fine if you can do these steps. > > I found these steps on the Goflexnet Openwrt > wiki: > > #set goflex neby bodhi - Rescue System
Vadim_Boev Wrote: ------------------------------------------------------- > QuoteNo. u-boot is the boot loader. You are not > writing > the u-boot commands to the Debian rootfs. In the > instruction > > I'm sorry, apparently I didn't express myself > correctly. I mean, I need the right instructions > for working with a USB flash drive, maybe I wrote >by bodhi - Debian
> Okay, as soon as I find the SanDisk USB stick, > I'll start. I would like to know what size a usb > flash drive should be? 2 GB? 4 GB? 8 GB? 16 GB? I would use 16GB, because Debian tends to growth. 16 GB will be good for a while before you need to migrate to larger disk. > And also, since I'm not at all sure that I wrote > the data to U-Boot correctly, could yoby bodhi - Debian
> U-Boot 2011.06 (Jan 03 2013 - 16:19:06) > Promwad-ThinClient > Marvell>> usb start > (Re)start USB... > USB: Register 10011 NbrPorts 1 > USB EHCI 1.00 > scanning bus for devices... 3 USB Device(s) found > scanning bus for storage devices... EHCI > timed out on TD - token=0x248d80 > EHCI timed out on TD - token=0x80008d80 > 1 Storage Deby bodhi - Debian
Vadim_Boev, Loading file "/boot/uImage" from usb device 0:1 (usbda1) ** File not found /boot/uImage Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) ** File not found /boot/uInitrd These errors mean u-boot could not find the kernel images. This usually happens if the USB partition was formatted as Ext4 and not "finalized". But you have verified thaby bodhi - Debian
Vadim_Boev, QuoteI tried to update the u-boot and Debian firmware based on these instructions: 1. Linux Kernel 6.9.6 Kirkwood package and Debian rootfs (Updated 01 Nov 2023:) 2. Boot Kirkwood rootfs with stock u-boot If you have kept the log of what you did in creating the rootfs (1), and also the u-boot booting (2), including all setenvs commands, please post them here. QuoteI do notby bodhi - Debian
Indeed a good deal. Hope it is still in stock when I can get to it. Thanks David!by bodhi - Off-Topic
These are the kernel files, so they have the build date, except for initrd file. They were generated by dpkg -i linux-image-6.9.6-kirkwood-tld-1_1_armel.deb -rwxr-xr-x 1 root root 6.0M Jun 21 15:33 vmlinuz-6.9.6-kirkwood-tld-1 -rw-r--r-- 1 root root 197K Jun 21 15:33 config-6.9.6-kirkwood-tld-1 -rw-r--r-- 1 root root 4.4M Jun 21 15:33 System.map-6.9.6-kirkwood-tld-1 -rw-r--r-- 1 roby bodhi - Debian
Cont. 5. And then after logging to Debian, flash stock Dockstar firmware. It is also possible to do the flashing while in serial console, and at u-boot prompt.by bodhi - Rescue System
There are 4 possible unbrick steps (1 is easiest). 1. Take your USB rootfs to another Linux and run e2fsck to check for errors and fix it. Bring it back to the dockstar and try booting it. 2. If you remmember what u-boot was installed, and what Debian rootfs is on the USB, (or what procedure you used to install), then we could try booting a rootfs that matches what this u-boot expects. 3by bodhi - Rescue System
Zasshi, How "bricked" is your Dockstar? do you have serial console, and if you do when you power up do you see u-boot booting activities? Post the boot log.by bodhi - Rescue System