bobafetthotmail, Thanks for confirming! > Why do you want to connect a Jtag? Better > understanding of the SoC/box? Yes. I'm hoping to learn something new about this SoC using this interface. Besides, I have a friend offering to do the soldering for me at his work place after hours, so I though why not :) > Btw, a german guy seems to have installed (your) > Debianby bodhi - uBoot
pengu Wrote: ------------------------------------------------------- > the NSA310s isn't capable of kwboot > only the NSA310 and NSA320 It is if you get any response such as receiving the image.by bodhi - Debian
Hold on! egiga0: link down reg(0, 0) = 0x1140 mvEthPhyRegWrite(mvBoardPhyAddrGet(ethPortNum),22 ,0x0); mvEthPhyRegWrite(mvBoardPhyAddrGet(ethPortNum),0,0x9140); // reset eth-phy mvEthPhyRegRead(mvBoardPhyAddrGet(ethPortNum), 0, &phy_reg); printk(KERN_ERR"reg(0, 0) = 0x%x\n", phy_reg); Where did that bit go :) did they overwrite something right before thby bodhi - Debian
JohnnyUSA Wrote: ------------------------------------------------------- > @bodhi, thing is, i've tested Pengu's rootfs > myself and had the same problem. Ah! OK then, the theory is shot :) I won't bother with the shutdown anymore.by bodhi - Debian
superelchi, I've booted back to Zyxel stock on my NSA325v2 and then shutdown and observed this. / # /sbin/halt led_state_map_addr = 4e Jul 23 08:50:57 NSA325-v2 linuxrc: starting pid 2781, tty '': '/etc/init.d/rc.shutdown' / # Starting "/etc/init.d/zypkg_controller.sh". Stopping all zypkgs via "/etc/init.d/zypkg_controller.sh" ... - shutdby bodhi - Debian
bobafetthotmail & others, I'm looking to get a JTAG header to install on NSA325v2. Would this fit? http://www.ebay.com/itm/20-Pcs-2-54mm-Pitch-10x2-20Pin-ISP-Download-Header-JTAG-I-O-Socket-DIY-DC3-20P-/271675139331?pt=LH_DefaultDomain_0&hash=item3f4119a503 This product says it has 2.54 mm pitch. The unpopulated 20 pins on the NSA325 board seems to be a standard JTAG connectby bodhi - uBoot
JohnnyUSA Wrote: ------------------------------------------------------- > Finally home and i've tried superelchi's solution > with phypoke and fixed ip, works like a charm. So, > until you guys work out something better, i'm > happy with what we have at the moment ;) > > Cheers! > > PS: It seems my box doesn't want to resume after > poweby bodhi - Debian
superelchi, Thanks for trying, I'll upload a different one in a few days!by bodhi - Debian
UPDATE: I've removed the binary that superelchi tried below. It was a wrong binary for this box :)by bodhi - Debian
Vinay Wrote: ------------------------------------------------------- > He he. That worked. I got this output from the > plug while booting up. > > > vinay@MediaPC ~ $ nc -kup 6666 192.168.10.112 > 6666 > > U-Boot 2010.09 (Oct 23 2010 - 11:51:16) > Marvell-PinkPogo by Jeff Doozan > Hit any key to stop autoboot: 0 > (Re)start USB... > USB: Reby bodhi - Debian
desigabri Wrote: ------------------------------------------------------- > thanks for replay, and for the answers, > > 1) this is about dpkg: > > root@debian-jessi:/media/root/rootfs/boot318# > root@debian-jessi:/media/root/rootfs/boot318#dpkg > -i linux-image-3.18.5-kirkwood-tld-1_1_armel.deb > dpkg: errore nell'elaborare l'archivio > linux-image-by bodhi - Debian
desigabri Wrote: ------------------------------------------------------- > Hello Bodhi, > > I really had hard time understanding the steps to > make the usb-key, anyway I've arrived using the > 3.18 rootfs.tar file and my NSA-325 now runs > Debian. > > I wanted to try the 4.1.0 kernel, but I haven't > found any 4.1.0 rootfs tar file so I suppose Iby bodhi - Debian
pbg4. Interesting! thanks for the info. I really not paying close attention to sensors at all (never have the needs). And BTW the 6281 HW specs doc is available, the 6282 is still under NDA.by bodhi - Debian
Vinay Wrote: ------------------------------------------------------- > How do I change the typo in fw_setenv? The same way you did when changing u-boot envs in Debian for netconsole. The 1st command sets the new variable, the 2nd one erase the wrong variable. fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderrby bodhi - Debian
Davide, Chainloading u-boots using more modern versions is difficult (due to structural changes). You could try recompiling my u-boot version as is, and name it differently to identify it. See if you can do that first. And then start changing the code a little, try it. Keep doing this until it stops working. That's when you know it has been changed in a way (memory locations were substantby bodhi - uBoot
Vinay, > After i shut > down the plug, it just wouldn't start up properly. > The plug would just show the amber light even > after half an hour. If the swap partition was created as the 1st partition then I think it was your problem (check it using fdisk on Mint). The rootfs must be the 1st partition. However, if you use a swap file then you will not have this problem.by bodhi - Debian
superelchi, > What I still do not understand: why is it working > for Pengu and not for Johnny and me - hardware > looks exactly the same. On Pengu's box the > register woodoo seems to work as on bootup the phy > is initialized... Yeah :) this has been a puzzle, as though pengu's box is a different 310S variation, or has different u-boot.by bodhi - Debian
Hi pbg4, On my iConnect, the current kernel (4.1.0-tld-1) lm63 module did not need CONFIG_KIRKWOOD_THERMAL to work correctly with lm-sensors (which I believe using sysfs since a few versions ago). Jul 19 18:12:55 tldDebian daemon.info sensord: Chip: lm63-i2c-0-4c Jul 19 18:12:55 tldDebian daemon.info sensord: Adapter: mv64xxx_i2c adapter Jul 19 18:12:55 tldDebian daemon.info sensord:by bodhi - Debian
Hi pbg4, > if this is working, there would be an alternative > to get the temperature of the soc with i2cget > commands > from the mcu, You meant this config will enable the kernel builtin thermal sensor? Instead of using i2cget commands like this: echo "CPU Temperature" $(($(sudo /usr/sbin/i2cget -y 0x0 0x0a 0x07))) "C"by bodhi - Debian
@superelchi, > Can we persuade the driver somehow to tell us > which chip it detected? I looked at Marvell latest driver in Linux 4.1. Looks like it does not have the exact 88e1318 in the list of chips that needs special care (using reg-init). We'll have to use the 88e1510 for it to detect the chip model! otherwise, it falls back to the Marvell default handling.by bodhi - Debian
osa, > nsa310s_phy_fixup(struct phy_device *phydev) > +{ > + int err; > + int temp; > + /* go to page 3 */ > + err = phy_write(phydev, 22, 3); > + if (err < 0) > + return err; > + /* read page 3, register 17 */ > + temp = phy_read(phydev, 17); > + /* clear bit 4, set bit 5 */ > +by bodhi - Debian
Vinay Wrote: ------------------------------------------------------- > I tried setting up net console by reading the > tutorial here. > http://forum.doozan.com/read.php?3,14,14 > > I cant get it working. I'm stuck at this part and > don't understand it. > > Note: the above command will start a 'view-only' > console. If you want to be ablby bodhi - Debian
@Johnny & superelchi, Do you have a picture of the LAN chip in your box?by bodhi - Debian
Vinay, Everything looks great! except that your USB rootfs right now is Ext3, but your u-boot env still set to Ext2. It works for booting, but Ext3 journal is not used. dmesg [ 21.783978] EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2 u-boot envs usb_rootfstype=ext2 Since you have only one Pogo, and no serial console, I'm hesitate to suggest installing new u-boot.by bodhi - Debian
Now since it's working with the work around. I'd suggest the next step is to look at the DTS. In the DTS, these register values were specified already in eth PHY. What would be the difference that caused Debian to ignore these values? I am suspecting that the "compatible" field was the culprit. So I've added both chips to the list. However, we don't know for sureby bodhi - Debian
superelchi, > The "NSA-310S" is internally names "STG315" and I > assume it's mapped to a #define > "CONFIG_MitraStar_STG315" (didn't find out where > this is done so far). > > As you also found there is: > > STG315_Kernel.config:# CONFIG_ZYXEL_POWER_RESUME > is not set > and that's because in > trunk/linby bodhi - Debian
It seems as though you guys have different versions of the NSA310S :) Furthermore, I'm thinking even though GPIO 47 and 49 are common for NSA3xx, they might not be used in the 310S that is not working (I am still digging in GPL code, and we don't know if this GPL reflects the latest FW). Wish I have my NSA325 at home to double check this too. I've attached the GPIO tool binary iby bodhi - Debian
Vinay Wrote: ------------------------------------------------------- > Sorry. I think I messed up. I didn't do this part > you asked me to. > After booted into Debian successfuly, then > move on to install new u-boot. > > I'm also getting some locale errors. I tried > installing locales, but it does not go away. > Will look at how to install uboot firby bodhi - Debian