habibie, Apparently, during u-boot installation, you have missed step 8f. Quote8. Flashing default u-boot envs image (if you are upgrading from 2016.05-tld-1 u-boot, you can skip this step 8). As described in step 1, u-boot envs must be defined in /etc/fw_env.config as # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000by bodhi - uBoot
Manuel, Good works :) I'm aware about this script too. > download-serial.sh > script. This is the one we should use: u-boot-a38x-spi-uart.bin. I also have one similar I built last year. > edit: Looking at the sources: download-serial.sh > spams the magic character sequence 6000 times. Yup. Because they don't know the timing either :) > The > mainby bodhi - Debian
Good works Tommy :)by bodhi - Debian
I think you both were most likely right! perhaps this box hang when we don't try initialize the NAND partitions. Will do a version 4 to add the correct NAND mtds back in. Overall, the kernel log looks very good.by bodhi - Debian
habibie, > I now only have a SATA HDD attached sans any USB > memory stick, and yet my Seagate GoFLEX Home still > loads the kirkwood-pogo_e02.dtb instead of > the kirkwood-goflexhome.dtb when booting > through a SATA HDD. This happens regardless I have > the USB memory stick attached or not. So, what you > said is not an issue, AFAICT. OK then post the netconsoby bodhi - uBoot
ShapeShifter499 Wrote: ------------------------------------------------------- > Hello Bodhi, > > The thread is too long to read through all of it. > I'm just wondering what your patches fix over the > mainline and why they haven't been added to the > mainline kernel. Yes the patches should be applied on top of the mainline source tree 4.4.117. There is aby bodhi - Debian
Here is a modified DTB version 3 for testing. This time we have the correct SPI flash type, and the SPI driver (in mtdparts). Copy the attached DTB to your USB rootfs /boot/dts/ folder. Power up, interrupt serial console and set the envs (note that we are not loading uInitrd). We want to ignore that for now and see if the USB drive is powered up OK first. setenv mtdparts 'mtdpartsby bodhi - Debian
But that's a good point, though. Here is the boot log for NAS326. [ 1.269893] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode [ 1.279299] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs [ 1.299041] scsi host0: ahci-mvebu [ 1.312901] scsi host1: ahci-mvebu [ 1.316504] ata1: SATA max UDMA/133 mmby bodhi - Debian
I'd doubt that a wrong flash definition would cause the hang. However, on the subject of SPI flash. 1. You're correct. That should be MX25L3205D according to your boot log. The current compatible name is from the mainline DTS version. I was not worry about it. SF: Detected MX25L3205D with page size 64 KiB, total 4 MiB 2. I suspect this would be wrong in mtdparts. But agaiby bodhi - Debian
Manuel, Try removing the HDDs and boot with USB only. And I am eager to see if you can try kwboot again.by bodhi - Debian
Manuel Here is the DTS source. Perhaps you might be able to spot something I did was wrong.by bodhi - Debian
Here is a modified DTB version for testing. Copy the attached DTB to your USB rootfs /boot/dts/ folder. Power up, interrupt serial console and set the envs (note that I've changed the usb_bootcmd to not loading uInitrd). We want to ignore that for now and see if the USB drive is powered up OK first. setenv load_dtb_addr 0x1000000 setenv load_initrd_addr 0x2900000 setenv load_imaby bodhi - Debian
habibie, As I've said above, conflicting info from both USB and HDD rootfs https://forum.doozan.com/read.php?3,54589,54659#msg-54659 Use one for data and other for rootfs then problem will be gone.by bodhi - uBoot
No, that dirty hack is not reconmended :)by bodhi - uBoot
lordzahl Wrote: ------------------------------------------------------- > > This run is actually better. When this happen, > > immediately use the up arrow to recall the > command > > and execute it again. > > I did that and it ended in the exact same message. > So it seems it at least got into the right mode, > but the data connection is still pretty baby bodhi - Debian
> Yes, it just stops/hangs. Nothing happens after > that. Inputs have no result. > I tried a second time with the same result. OK! I did not have any SATA node in the DTS yet. Will upload another version in perhaps 8hrs or so.by bodhi - Debian
habibie Wrote: ------------------------------------------------------- > Bodhi, > > You are right. I fixed the netconsole now. Also, I > have updated my OP to include the netconsole > output which indicates uboot loads a wrong > boot/dts/kirkwood-pogo_e02.dtb file when > booting off of a SATA HDD. I don't know how this > happens. Remember: there should beby bodhi - uBoot
Did it stop here? hang? [ 0.920675] ata2: SATA max UDMA/133 mmio port 0x180 irq 43by bodhi - Debian
Please see the DTB I've attached above for testing.by bodhi - Debian
lordzahl, > > $ ../kwboot-x86_64 -t -B 115200 > /dev/ttyACM0 -b mtd_uboot -p > Sending boot message. Please reboot the > target...- > Sending boot image... > 0 % [+++++++++++++++++xmodem: Bad message > This run is actually better. When this happen, immediately use the up arrow to recall the command and execute it again.by bodhi - Debian
leitmotiv, > Any particular reason why you would not recommend > switching to OpenRC just yet? Not really. I think OpenRC is good to. I was just making comment on sysvinit. I think it will be with us for a long while, eventhough it is not being updated.by bodhi - Debian
Here is the initial DTB version for testing. Copy the attached DTB to your USB rootfs /boot/dts/ folder. Power up, interrupt serial console and set the envs (note that I've changed the usb_bootcmd to not loading uInitrd). We want to ignore that for now and see if the USB drive is powered up OK first. setenv load_dtb_addr 0x1000000 setenv load_initrd_addr 0x2900000 setenv load_imby bodhi - Debian
dietgert, I recall testing the new u-boot with older SPL and it was fine. QuoteUpdated 22 Nov 2015 I've uploaded the uboot.2015.10-tld-1 u-Boot image for Pogoplug V3 Oxnas. Warning: netconsole does not start automatically in this version. If you don't have serial console and therefore need netconsole to see the boot progress, please use previous u-boot version (uboot.201by bodhi - uBoot
habibie, You did not activate netconsole. These are the relevant uboot envs. if_netconsole=ping $serverip ipaddr=192.168.0.231 preboot_nc=run if_netconsole start_netconsole serverip=192.168.0.220 start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version; To activate netconsole, boot with USB and copy/paste this commandby bodhi - uBoot
@nailman, Did you solder the wires or just temporaily connect them like lordzahl did? @all, That was actually some strange behavior, since we are kwbooting the same u-boot, but the output seems to be different. BootROM - 1.73 (Boot) Booting from SPI flash And the progress of image loading did not show after this: Sending boot image... So I think the handshake did not occurby bodhi - Debian
While I'm coding the DTS, I'd like you to try the kwboot again. I can see why your kwboot was not successful with that error. Thecus u-boot is in SPI flash! BootROM - 1.73 Booting from SPI flash [ 3.652367] 2 ofpart partitions found on MTD device spi1.0 [ 3.657900] Creating 2 MTD partitions on "spi1.0": [ 3.662714] 0x000000000000-0x000000400000 : &qby bodhi - Debian
Hi Manuel, I see I've missed that picture :) Looks like J1 is a 4-holes pinout? hope it is not a 4 solder buttons! J2 looks like JTAG pinout (usually 20 pins).by bodhi - Debian
lordzahl, Do you have a picture for this box that you can upload here? Is there a serial pinouts header?by bodhi - Debian
I'll write an initial DTS for this Thecus N2350 and upload it for testing.by bodhi - Debian
Ok found a whole bunch of GPIOs. /* N2350 GPIO(MPP) Definition */ static const unsigned char FAN_TACH = 6; static const unsigned char STAT_LED_WHITE = 14; static const unsigned char STAT_LED_RED = 15; static const unsigned char USB_LED_WHITE = 16; static const unsigned char USB_LED_RED = 17; static const unsigned char PWR_LED_RED = 18; static const unsigned char HDD1_LED_WHITE = 19;by bodhi - Debian