Apparently @kingyond trashed their recovery partition and is looking for an mtddump (they sent me a PM): Quotekingyond I don't konw if i make the "rescue fw" mtd part corrupt. it cannot boot into rescue mode. would you please dump the mtd part and send me the bin file. thanks very much. I don't own this device, but maybe someone here could assist?by hmartin - Debian
bodhi, do you know the u-boot config option for the map command? Is this perhaps a vendor specific command, added to a fork of u-boot? I've searched several times for map in menuconfig and come up empty on the command you're referencing. I'm building denx u-boot from the v2019.10 tag.by hmartin - Off-Topic
bodhi Wrote: > Sorry, I meant "map" command. No support for the map command, I'm sorry to say. I reverted back to RedBoot and I'm almost to the point of having network connectivity in userspace, but there's something in the Click Router configuration that's blocking traffic to userspace. (Click: pesky over-complicated and severely under-documented researchby hmartin - Off-Topic
Quote Does this u-boot has a "mem" command? Yes, but it's not useful: luton # mem DRAM: 128 MiB luton # meminfo DRAM: 128 MiB Quote The u-boot and kernel handover occur after it loads and start the kernel. The params data remained as the input to the kernel. It tells the kernel where things are to go and read. I could be mistaken, but I don't think Vitesse impby hmartin - Off-Topic
Quote ttyS0 might be wrong, should be S0. I tried modifying the line to just S0, no difference: S0::respawn:/sbin/getty -L ttyS0 115200 vt100 I looked into this, and as best as I can tell, the arguments to getty are what matters and the first portion of the line exists only for legacy purposes: https://serverfault.com/questions/925480/t0-vs-s0-in-inittab-for-serial-ttys0-access Otherby hmartin - Off-Topic
Easy, Raspberry Pi 4 with 4GB of RAM. Dual HDMI outputs, loads of availability, and good community support (even if it is in some ways inferior to other products). It doesn't (yet) boot natively off of USB3, but just slap in the smallest micro SD card you can find and use that with a bootloader to boot from USB: https://raspberrypi.stackexchange.com/questions/109546/boot-raspberry-pi-4-frby hmartin - Off-Topic
I need the collective wisdom of people who work with embedded devices. Background: I'm working on an alternate firmware for the Meraki MS220 switch. It's a MIPS-based device that originally ships with Redboot, a NOR-based kernel + embedded initrd that kexec's to a NAND-based kernel + embedded initrd. Very inelegant, and the tools to work with TSOP48 NAND chips are expensive andby hmartin - Off-Topic
Quotebodhi I'll notify hmartin to fix and test this EX2100 DTS. Unless you have a patch and would like to post the patch and the bootlog to show that you've fixed it (Please do that in a new thread). Thanks for notifying me bodhi. I don't have access to my EX2100 at the moment, I moved recently and it's still packed in a box... somewhere. If someone else with an EX210by hmartin - Debian
Uart Before we begin installation of Debian, you will need a working uart connection to the EX2100. There are two possible methods to connect via uart: 1. solder a header to JP1 the PCB to expose Rx, Tx, and Gnd. This will require opening the enclosure and removing the PCB, which will void your warranty. Picture. 2. Using kapton tape, cover the 3.3V and Gnd pads on the front of the PCB. Useby hmartin - Debian
Well, just my luck. I patched out the wake on lan portions u-boot was puking on and I was able to boot the WD firmware. Even more lucky for me, there is a new update to be installed. I installed the update, and now it seems the firmware on the Weltrend is back into a reasonable state. It's still not what was shipping on my unit because I'm missing the "Yosemite uart test" oby hmartin - Debian
Well, good news, bad news. I was able to locate software (Postal2) that can enable ISP mode on the Weltrend. After reading the contents of the Weltrend's EEPROM, I was able to determine that mcu_upgrade erased the firmware portion of the Weltrend's flash. But, due to some issue it didn't write the new firmware, so all the Weltrend had was its bootloader and nothing else. This exby hmartin - Debian
The latest WD firmware for the affected models is supposed to fix these vulnerabilities. For example the EX2100 has firmware 2.30.172 released in November 2016 which is supposed to fix these vulnerabilities. But having spent some time working in the WD firmware to try and determine how the Weltrend MCU controlling fan and power functions, and working with their u-boot and firmware source coby hmartin - Off-Topic
I was updating my EX2100 to the newest WD firmware to resolve the vulnerabilities discovered (not that I ever plan to use the WD firmware, just thought I should update it now while it's on my mind) and I noticed during the firmware update process that it also updates the firmware on the Weltrend: 19436 root 49120 R mcu_upgrade -r -f /tmp/uP_0.bin 19552 root 2720 R ps axby hmartin - Debian
It has just been revealed that there are numerous, serious vulnerabilities and a backdoor present in the stock firmware from Western Digital: http://gulftech.org/advisories/WDMyCloud%20Multiple%20Vulnerabilities/125 These vulnerabilities affect all WD MyCloud products running the Western Digital firmware. For the EX2100, WD firmware below 2.30.172 is vulnerable (PDF release notes). I willby hmartin - Debian
Already there is enough trouble to get good mainline support on ARM platforms, given the vendor specific u-boot patches, kernel patches, hacks, etc. It's interesting to see Western Digital putting their effort behind RISC-V. I will be especially interested if they release any NAS products based on RISC-V instead of ARM. However I hope that this won't mean the end of good Linux supporby hmartin - Off-Topic
Quotebodhi In January, I'm going to get another Armada based board which has kwboot capability and start on building u-boot for it. Once I have one board working using the latest mainline u-boot code, then other Armada boards will be the next step.. This is great news! I noticed that recently Turris Omnia (Armada 385) support was added to mainline u-boot. Unfortunately, trying to kwboot mby hmartin - uBoot
Quotebodhi We don't do power off during normal operation. There are quite a few things that need to happen before power off is issued, as the final step. Yes of course, but I wanted to test without modifying a bunch of things (like the kernel). Are you saying that if I issue the PowerOff command to the MCU as one of the last things the kernel does before halting the Marvell SoC, I shouby hmartin - Debian
Quotebodhi Perhaps you can try to pigyyback the mcmdaemon Power Off in /etc/init.d/halt? I don't understand what this would change. Can you explain why you think putting the command in halt would be different than just issuing it while the OS is running? Unless I've completely misunderstood, the MCU brings the Marvell SoC out of reset. So unless the Marvell needs to set some GPIOby hmartin - Debian
Quotebodhi How far did saschadd and I got regarding Power Off I just tested the "Power Off" command from the kernel patch on my EX2100. It doesn't stay powered off, just shutting off for about 1 second and then starting again immediately. import serial from time import sleep port = serial.Serial("/dev/ttyS1", 115200, 8, "N", 1, 0.1) def WritePktToby hmartin - Debian
I don't think mcm-daemon was originally intended to control the power LED. It is however possible, since the commands are known: char PLedOffCmd[] = {0xfa, 0x26, 0x00, 0x01, 0x00, 0x01, 0xfb}; char PLedBlueOnCmd[] = {0xfa, 0x26, 0x00, 0x11, 0x00, 0x01, 0xfb}; char PLedBlueBlinkCmd[] = {0xfa, 0x26, 0x00, 0x21, 0x00, 0x01, 0xfb}; char PLedBlueFby hmartin - Debian
fdtfile=armada-38x-modular.dtb This is leftover from the stock uboot environment. It's not used to boot Debian. So your DTB is appended to the end of the kernel, which is why the second serial port is not being created (because the DTB you downloaded is not being used). You need to append the updated DTB to the bare kernel, as described in the second link.by hmartin - Debian
Can you please print the output of fw_printenv | grep dtb? @bodhi: I thought you updated the boot process so the DTB was appended to the kernel? In that case, esion needs to replace the appended DTB with the updated version. https://forum.doozan.com/read.php?2,34103,35370#msg-35370 https://forum.doozan.com/read.php?2,34103,38164#msg-38164by hmartin - Debian
Okay, good, that was expected. Can you please try to boot Debian with the most recent dtb bodhi has posted? There is no point to trying mcm-daemon if you do not have two serial ports in dmesg after booting. The output of dmesg should be nearly identical to the WD stock firmware output you provided above. If there isn't a ttyS1 created then there's some other issue and I would defeby hmartin - Debian
Quotebodhi No, I cannot :) I don't have this box, you forgot that I do not have the hardware :) I only worked on it virtually based on saschadd information. Either saschadd or esion has to do it. Sorry about the miscommunication. I know you don't have the EX4100. I meant about the DTS. Thanks for posting, maybe esion can try again. If the dts is correct, there should be two seriaby hmartin - Debian
Unless I am mistaken, this is still not correct. You have one serial port at 0xf1012000 enabled. This is the uart output from the SoC (since it has the console enabled). Serial at 0xf1012100 is still not being created, and there should be no console present on the Welltrend uart interface. Your output: [ 1.152223] console disabled [ 1.176119] f1012000.serial: ttyS0 at MMIO 0xf101by hmartin - Debian
Quotebodhi Did you mean this? Yes. I guess I'm looking at at old dts here? If esion is booting with the correct EX4100 DTB, any idea why the ttyS* device isn't being created? It's strange there is nothing about the ttyS device in dmesg. Here is on my EX2100: [ 1.324990] console disabled [ 1.348744] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 23, base_baud =by hmartin - Debian
Quoteesion dmesg | grep tty doesn't show any output. @bodhi, the EX4100 dts is missing the uart port to the Welltrend. Could someone with the EX4100 and a serial console please post the output of dmesg | grep ttyS from the WD firmware?by hmartin - Debian
Can you please post the mcm-daemon.ini? Unless you didn't modify it. In case you didn't already know, you cannot run the daemon alone, you need the mcm-daemon.ini configuration file too. Is mcm-daemon.ini configured for /dev/ttyS1? What does this show: dmesg | grep ttyS The errors in your output show mcm-daemon wasn't able to connect to the serial port and set the communicby hmartin - Debian
Quotebodhi Argh :) that's just thoughtless WD. Probably a different contractor/engineer designed this product. But very annoying they don't even bother to update their own hardware_init script. I took some measurements today with an optical tachometer, the fan speed on 100% duty cycle is 4800 RPM. I updated the fan RPM calculation to reflect this. Updated binary is attached, no otby hmartin - Debian