@sym0, > registered as rtc0 > [ 92.625677][ T176] rtc-ds1307 0-0072: hctosys: > unable to read the hardware clock > [ 92.633382][ T176] i2c i2c-0: new_device: > Instantiated device ds1307 at 0x72 OK that's good to know. Now try: Boot with serial console connected. Interrupt count down and set the date date # or help date date <current time>by bodhi - Debian
What's the content of: cat /sys/firmware/devicetree/base/ocp@f1000000/i2c@11000/rtc@64/compatible cat /sys/firmware/devicetree/base/ocp@f1000000/i2c@11000/rtc@64/nameby bodhi - Debian
The kernel does not have driver for IDT 1337G chip (quite common for older chips that nobody has tried to mainline). Hopefully we can use the Dallas/Maxim ds1307 driver, which was known to work for some other chips other than Dallas/Maxim's. Attached is the updated dtb/dts.by bodhi - Debian
Koinin, > However, as expected, if the system fails to > boot (e.g. issues in initramfs or mounting root), > I do not get any kernel logs via netconsole — > since the module hasn’t been loaded yet. > I want to receive early kernel logs over > netconsole — as early as possible — ideally > starting right after U-Boot, even before the > rootfs is mounted.by bodhi - Debian
> I think that first we need to try to understand > the mechanism of interaction with RTC on 3.2.40. It is well defined in the modern kernel, we just need to do the right thing in the DTS. Since this box uses the external RTC we need to disable the internal RTC in the SoC.. Attached is the updated dtb/dts.by bodhi - Debian
sym0, Perhaps you should install and run my kernel linux-6.14.6-kirkwood-tld-1. See if there is any difference.by bodhi - Debian
> On 6.14.8 it doesn't find the I2C adapter... > > I also tried to compile kernel 3.2.40 with the > "modular" driver mv64xxx_i2c (it does not load > automatically). Don't need to do that. The kernel should already have i2c. We just need to enable it. > The boot log had typical errors, but RTC worked > fine (I checked it via /usr/sbin/rtc). Soby bodhi - Debian
> Now that I see > root=LABEL=rootfs works > reliably, I’ll stick with it. Cool!by bodhi - Debian
Koinin, > I'm using a GoFlex Home with U-Boot 2017.07 > installed following your instructions, and I've > successfully booted into Debian from a USB drive. Cool! > Other times the USB becomes > /dev/sdb1 → boot fails > because the kernel can't find the rootfs > > I have already tried using > UUID in > bootargs, but it did not >by bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > This is suspect, might be wrong. > > > mww 0xD0010418 0x003E07CF ;# NAND Read Parameters > REgister > mww 0xD001041C 0x000F0F0F ;# NAND Write Parameters > Register > mww 0xD0010470 0x01C7D943 ;# NAND Flash Control > Register > I've verified they are correct.by bodhi - uBoot
This is suspect, might be wrong. mww 0xD0010418 0x003E07CF ;# NAND Read Parameters REgister mww 0xD001041C 0x000F0F0F ;# NAND Write Parameters Register mww 0xD0010470 0x01C7D943 ;# NAND Flash Control Registerby bodhi - uBoot
Some thoughts. The fan might be on the i2c (if not an GPIO fan), as well as the RTC chip. I don't think the IDT 1337G driver is supported in the kernel. It is on i2c bus.by bodhi - Debian
Quote> I found out that the board uses IDT 1337G (photo). > However, in the iomem output for 6.14.8 I do not > see any mentions of rtc-mv and mv64xxx_i2c > (perhaps they are called differently?). Interesting. Let me take a look at the DTS (please do the same). The RTC must be specified in the i2c node in the DTS. Yes, we are missing this RTC.by bodhi - Debian
Hi sym0, Thanks for your contribution! they are very good. > - NAND: > > 1) I had to change the "chip-delay" value from 25 > to 35, because during boot, errors were pouring > into dmesg for 10 seconds: Yes. This happens frequently with Kirkwood boxes, and we need 35 or 40 chip-delay. > 2) The original MTD markup has 7 sections, not 2: > > [by bodhi - Debian
shermbug, While we are waiting for joerg to chime in about the NAND write error, here is my next recommendations. 1. The example in the 1st post is for the Pogo E02 which uses the 88F6281 SoC. The Pogo V4 uses the 88F6192 SoC. The CPU is running at a different speed, and the TCLK is also different. And I am almost certain the register values are different (I have not looked in the 88F6192 Rby bodhi - uBoot
Hi shermbug, I do rely on joerg to provide helps on this subject. I'm very rusty about JTAG. I played with it at my job more than 10 years ago, and probably need to relearn it like you are doing!by bodhi - uBoot
ksuszka has info about recovery here: https://forum.doozan.com/read.php?2,134563,137486#msg-137486by bodhi - Debian
mmm has tried here: https://forum.doozan.com/read.php?2,134563,136711#msg-136711 Gravelrash has tried here: https://forum.doozan.com/read.php?2,134563,135491#msg-135491 That is how you flash boot loader to SPI (with flashcp). But unfortunately it did not work.by bodhi - Debian
Phaze Henot, > Has any > progress been made on flashing the SPI from within > Linux? I would like to attempt flashing one of > Ksuszka's firmware dumps to see if this solves the > issue. I have not looked into how to flash this boot loader in Linux. I need a recovery mechanism before I'd try flashing Ksuszka's firmware dumps. Not sure if we've figuredby bodhi - Debian
Attached here is the June 02 build. This build has some PCIe debug output intended for the DS112. Tests: Large HDD >2TB and 2nd SATA bay. uboot.2024.10-tld-1.ds211.bodhi.250602.tar md5: 1d76463da262910dc1601564be97dd77 sha256: e030248e75ee021b566b1e4ce83d15494b3b33aa939682064342cc99523b1bb1 This tarball contains 5 files. Ony the image uboot.2024.10-tld-1.ds211.kwb is different frby bodhi - uBoot
> I was confused by "stock u-boot" as I thought that > was referring to original bootloader (aka not > u-boot :) ). Now re-reading instructions it makes > sense! These ARM boxes use u-boot as boot loader. "Stock u-boot" means to say what the manufacturer installed, usually very old (circa 2012 ) and very limited in capability. Some ARM boxes also use barebby bodhi - Debian
Man, > I installed ksmb instead of smb/samba, and it's > MUCH faster, saturating my AC wifi at 70MB (and > possibly close to Gb on ethernet, which I can't > test atm since I'm about to leave for vacay). > Maybe you should start including this module in > your kernels Bodhi? A lot of devices will see a > great speed increase. Sounds good! I'llby bodhi - Debian
shadowpho, It's a classic problem when you are booting with stock u-boot envs vs with the env image that comes with the new u-boot. When you installed new u-boot 2023.04-tld-1, you are supposed to boot with the separate DTB, as its default envs are set up to do so. But, since you set up the boot with OpenWrt, you treated it like OpenWrt and successfully booted. Now when you are switby bodhi - Debian
Attached here is the new u-boot build for Synology DS112. This is a PCIe debug build. I could not see where the bug is, so I need to get some info at the most likely place. uboot.2024.10-tld-1.ds112.bodhi.250601.tar md5: 08a288d75acc667bed535cc973416eef sha256: 2580ea7cb873b7425e3da3a786648cc541ac9fd5a22d5d538cb2ef1c6ea6c851 This tarball includes 5 files uboot.2024.10-tld-1.ds112by bodhi - Debian
Navi , > > busybox-syslogd > > was also automatically installed during the > upgrade. Yes. It's already installed in the basic rootfs. > Used > apt-get install dphys-swapfile > > command and then adjusted the swap factor in > > /etc/dphys-swapfile > > to 4. > CONF_SWAPFACTOR=4 > This box is too low in memory, only 128MBby bodhi - Debian
BayPanard, > Again sorry for the delay i'm struggling finding > time to test and answer :-( Don't worry, what we do here is not high priority, take your time :) > I'll take a look at the sources and i'll share any > findings here. The issue is why the PCIe links are down. And your test was pretty good, it gave me some clue: U-Boot 2024.10-tld-1by bodhi - Debian
Koinin, > I'm installing the latest Debian rootfs > (Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2) > on my GoFlex Home, and everything seems to boot > successfully from USB > sudo tar -xjf > Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > -C /mnt/usb You must be root, sudo won't work. https://forum.doozan.com/read.php?2,12096 QuoteNote: alby bodhi - Debian
And remember to do this so the USB rootfs will not wear out prematurely. https://forum.doozan.com/read.php?2,13702,13704#msg-13704by bodhi - Debian
Hi Navi, Welcome back, hope all is well too! > 2) This time I plan to keep booting from USB pen > drive and use the new HDD just for DATA. I will > also make a clone copy of the USB pen drive for > emergency use. That's how I run my GF Homes for many years. > Therefore the Questions I have are: > > (1) Since I already have your UBoot (2017-07) > inby bodhi - Debian
BayPanard, > > # GPIO for internal HDD power on > #################################### > static void > KW_6282_112_GPIO_init(SYNO_KW_GENERIC_GPIO > *global_gpio) > { > KW_6282_211_GPIO_init(global_gpio); > global_gpio->hdd_pm.hdd1_pm = 30; > } > > > # Global GPIO > ##################### > static void > KW_6282_211_GPIO_iby bodhi - Debian