I see, we need to remove the mask to make mtd0 writeable then.by bodhi - uBoot
@Warhead, It looks like the kernel set mtd0 to read-only. Was it intentional? grep -5 MTD arch/arm/mach-kirkwood/nsa325-setup.c.org static struct mtd_partition nsa325_nand_parts[] = { { .name = "uboot", .offset = 0, .size = SZ_1M, .mask_flags = MTD_WRITEABLE }, {by bodhi - uBoot
InfoScav, With GFHome and just starting to learn modding, you should follow Jeff's instruction to install Debian Squeeze on a USB stick: http://projects.doozan.com/debian/ - Best to have another Linux box (Ubuntu), or Windows PC that you can run Linux VM or Linux Live CD. - Remember to run the Squeeze script ( http://projects.doozan.com/debian/dockstar.debian-squeeze.sh), not Wheezyby bodhi - Debian
Without the PHY init, I just set GPIO 14 to 1.by bodhi - uBoot
shatterstar78, The stock kernel and rootfs are on other MTDs (U-boot is on mtd0), they are untouched. But you will not be able to access them after you installed new U-Boot. You can only use USB or SATA for rootfs (which include the new kernel). Do you have another plug that you have installed Debian or Arch? If not, this is a not a good device to start with :) the easiest ones are: GoFlexby bodhi - Debian
shatterstar78, Unfortunately, it is a little more complicated on this device than all other plugs. Because at this stage, there are a few options and that made it confusing. What I have done is what I recommend and support fixing problems that might come with it. To boot SATA, install new U-Boot image and new Debian rootfs: 1. Create a USB Debian rootfs: http://forum.doozan.com/read.pby bodhi - Debian
Warhead, I've killed watchdog successfully with just setting the GPIO 14 in board_init. I'm going to clean up a bit and attach the patch here.by bodhi - uBoot
I know fat fingers. It's 14 in the kernel correctly :))by bodhi - uBoot
@Warhead, I found why it was shutdown: typo in nsa325.h (16 is Power Off). #define WATCHDOG_SIGNAL (1 << 16) should be #define WATCHDOG_SIGNAL (1 << 14) Here is the warm start UART boot: U-Boot 2013.10-bodhi-1 (Aug 14 2014 - 13:48:08) ZyXEL NSA325 2-Bay Power Media Server DEBUG: Booting UART, print_cpuinfo ... SoC: Kirkwood 88F6282_?? DRAM: 512 MiB WARby bodhi - uBoot
http://forum.doozan.com/read.php?2,16044by bodhi - Debian
Hi syong, Thanks for posting a nice and clean set of envs! it's much easier to read this way.by bodhi - uBoot
jman Wrote: ------------------------------------------------------- > I was having the same issue as dinjo, but then i > changed my netconsole ipaddr to be different then > the ip address it gets after it boots and i see > the full dmesg until it registers the nic. If the U-Boot ethaddr env is the same as the static IP in your rootfs /etc/network/interfaces, then all log shoulby bodhi - Debian
CasperJim, If you've changed them around too much, it is hard to see the mistakes :) If you get the output of your current envs and post here. I'll take a look. May be just a typo somewhere. Or is it booting now?by bodhi - uBoot
See this thread: http://forum.doozan.com/read.php?2,9522by bodhi - uBoot
Yes! but back up your rootfs first. It will be a massive change.by bodhi - Debian
Yes. That jessie: https://packages.debian.org/search?searchon=names&keywords=gcc-4.8 So if you have wheezy in your /etc/apt/sources.list then you are running wheezy rootfs. And to see gcc-4.8, your apt sources must be changed to point to jessie, therefore you will be using Debian testing distribution, not stable distribution (wheezy). The pinning I've mentioned above allows you toby bodhi - Debian
optim Wrote: ------------------------------------------------------- > I am looking for a copy of gcc 4.8 for arm. A > project I want to play with says it requires gcc > 4.8 and apt search only shows up to 4.7. > > I have Bodhi's 3.10.4 installed on the GoFlex that > I want to play with. Is there a way to > get/compile/ have added to repositories GCC > veby bodhi - Debian
@theliquid, I could add them in 3.16, when I get time to do it.by bodhi - Debian
Quote> So the only solution is a UBoot which disables the > watchdog by his own. After this stage all devices > are allowed to take as long time as they need. We are working on it in the U-Boot Kirkwood thread. Hopefully the watchdog will be whacked early on in U-Boot!by bodhi - Debian
Result 1: wait, why would it have shut down I guess the warm start had some remnants of stock u-boot in memory, and it did not jive with new u-boot copy. Result 2: Okay, now if we can get the phy_init stuff working for it, we might actually be able to shut off the watchdog. OK, back to you.by bodhi - uBoot
WarheadsSE Wrote: ------------------------------------------------------- > And the changes to the kwbimage.cfg ;) Oops! I've attached it above. It looks ugly w/o comments but works :)by bodhi - uBoot
@Warhead, More progress! I've looked at board/zyxel/nsa325/kwbimage.cfg file and realized that we are using DDR2 definition (it does not seem right). So I looked in the stock U-Boot build, and there is a file dramregs_533ddr3db_A.txt which contains DDR3 definition! so I used this file to build the UART image using the build raw u-boot.bin. It seems this was the cause for the failed startby bodhi - uBoot
@theliquid, Nothing to be concerned. From now on, if you get more bad blocks then yes, keep watch on them. And your bad blocks are in the stock FW (kernel/rootfs) area so they do not affect u-boot (1st 1M). Only later if you want to flash your kernel and/or rootfs to NAND then they will have be accounted for.by bodhi - uBoot
@Warhead, I've posted my further test result in the u-boot kirkwood thread.by bodhi - Debian
CasperJim, > Change this line: > > FSCKFIX=no > > To this: > > FSCKFIX=yes > Nice! I knew something missing on a couple of my boxes that behave differently from the others during bootup regarding fs check, but could't remember what it was. Turned out it is this :) Thanks.by bodhi - Debian
A bit of progress! This is UART catching warmboot. root@Dockstar:/localdisk/linux/uboot# ./kwboot-tool/kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.1.1.4-nsa325v2-uart.bin Sending boot message. Please reboot the target...\ Sending boot image... 0 % [......................................................................] 1 % [............................................................by bodhi - uBoot
@Peter, This is in continuing with the NSA325 booting problem starting at this post in the 3.16 kernel thread. QuoteThe corrupted FS - guess where it does come from: the watchdog resets the nsa35 just right after the sda2 has been mounted! Anyway: I set bootdelay to 1 . I fsck'ed sda2. I cold rebooted, watchdog strikes again ! At which line in the kernellog.txt can we sby bodhi - Debian
ptosch, Let's move this booting problem to the NSA325 thread.by bodhi - Debian
@CasperJim, It's a normal behavior. It got kicked out to the shell because the rootfs couldn't be mounted without correcting errors that are serious and need user interactions. OTOH, if the only thing needs to be done is recovering journal (as occurred during power outage) then it should recover OK and continue booting. And I don't think fstab is really important here. You coby bodhi - Debian
t3ch42, I realized now I should have mentioned netconsole in the instruction. For netconsole, set the preboot variable with fw_setenv. The default settings has only preboot_nc (since I don't want to assume that users want to activate netconsole by default). preboot_nc=run if_netconsole start_netconsole preboot=run preboot_nc To help the kernel to find the correct rootfs, use rootfby bodhi - uBoot