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
lordzahl, > http://www.thecus.com/Downloads/GPL/arm_32.a385_v3.02.02.11_GPL.tar.bz2 There is no u-boot GPL in this tarball. That would be more helpful than the kernel source.by bodhi - Debian
leitmotiv, Stay with sysvinit for now. No need to worry about it being obsolete yet.by bodhi - Debian
habibie, > Now, I am trying to flash your u-boot on my > Seagate GoFLEX Home as well as my Seagate GoFLEX > NET. It looks like the same as a Seagate > Dockstar's mtdparts you mentioned > here. > So, I reckon it safe to use the above mtdparts and > with the following command for both my Seagate > GoFLEX Home and/or Seagate GoFLEX NET. > fw_setenv mtdpartsby bodhi - Debian
lordzahl, > @bodhi: Okay, if i understand you correctly i > should still use the dtb from your Debian/linux > Images. We also do not need the kernel config. The > only thing which is missing (at the moment) is the > USB power. Correct. > > So i was thinking, the dts, which is used for this > box does indeed not enable USB power on boot. We > can see thaby bodhi - Debian
JT, I don't recall using dpkg-reconfigure at all. I think if you apt-get install locales, everything should be good.by bodhi - Debian
@schnee, Good works :)by bodhi - Debian
echowarrior108, Congrats :) At this point, it is unbricked :) Now you can boot into Debian. And set up booting with USB rootfs. Keep this HDD as a rescue mechanism, until you can boot with u-boot in NAND and USB rootfs. After that, you can switch back to HDD rootfs if you like to do that.by bodhi - Debian
dietgert, > System is now up again. > So this brings me back to the original point: > which spl-file could be safely used for operation > > below 850Mhz frequency ? > This SPL is below 850 Mhz: Quotehttps://forum.doozan.com/read.php?3,16017,16017#msg-16017 Updated 16 May 2014 I've uploaded the 2013.10 u-Boot image for Pogoplug V3 Oxnas ...... Doby bodhi - uBoot
How to enable UTF-8 for different languages in your system. ============================================= Please adjust the locale to your own country. This example uses US UTF-8. Prerequisite: locales was already installed with: apt-get install locales Steps: 1. Change locale.gen (uncomment the appropriate line). cat locale.gen # This file lists locales that you wish tby bodhi - Debian
I am updating this post as I am reading the info from n2350_gpl.tar.gz. 1. The newer DTB that should be used for this Thecus N2350 box: In the rootfs Debian-4.12.4-mvebu-tld-1-rootfs or in newer kernel linux-4.15.4-mvebu-tld-1: ./boot/dts/armada-388-db.dtb 2. The kernel config in In the rootfs Debian-4.12.4-mvebu-tld-1-rootfs or in newer kernel linux-4.15.4-mvebu-tld-1 should be enouby bodhi - Debian
Yes, there is some minimum UTF-8 setup needed. I will post my settings (in my log somewhere).by bodhi - Debian
I think what I want to do here is to setup the installation the same way for OXNAS as for Kirkwood. I know habibie has been asking about this issue. Perhaps habibie can tell us how it was installed on Pogo Pro?by bodhi - Rescue System
alexinc, We should move your thread to the Rescue subforum. It is now a OpenWrt problem (not a u-boot problem). I do think you need to reinstall OpenWrt. Do you have any data on its rootfs that you want to save? In the Rescue subforum, there are different OpenWrt/LEDE threads that discuss this topic (no Medion OXNAS topic yet). You could look and see how others install their Kirkwood boby bodhi - Rescue System
bchen Wrote: ------------------------------------------------------- > bodhi, > > I resolved it by using a different SD card. I > don't understand but who cares :P Cool :) the problem might be during you created the rootfs, you've missed some step/requirements, or the SD card itself is not good for booting (there are brands that really bad for rootfs). Doing it theby bodhi - Debian
Try /srv 192.168.1.0/24(rw,no_root_squash,insecure,no_subtree_check,sync)by bodhi - Debian
Hi habibie, Please keep all gcc-7 in this same topic. No need to create new thread for different gcc-7 problem.by bodhi - Debian
habibie, It should be own by man/man. I think you should redo your rootfs from the tarball again.by bodhi - Debian
So at 2nd stage boot, U-Boot 2014.10 (Dec 08 2017 - 09:01:13) for OXNAS DRAM: 128 MiB NAND: 128 MiB UBI: attaching mtd1 to ubi0 UBI: scanning is finished UBI: attached mtd1 (name "mtd=1", size 114 MiB) to ubi0 UBI: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512 UBI: VID header offset: 512 (aligned 51by bodhi - Rescue System