joerg_999 Wrote: ------------------------------------------------------- > Hi mrmazak > i did this repair job in the middle of 2015, but > it should work also with new raspbian an aktual > openocd. The only thing i didnt try is with newer > Pis. > The last one was:(B,B+700Mhz, RPI2 900Mhz and RPI3 > 1200Mhz) with simply standard clock Speed of the > Raspis. >by mrmazak - uBoot
I got the same errors with Jessie. and current build of openOCD.(v10) I tried to build with the other branch (v6.0.1) on github, that didnt go so well. It gave error that the only interface programed in build was buspirate. I got little further with the apt-get repository version (v8) but I had to comment out some config lines because errors said unknown command. But it did show connectionby mrmazak - uBoot
Maybe I need an older version of raspian OS. openOCD gives deprication errors. and fails to connect to JTAG. pi@raspberrypi:~ $ telnet 127.0.0.1 4444 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. Open On-Chip Debugger > pogo_init DEPRECATED! use 'adapter assert' not 'jtag_reset' unexpected Feroceon EICE version signature DEPREby mrmazak - uBoot
Is the telnet interface needed, can it be a second ssh or term screen. I'm having trouble setting up telnetd on my pi.by mrmazak - uBoot
hello, I am tring to recover my pogo plug e02. i bought it used on ebay, i never had it working. I almost got Dohi's debian rootfs to load, through tftpboot, but was stuck on loadin kernel. I was impatient and tried frist thing i saw for flashing u-boot from openwrt forum. this made device corrupt nand enven further than it was. I am left with jtag as my last hope ( Help me Old Beby mrmazak - uBoot
Yeah, I got ahead of my knowledge of this device. I did setup jtag as the guide says. https://forum.doozan.com/read.php?3,21789,page=1 But planed to do it from the pi itself. So I think 2 terminal sessions is correct?. Not three. So telnet step would not be relevant? I don't have a 8 pin plug for the connection . And to buy the ones I found on amazon would be same cost as thisby mrmazak - uBoot
Yes, there is one quick flash of the LED when plugged in. Not from the big led(led4), from the lan port lights and one on the board(led3) Lan port also has lights while connectedby mrmazak - uBoot
i did bad things t this thing now. got frustrated and did tftpboot 0x800000 pogo.kwb(short name I put for 2017 bootloader) nand erase 0x0 0xa4fff nand write.e 0x800000 0x0 0x80000 addresses found on openwrt flashing directions site. Then did reset. Now I get no response on serial console. now i wil just stop, as i thin there is more more to do??? Maybe jtag, but that still neby mrmazak - uBoot
fantastic. I of cource made a mistake. I cp the kernel files to "tftproot" folder, and servers root is setup in "tftpboot" folder. fixed that and kernel loaded, but is halted at "booting Kernel" Welcome to minicom 2.7.1 OPTIONS: I18n Compiled on Aug 13 2017, 15:25:34. Port /dev/ttyS0, 17:27:36 Press CTRL-A Z for help on special keys U-Bby mrmazak - uBoot
When I use term on other box on network, and I do tftp $server_ip I get the tftp prompt Then I command 'get uImage' the file is transfered I can only assume that the tftpboot command should have been able to connect also. Maybe need to chown the files or something. I'll try that after work. Thanksby mrmazak - uBoot
This Pogo is failing to connect to my network. I find out. During the tftp load it just keeps trying and then stops with message Retry count exceeded; starting again *** ERROR: 'eth1addr' not set So I added setenv 'eth1addr' (router ip) This stopped the error message, but still does not load from tftp. Router log does not show any connection to box either..by mrmazak - uBoot
I have setup tftp server and found an example on using it to boot kernel, but have not tried it yet. Has anything from this guide need updated? https://forum.doozan.com/read.php?3,28772,29034#msg-29034by mrmazak - uBoot
Tftp method might be better option. Gives more room for recovery before needing JTAG.by mrmazak - uBoot
different usb drive with rootfs confirmed to work on my nsa320 ( i know it would not boot) gives same 'block device usb 0 not supported' message didn't see your earlier response, ignore this post. hahahaby mrmazak - uBoot
Maybe I should try to make rootfs again. This line seems to indicate the usb stick is not recognized. It is ext3, like Debian release thread says. CE>> boot Unknown command 'usb' - try 'help' ** Block device usb 0 not supported ## Booting image at 00800000 ... Bad Magic Number Unknown command 'usb' - try 'help'by mrmazak - uBoot
seems to not recognize the 'usb' cmd in 'usb boot' CE>> reset U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16) U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690D60 Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0by mrmazak - uBoot
the 4th line , the one with the if statement was 'too many args" CE>> CE>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=seri' CE>> setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' CE>> setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd' CE>by mrmazak - uBoot
Here we go. You specified to do step 4 because of stock uboot. Makes me need to ask. Once I am able to flash new uboot, will I then update rootfs and undo step 4?by mrmazak - uBoot
I did find a post from 2014 mentioning that from serial console you can set env and command boot from usb, but it was not enough details for me I suppose. I will keep at it. I do find a couple posts and threads that say how to run Jeff's scripts to install Debian and update uboot. Bit they start with a running device with ssh access All I have access to at the moment is serial console.by mrmazak - uBoot
I just received a used pogo e02, I wanted to to convert this to a slim player device by putting debian onto it first. I expected stock is to have been on the plug, but it seems to have corrupt is as of now, stock is not booting. No Pogo server running on ip address of device, my router identify it as "debian", can't connect with ssh, default password is failing. I have seriby mrmazak - uBoot
bodhi Wrote: ------------------------------------------------------- > QuoteIs it advisable to set min protocol to SMB > v2 on a samba server on Pogo v4? > > Yes. Wow, this is the whole reason I put debian onto my nsa320. The stock nas os was stuck on smb v1, I had hooked the old nas up after having it mothballed for about 7 years because HD has failed. Both windowsby mrmazak - Debian
Good to know you are getting it working. I have just last weekend (Nov 7&8) flashed my nsa320 over to buster . The serial console was easy to setup from an extra raspberry pi I had , so didn't need to buy usb-tty adapter.by mrmazak - Debian
Thanks. I had the leds working, but still needed a clue for the power button. I have a very simple halt now when tap button. I saw the example with >< 2sec triggers and flashing blue light. Wow ok anything you want, you just need to code it. Great.by mrmazak - Debian
Power button Reset button Lights None seem to respond. Need to use ssh or console to command halt. I found some thread that mentions editing an *.rc file , to make lights and buttons to work. From "nsa325" to "nsa320" . Don't know if there is other configs that need to be tweaked. Will booting from the usb rootfs, cause thumb drive to fail in short tby mrmazak - Debian
some differences in /proc/mtd. is it need to change. Guide says mtd0: 00100000 00020000 "u-boot" Without changes made mine says mtd0: 00100000 00020000 "uboot" does that name need changed? Step 5 of u-boot flash guide say to extract the archive. to /tmp. I must have missed the step of transfering the uboot to the rootfs. i ended up useing scp to push fby mrmazak - Debian
Now I am at debian log-in. U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:46:11 -0700) ZyXEL NSA320 2-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHY initialized on egiga0 Hit any key to stop autoboot:by mrmazak - Debian
Alright, so I need to search for distribution of kwboot from apt-get. Did not know that was an option. current console output from kwboot, When I halt to autoboot, prinenv, then command a boot, the Nas tries to boot from my USB loaded with rootfs ( I may have it wrong) reboots back to installed uboot not the kwbooted one, then continues to boot to stock system. here is log. pi@rby mrmazak - Debian
these outputs are from stock u-boot. Unless the install script from archlinux instaal modified it. The scripts do not look like the were supposed to have though. printenv output del.dog/irepebogym.txt boot console output if needed. console output more logs to come. but i did find other kwboot to use. For arm since i am runninng on a PI. this one DID get me to a boot from new uboot.by mrmazak - Debian