Kernel linux-6.8.7-kirkwood-tld-1 package has been uploaded. See 1st post for download link. And please create a new thread for any installation problem or question.by bodhi - Debian
> I'm currently preparing a complete guide that I > will post here in a few days. There are few other > minor quirks > I didn't mention previously that I will sum up in > it, such as the fact that the stock u-boot only > detects drives in the DISK 2 bay, even with an > appropriate config. 26 GPIO0 26 OUTPUT HIGH HDD1 power enable.by bodhi - Debian
@primuspaul, > Is there a comprehensive guide, step 1 to end, on > how to install a Linux distribution on a 3020? No we don't, atm. This is where you should start reading: https://forum.doozan.com/read.php?2,134563,137251#msg-137251by bodhi - Debian
> Will this work? > https://www.ebay.com/itm/355519965973 That looks OK, it's the right chip. But as with any cheap serial converter module from eBay, you'd have to try to know for sure. If it does not work, see in the Wiki thread: Quote Unbricking with Serial Console & JTAG console How to unbrick your box using serial console with kwboot .... Serial Port connby bodhi - Debian
@Robin, > It just works > > I followed your procedure with the stock kwboot of > my debian 12 PC and it worked fine. I had to keep > the power button pressed until kwboot stated > loading. Any other way to power on the NAS ended > up in a normal boot, ignoring kwboot. Cool! that's a quirk worth knowing, will save people time trying to run kwboot. I'mby bodhi - Debian
Kwboot with stock mtd0 1. Dumping mtds dd if=/dev/mtd0 of=mtd0.ds216 bs=1024k conv=sync dd if=/dev/mtd1 of=mtd1.ds216 bs=7040k conv=sync dd if=/dev/mtd2 of=mtd2.ds216 bs=64k conv=sync dd if=/dev/mtd3 of=mtd3.ds216 bs=64k conv=sync 2. kwboot - Here is an example of running kwboot. - Download the latest kwboot here. Eventhough the kwboot comes with your Linux host distro is adequatby bodhi - Debian
> It works perfectly. > We can check if kwboot works indeed. But as I have > the required tools to dump or flash the SPI NOR in > place, it's not that risky for me to edit things > to oblivion. Cool! Let's dump the mtds first to back it up and use for kwboot.by bodhi - Debian
Looks like you are using a wrong tutorial. This is what we are using here: https://linux-mmp.docs.kernel.org/dell-wyse-3020.html And in this thread, this is the post you should start from: https://forum.doozan.com/read.php?2,137328,137330#msg-137330by bodhi - Debian
u-boot envs in Linux. Power up, interrupt u-boot countdown and, setenv mtdparts 'mtdparts=spi0.0:1m(u-boot),7040k(kernel),64k(u-boot-env),-(data)' Boot into Debian and - Check the mtd layout cat /proc/mtd - modify /etc/fw_env.config cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors # DS216 /dev/mtd2 0x000by bodhi - Debian
Severuspiton99, > I tried but when i tried to get to kwboot nothing > happens. What could It be? There are a few reasons. It could be that your serial connection is wrong (which is not the case here because you've used serial console before), or the kwboot version you are using is old and cannot handshake with this box BootROM successfully. Post what is the u-boot image (wheby bodhi - Debian
@Robin, > Just a quick message to say that I dug a bit into > the DS214 DTS and found several issues. The most > important one probably being the RAM set to 1GB > instead of 512MB. While it's good to fix that RAM size, what's in the DTS should not impact how the kernel determines the RAM size. The RAM size is determined by u-boot and the kernel use that info, and igby bodhi - Debian
@Robin, Thanks for the envs and boot log. And I've looked at the DTS. Looks very good! The only nit I have is the indentations, some are spaces where they should be tabs (not relevant for our purpose here, though). I'll be back tomorrow to post more details about u-boot envs.by bodhi - Debian
primuspaul, See this thread, beggining here: https://forum.doozan.com/read.php?2,134563,137251#msg-137251 And post your questions there too.by bodhi - Debian
Robin, Sorry I was not clear. What I'd like to see is your current envs and how it boots. But the stock envs are also good to have, too. ==== These are how the USB 3.0 ports were activated in stock u-boot (no need to poke the memory). usbActive=0 usbType=2 So, setenv usbActive 1 setenv usbType 3 But your finding about what GPIOs to set is great info.by bodhi - Debian
> Just a question: the image i used Is not in .kwv, > like i saw in the other post. Why? Should ut be? No matter, currently you only want to be able to try to load and run with kwboot over UART (it's a non-destructive test). But when you flash it, it must be a flash-ready format. Sometime it is .bin, sometime it is .kwb, depending on who built the u-boot image.by bodhi - Debian
> I made a lot of minor edits to my DTS file, the > latest one is attached to this post. > I listened to your advice and tested the fan > speeds carefully, LSB and MSB were swapped so I > fixed it in no time. > Everything seems to work fine when it comes to > hwmon, and even though the LED config is not the > way we would like it to be, it's probably the mostby bodhi - Debian
Hi Robin, > There is absolutely no EEPROM chip on this board > whatsoever, and the i2c-0 bus is most likely > unused. The bus experiencing locks all the time, I > decided to remove the whole i2c-0 + EEPROM node. Cool! > This is something that is more related to u-boot > than the core subject of this topic, but I prefer > to write a small paragraph about it withby bodhi - Debian
HDD LEDs Since you have found this in the GPL: 9 GPIO0 9 OUTPUT HIGH Enable HDD LEDs. But there is no GPIO for HDD1 or HDD2. It looks like the HDD LEDs are not individually controlled. As I recalled (badly), some Synology boxes are like this (it's how the board layout was designed, not that they could not do it). So add another led node similar to what you did foby bodhi - Debian
Severuspiton99, Quotei don't think i did, it's my first time with this kinda things. Should be something with kwb extension? is the backup unique for any machine or maybe i could take the backup for the ex2 ultra from someone? Yes, you can use the mtd0 backup for the EX2 Ultra from other box. Or use the same binary that you use for the bubt command. Quotei just used bubt commanby bodhi - Debian
Hi Robin, Great job with the DTS! > Here are my current DTS and > bootlog, if you find something i may have missed > i'm all ears ;-) The boot log looks very good! Here is my comment on the DTS so far. FAN The new binding for fan speed now has each speed in the map inside brackets. This is a recent change in the DT binding (old style still work, though). For examby bodhi - Debian
Severuspiton99, > guys i need help, i'm not able to use minicom > anymore, nothing happens when i connect the nas. I > think a herror happened when i flashed the boot > image, cause now i cant do nothing. Please i > really need your help Before you flashed u-boot image, did you back up the mtds? especially mtd0? If you keep the log of what you did to flash u-boot, plby bodhi - Debian
@tmn505, > @bodhi I have few patches You might be interested > in and cleaned up the dts, these are not tested > with T50, so validity of changes in PCIE and SD > CARD node need to be confirmed. > https://github.com/tmn505/openwrt/tree/dove/target/linux/dove Thanks! I'll take a look.by bodhi - Debian
Robin, > > compatable = "marvell,neta"; Yes, you can take out the compatible property. It was a left over from the old style binding. There is no need to do this for Armada 385 SoC boards. And most likely that typo has screwed up the hwmon! > > ethernet@34000 { And yes, remove this 2nd ethernet node ethernet@34000.by bodhi - Debian
> I think most of the issue is related to GPIO > conflicts and/or bad definitions. I'll get back > into this when debian will run a kernel with my > edited DTB. Bad definition. > LEDs AND GPIOs > > Okay so after a bit of trial and error, and time > spent digging into the Synology GPL tarballs > (especially synobios.txz), I finally determined > tby bodhi - Debian
Robin, I already read this post before you edited it. So I did not realize there was new info until I happen to browse previous posts (if I don't see the new post flag, I don't read it). > I started to look at the DTS of the DS218j and > DS116 and found something i'm not sure about. In > "armada-385-synology-ds218j.dts" one can read: > >by bodhi - Debian
Quotebodhi > > Both front buttons do nothing in debian. I > don't > > fully understand how those should be declared > in > > the DTS files, any hints ? > > Look in my patch linux-6.7.5-mvebu-tld-1.patch in > the > tarball > linux-6.7.5-mvebu-tld-1-bodhi.tar.bz2. And > find the armada-385-thecus-n2350.dts. There are 3 > buttons definedby bodhi - Debian
> HWmon > hwmon2 does not exist. It seems like > hwmon1/temp1_input is the SoC temperature, and i'm > not sure hwmon0/temp1_input is working as the > value stays the very same. No fan input so far... That's strange. There should be 3 hwmons. CPU, Fan, and Ethernet. But the order is not guaranteed to be the same for different boards. For example, the DS116: lsby bodhi - Debian
> > So does the power button work OK? > > > No wont work right now but i sorted some other > problems out Yeah, it's nice to have button, but not too important. > Like transferrate > I now get about 38mb/s both ways using XFS > filesystem on both drives > > And im able to boot reliable without errors Cool! > But the problem with thby bodhi - uBoot
Robin, > Thanks for your quick reply. The original RTC > battery was dead, I replaced it before the first > boot and I didn't set the time since. I'll check > tomorrow but it's probably nothing to be concerned > about. OK. > > I felt like the SPI flash issue was indeed minor, > if LEDs and Buttons requires us to edit a separate > DTS forby bodhi - Debian
In any case, we should stop discussing hdd temp here before it gets out of topic of this thread.by bodhi - Debian