pengu > moved to the right thread ;-) > sorry for confusing > Good idea :) let's keep everything about this u-boot testing in this thread from now on. Here is what I posted in the Debian thread: QuoteI'm running out of free time to pursue this. If you could, pls continue with similar tests for the other GPIOs. There are 36 GPIOs that are usable (0 to 35). And I&by bodhi - uBoot
pengu Wrote: ------------------------------------------------------- > done, nothing changed: > > http://pastebin.com/htLjmNHE Thanks pengu! I'm running out of free time to pursue this. If you could, pls continue with similar tests for the other GPIOs. There are 36 GPIOs that are usable (0 to 35). And I've determined those above were the most likely to work, based onby bodhi - Debian
pengu, > yes it is And there was no debug output? if there was, pls post the log from the beginning. Does ethernet works in stock u-boot? i.e. can you ping the router in stock 310 u-boot serial console? As I thought, this could be troublesome :) PCI, in general, is not well supported inmainline U-Boot. I'm running out of time, so I might have to release this without Ethernet aby bodhi - uBoot
I've uploaded the Pogopug E02 u-boot-2014.07-tld-3 image. Please see first post for download link. This version adds the enhancement so that u-boot can boot stock Pogo OS. There no need to upgrade if you don't intend to use stock OS.by bodhi - uBoot
@pengu, Let's try another few GPIOs. In the NSA320S stock u-boot serial console. Poke each GPIO in order (most likely to least): 34, 20, 10, 4. Each poke should follow with a "ide reset" to see if the 2nd HDD is power up. Please check my cconversion for correctness in the shift left operations below :) GPIO 34 (1 << 2) -- 1 left shift 2 bits is 0x04 md f101014by bodhi - Debian
pengu, > > NSA310> ping 192.168.1.112 > No ethernet found. > ping failed; host 192.168.1.112 is not alive > NSA310> > Is this the output from the test u-boot UART booting?by bodhi - uBoot
doomgiant, Everthing looks normal. Except that the stock kernel could not start. I believe this is likely the problem that restamp and I solved a few months ago, and I uploaded a new Pogo E02 u-boot image but forgot to release it: http://forum.doozan.com/read.php?3,12381,20906#msg-20906 Basically, somehow the stock OS in NAND was modified during the installation or later, but with a differby bodhi - Rescue System
@pengu, Please try UART booting the test u-boot image attached above: uboot.2014.07-tld-4-test-1.nsa310.mtd0.kwbby bodhi - uBoot
hawryszka, Glad it works for you! > Should or could i update/upgrade it to 4.0/4.1 > rootfs version ? > From which instruction should i take it ? The reason you've had trouble trying out many different kernel versions was the issue of device tree (FDT) kernel vs. older non-FDT kernels. My kernel build 3.16.x or earlier were non-FDT. You should upgrade to get all the latesby bodhi - Debian
theeleaper, So the problem is with Samba? if it is, see this post for a working Samba config: http://forum.doozan.com/read.php?8,23223,23293#msg-23293 I would suggest that when you need help with any problem, be very wordy :) give a lot details, as much as you can. And post a log of what you trying to do.by bodhi - Debian
z3bram3n Wrote: ------------------------------------------------------- > PBG4 wrote that the NSA320 has been tested and > validated. Will this be available for uploading? > Thanks. > > Paul Hi Paul, See my post above: http://forum.doozan.com/read.php?2,12096,23388#msg-23388 I'm building a test kernel, and will check out on other Kirkwood boxes. Will let you kby bodhi - Debian
Attached here is the first cut to enable RTL8169 chip ( not sure how far we'll get with this image :). I turned on RTL8169 debug so we can see if the card is intialized at all. Please test with UART only (not flashing to NAND) kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-4-test-1.nsa310.mtd0.kwb -pby bodhi - uBoot
doomgiant, So now when you boot without the USB drive, what does serial console output looks like?by bodhi - Rescue System
Quotehttp://forum.doozan.com/read.php?3,12381,21223#msg-21223 marlemion said: EDIT7: So the RTL8111d chip is an PCI-e chip. PCI-e is initialized, however, the linking problems remain. Does anybody know how to get further? And: http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=5&Level=5&Conn=4&ProdID=193 This is going to be troublesome.by bodhi - uBoot
bobafetthotmail Wrote: ------------------------------------------------------- > nsa310 here, zyxel one. > > It does seem to have indeed that realtek chip. Cool! thanks for the confirmation. > kwbooted and your uboot has no ethernet access. No wonder! > rebooting into normal uboot, see below > then I get multiple errors of marvell driver like > below, suby bodhi - uBoot
hawryszka Wrote: ------------------------------------------------------- > Hello Guys > I have problems with nsa 325 v2. > I did everything, step by step on the solution but > stil have problems , i dont have any more patient > for that .. > I try to start linux from USB storage formated to > ext2 but i have that information in console : > > Part Start Secby bodhi - Debian
Thanks luke, have been busy so I will take a look later.by bodhi - Debian
pengu Wrote: ------------------------------------------------------- > both, the "ZyXEL" and the "TDC" brand has a > Realtek LAN chip > I haven't seen any NSA310 with Marvell Chip Do you have the orginal NSA310 dmesg output? Or if marlemion indeed has the orginal 310 then it would clear up the confusion. The current NSA310 u-boot code patch I am usingby bodhi - uBoot
doomgiant, > Could you help to show how to update error kernal > image in debian?Sorry i am not familar with it. Or > is it possible to make original pogoplug system > work again? That error was not real. Right now, you can just remove the USB stick and it will boot into orginal Pogo OS. If that does not work, please post the u-boot envs while in Debian: fw_printenvby bodhi - Rescue System
pbg4, Thanks! will try it shortly.by bodhi - Debian
Here is the page that has pics of both: http://zyxel.nas-central.org/wiki/Category:NSA-310by bodhi - uBoot
marlemion Wrote: ------------------------------------------------------- > AFAIK there is only the NSA310S, which uses the > Alaska chip: > > http://archlinuxarm.org/forum/viewtopic.php?f=57&t > =8827 Yes. I've just finished a new u-boot for that: http://forum.doozan.com/read.php?3,23331 I'm starting to doubt whether any flavor of the NSA310 boxes has thby bodhi - uBoot
pengu & marlemion, I would like to find out if there is a NSA310 box that uses the 88E1318 chip (before I start creating a separated board directory or sub-board version :-). A very long thread at NAS-Central: http://forum.nas-central.org/viewtopic.php?f=249&t=5145&start=15by bodhi - uBoot
marlemion Wrote: ------------------------------------------------------- > This one: > http://abload.de/img/nsa310_lanbisgx.jpg > > I can confirm that this one is on my NSA310. If > you read EDIT6 here: > > http://forum.doozan.com/read.php?3,12381,21223#msg > -21223 > > you will see that I mentioned it there, too. OK. Got it. I think pengu misundersby bodhi - uBoot
I could not see where is the LAN chip is, does it say 88E1318? if it does, then there is no need for another u-boot sub-version to use the RTL8169. It looks like we need another build to take care of the 88E1318 PHY. I'll rebuild and upload.by bodhi - uBoot
pengu, > both is from the same box so ZyXEL OS uses a > different driver for the same chip So when you opened it, the chip inside is Marvell Alaska? But does it "really" have a USB LED that turns red? And I should have asked "does PCI appear to be used in anything, e.g. USB 3.0".by bodhi - uBoot
pengu, > no it's the seme on the original NSA310 because it > uses the same LAN chip That's not the same LAN chip, if it shows RTL8169 > > > r8168 Gigabit Ethernet driver 8.023.00-NAPI > > > loaded > > > r8168 0000:00:01.0: no MSI. Back to INTx. > > > Set LED ... > > > eth%d: RTL8168B/8111B at 0xd0900000, > > &gby bodhi - uBoot
pengu Wrote: ------------------------------------------------------- > > U-Boot 2014.07-tld-4 (Aug 19 2015 - 20:51:56) > ZyXEL NSA310 1-Bay Power Media Server > > > SoC: Kirkwood 88F6281_A1 > DRAM: 256 MiB > WARNING: Caches not enabled > NAND: 128 MiB > *** Warning - bad CRC, using default environment > > In: serial > Out: serialby bodhi - uBoot
doomgiant, Since you have installed u-boot successfully using Jeff's script. You can just create a basic working Debian rootfs. Ttry the Debian-3.16.0-kirkwood-tld-2 rootfs: http://forum.doozan.com/read.php?2,12096 Scroll down to the section: Quote Updated 02 Sept 2014 (rootfs): Rootfs Debian-3.16.0-kirkwood-tld-2 was uploaded. This rootfs is to keep in sync with kernel Linux-3by bodhi - Rescue System
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > brought out my inner comic :-D > > There's only one thing this lacks on the E02, > either a browser that supports Ghostery or a > standalone file downloader that's break resistant. > The company I beta test has files for me at > app.box - a dropbox-style uploader that's prby bodhi - Debian