> What I have not yet found is how I flash the > u-boot to the nand, because I have to reuse kwboot > every time I turn it off now. And is the > uboot.2023.04-tld-1.nsa325.bodhi.tar image better > to use as it's newer? Does it matter? Log into Debian, follow the instruction in the u-boot release post to install to NAND. And for the initial installation, it does not matby bodhi - uBoot
FIS, > No idea what binary it was. Found it here > https://forum.doozan.com/read.php?2,61344,134363#msg-134363 I see. I think it was not tested thouroughly because not many people use Windows. > What version of Linux would you recommend? I would recommend Linux Mint. But Mint is a Ubuntu derivative. So Ubuntu is fine. Basically, you need to format the drive at command linby bodhi - uBoot
> Before this I ran > kwboot from Windows 10, thus ttyS2. Not a good idea. Which kwboot binary were you using? was it compiled on Windows? > Never connected the 3,3v pin so serial is not > fried. But for some reason Windows would get > stuck/do nothing when running the kwboot command. I would avoid using Windows apps for things Linux-related. Just install a Linux VM forby bodhi - uBoot
ksuszka, > @bodhi I'm not sure if I understood correctly. > Should we test it with released kernel 6.5.7 and > only modified kernel boot params or something else > should be changed? > > If it is the first case then I attach two logs, > from two boots which differ only in kernel boot > param. In both cases the behaviour of dumping mtd > is the same - evby bodhi - Debian
Ok so it was my mistake. The DTS clearly/badly stated spi1 but I overlooked (BTW, the non-standard naming convention used by the author here). ssp1: spi@d4035000 { compatible = "marvell,mmp2-ssp"; reg = <0xd4035000 0x1000>; clocks = <&soc_clocks MMby bodhi - Debian
I've just noticed your kwboot command: kwboot -t -B 115200 /dev/ttyS2 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Why it is /dev/ttyS2? Usually it is /dev/ttyUSB0 on most Linux host, or /dev/ttyAMA0 on the rPi. See: https://forum.doozan.com/read.php?3,51739,51919#msg-51919by bodhi - uBoot
> Found a way to flash the firmware from software > after all :) Cool! > [*] Followed > this > guide to bind the spidev driver to spi1.0. So I missed that fact! spi1 is the device. QuoteCompiled this kernel from the mmp-armada-drm-5 branch Built uImage for the kernel Successfully booted into Debian Do you have a boot log for this run? that could be very helpful.by bodhi - Debian
QuoteI have serial connection (which was what I used to erase it) Even the NAND is completely erased, kwboot should work for this box. Quote> Am I supposed to connect the 3.3V pin? No. If you had connected the 3.3V pin before, then that could have fried the serial port. ================ Some ideas: - Make sure the serial connection wires are away from the power cord. Sometime iby bodhi - uBoot
QuoteOn a sidenote, I found this extremely promising repository from the creator of linux-mmp, Lubomir Rintel. It seems like he even got the DRM drivers working, and his DTS is much more complete. It looks like this repo's kernel is a work-in-progress. Even the latest DTS seems to be a working version.by bodhi - Debian
> OK. I did not think it would have made a > difference either, but worth a try! I'll take a > look at this driver to see if there is anything > strange. I've looked at the Winbond SPI driver and did not see anything peculiar.by bodhi - Debian
msh493, > When I try to connect to the board with screen > /dev/ttyUSB0 115200 I get a blinking cursor. And > that's it. I can't get to firmware prompt. What > have I done? :) And how do I get back to being > operational? I would love to learn how to try > different images to learn the process. Right now > I'm kind of confused. You need to connectby bodhi - uBoot
FIS, > > I have an older NSA325v2 I decided I wanted to get > Debian on. I found some different posts here on > the forums and decided to give it a go. To cut it > short, I wanted to update the u-boot and somehow > managed to erase the nand, and now it won't do > anything. > I have serial connection (which was what I used to > erase it) but is there a wby bodhi - uBoot
Kernel linux-5.4.268-oxnas-tld-1 package was uploaded. See 1st post for download link. And please create a new thread for questions or problem in installation.by bodhi - Debian
CyberPK, I'm hesitate to restore the driver to what it was before, given what was said in the email thread. QuoteFrom: Mikulas Patocka The driver drivers/crypto/marvell/cesa/cipher.c uses GFP_ATOMIC allocations (see mv_cesa_skcipher_dma_req_init). So, it is not really safe to use it for dm-crypt. GFP_ATOMIC allocations may fail anytime (for example, they fill fail if the macby bodhi - Debian
> > So if you boot with USB only, then you can > access > > the eMMC drive in Debian? > > > Yes I can boot with USB, but only when I enter the > boot selection menu by pressing "P" repeatedly, > and then selecting "USB". I meant if you did the above (ignore eMMC completely), then later in Debian, can you see the eMMC drive being initiaby bodhi - Debian
> > root@debian:~# flash_unlock /dev/mtd0 > flash_unlock: error!: could not unlock device: > /dev/mtd0 > > error 95 (Operation not supported) > OK. I did not think it would have made a difference either, but worth a try! I'll take a look at this driver to see if there is anything strange.by bodhi - Debian
mmm, > Yes, the wloader seems to "jam" the eMMC when not > explicitly selecting booting from USB on boot. So if you boot with USB only, then you can access the eMMC drive in Debian?by bodhi - Debian
ksuszka, > Both terminals show the same behaviour when > reading mtd - every second read is correct. > However there is some difference in the firmware > content on both terminals. As far as I can tell, > most of it is the same, there is one block of a > few kb of compressed data which differs and a > second block with a few bytes which are different. > The seconby bodhi - Debian
Hi Andreas, > Swap as well as general memory was never a problem > – there is almost nothing running on this > device. Maybe the flash stick is dying and the > coincidence with the update is just bad luck. It's hard to say what's the problem here. Debian 11.x is considered too old now. So I guess it's time for me to release a new 5.4.x kernel for this boxby bodhi - Debian
Andreas, Quote have to resurrect this thread. Today I updated my Pogoplug Pro from Debian Bullseye 11.8 to 11.9 via normal apt update & upgrade. I encountered several segfaults during the installation (configuration) of the Debian packages. With dmesg I got several errors like this Sounds like a swap problem. What is your swap space? you do need swap to run apt upgrade. free -hby bodhi - Debian
Thanks mmm! SPI looks normal. Also, this is interesting, I guess this is your eMMC problem. [ 2.778335] mmc0: SDHCI controller on d4281000.mmc using ADMA [ 5.028810] mmc0: Card stuck being busy! __mmc_poll_for_busy [ 6.188727] mmc0: Card stuck being busy! __mmc_poll_for_busy [ 7.316328] mmc0: Card stuck being busy! __mmc_poll_for_busy [ 7.324078] mmc0: Failed to initiaby bodhi - Debian
> I'm still learning Linux and I after so many trial > and errors, I'm a bit scared of building my own > bin file. has anyone already built one for the EX2 > Ultra with 1GB configuration ready? I believe I > also mac address not persistent and I haven't even > yet checked the Leds. but most important issues to > fix are RAM and keep Mac address persistentby bodhi - Debian
kaze's boot log https://forum.doozan.com/read.php?2,134563,135436#msg-135436 [ 4.439326] spi-nor spi0.0: w25q32 (4096 Kbytes) [ 4.444682] i2c i2c-0: PXA I2C adapter, slave address 1 [ 4.444765] 1 cmdlinepart partitions found on MTD device spi0.0 [ 4.451104] (null): Enabling slave mode [ 4.464571] i2c i2c-1: PXA I2C adapter, slave address 1 [ 4.471155] (nullby bodhi - Debian
All, I'm refreshing my memory about this topic. https://forum.doozan.com/read.php?2,134563,135517#msg-135517 QuoteGravelrash Wrote: ------------------------------------------------------- > bodhi Wrote: > > I'm on travel currently, and will get back to > this > > subject when I can. > > > "Bodhi Bond" - International man of > cby bodhi - Debian
> @LegacyObj you need a laptop/PC with USB to UART > adapter. They can be bought for less than $1 on > aliexpress: > https://www.aliexpress.com/w/wholesale-usb-uart-adapter.html. > I use the one with CH340G chip. Next you need to > open top cover of the Wyse 3020 and connect two > pins of CN4502 connector on the motherboard to > this adapter. You need to connect GNDby bodhi - Debian
alexr, > Hey bodhi > > I can also verify the new bookworm rootfs does not > boot on the pogoplug v4 mobile when the rootfs is > installed on an sd card. Yeah. I'm updating the rootfs installation instruction to warn people about this quirk with Pogo V4 SD rootfs. Thanks for the confirmation!by bodhi - Debian
@ksuszka, > @mmm I updated my eMMC to kernel 6.5.7 using the > method described by bodhi, I added missing modules > to /etc/initramfs-tools/modules Is there other modules needed or just these 2? pwrseq_emmc mmc_block It's would be good to include only what's needed. So I could configure them as builtin modules in the next kernel build if size permitted.by bodhi - Debian
> @bodhi I've just noticed that I repeatedly > misspelled your nick. I sincerely appologize for > it. Just an explanation, in polish there is a name > spelled "Bohdan" and "bohdi" is a word one could > use if he tried to use it in English and make it > sound less formal. So I read it that way as it > sounded familiar. It's all good :) haby bodhi - Debian
mmm, > Thank you, now using this instead: > > lsmod | awk '{print $1}' | tail -n +2 > > /etc/initramfs-tools/modules > update-initramfs -u > I think you only need to add these 2 modules: pwrseq_emmc mmc_blockby bodhi - Debian
ksuszka, > Something strange happened. I just run this > command and check the content of the mtd0.bin and > it was all zeros (I've used some snippet from SO > to generate quick and dirty histogram of bytes in > the file): > > root@debian:~# dd if=/dev/mtd0 of=mtd0.bin > bs=4096k conv=sync > 1+0 records in > 1+0 records out > 4194304 bytes (4.by bodhi - Debian