First I would like to thank all people like Bodhi en many more to provide means to keep legacy hardware up and running.
Unfortunately to keep it running is something more challenging.
After a lot of fiddling en trying I managed to have a working PogoplugPro (oxnas) booting from USB.
I had it installed with U-Boot 2013.10-tld-5 and Debian running.
In an attempt to update the uboot to 2015.10 I managed to really brick the pogo.
What went wrong?
I had ssh ´d into debian on the pogo and created some directories to manage the files. Copied uboot.2015.10-tld-2.ox820.bodhi.tar to it with scp from my desktop system. (I could not download it directly from dropbox with wget)
untarred it etc and entered the command to erase the MTD0 device (I assumed this is the SPL aera, but it does not matter anyway)
I got this output:
Because the result did not show values that I would expect (...@0x and 100%) and because the memory area seemed way beyond 0x000000 I made the assumption that a reboot could be an option. ( I know Bodhi advised otherwise...)
How wrong appeared that assumption to be...................
There was no reboot. Only a dead Pogoplug. No Led, no serial, no nothing.
I am out of options now.
The only hope I have is that I may be able to boot from sata. Is that an option?
Or maybe revival using JTAG ?
Or should I accept that I really killed the device beyond revival......
The sata way is more or less described here: https://forum.doozan.com/read.php?2,32994
however I am lost at:
8b.) Run Sata uboot SCRIPT
But before I will attempt all this I would like to know if the sata boot procedure, if implemented properly, would make a revival of the box possible.
I have been working with single board computers and electronics way long ago, so assume I could manage a JTAG recovery. However I have found no information about that with reference to the PogoPro system. Only de V4. And I assume that this procedure cannot be used as is for the PogoPro. And it is already bricked, no need to repeat it ;)
I have also noticed the mentioning of kwboot. But have no idea of that could do the job.
Hoping for the best.
hacksome
Edit 1:
I have tried kwboot with the standard serial interface but got an error message because of image format incompatibility.
I assumed that the -p option would take care of the adjustment when using a standard image. But that assumption appeared to be false as well I guess.
At openwrt.org I read : https://openwrt.org/_export/xhtml/docs/techref/hardware/soc/soc.oxnas
So using kwboot to revive or program Oxnas devices seems undiscovered territory.
I have no idea of the detailed inner workings of kwboot. I have used X,Y and Z-modem protocols ages ago, know about hex S records for serial transfer to load ROM images to targets but that does not help me much now.
Maybe there is more needed then simple adjusting offset and is a more intelligent conversion needed from .img to .kwb format. More information is welcome.
Some further investigation about JTAG options seems to run into a dead end as well.
I have found general information about the chip used: NAS7820. The description matches the PogoPro functions and the information states that JTAG functionality is available on the chip.
I have scrutinized the PCB and found various scattered TPxx points on it but have no clue which function they have or where they are connect with.
The missing link appears to be how to connect a JTAG probe to the board. If that is even possible.... I also read that not all vendors have made JTAG functionality available. So it could be possible that JTAG support on the PogoPro ( I confirmed it is a Pro, because it has a miniPCI card for wireless) is not physically accessible. Or at best: not easy to find.
So my only hope left now is the sata boot. But before I try that I would like confirmation that it is a viable option.
hacksome
Edit 2:
I found some info about JTAG and PogoPro:
looking at the PCB I saw a none installed header with 14 pins labeled HD5. A search for this :
https://archlinuxarm.org/forum/viewtopic.php?t=1640
2 things: the HD5 seems to be the JTAG header, but info about the pin layout is not available.....
The other thing is that it is indicated in the thread that sata boot might work.........
The latter however is not verified as far as I know.
to be continued?
I would gladly want to figure out the JTAG route. Even if that is more complicated.
So any info about the actual JTAG pinout would be appreciated.
hacksome
Unfortunately to keep it running is something more challenging.
After a lot of fiddling en trying I managed to have a working PogoplugPro (oxnas) booting from USB.
I had it installed with U-Boot 2013.10-tld-5 and Debian running.
In an attempt to update the uboot to 2015.10 I managed to really brick the pogo.
What went wrong?
I had ssh ´d into debian on the pogo and created some directories to manage the files. Copied uboot.2015.10-tld-2.ox820.bodhi.tar to it with scp from my desktop system. (I could not download it directly from dropbox with wget)
untarred it etc and entered the command to erase the MTD0 device (I assumed this is the SPL aera, but it does not matter anyway)
I got this output:
root@debian:/home/pogobackup/tmp# /usr/sbin/flash_erase /dev/mtd0 0x0 6 Erasing 128 Kibyte @ 7f623f5c00000064 -- 6 % complete
Because the result did not show values that I would expect (...@0x and 100%) and because the memory area seemed way beyond 0x000000 I made the assumption that a reboot could be an option. ( I know Bodhi advised otherwise...)
How wrong appeared that assumption to be...................
There was no reboot. Only a dead Pogoplug. No Led, no serial, no nothing.
I am out of options now.
The only hope I have is that I may be able to boot from sata. Is that an option?
Or maybe revival using JTAG ?
Or should I accept that I really killed the device beyond revival......
The sata way is more or less described here: https://forum.doozan.com/read.php?2,32994
however I am lost at:
8b.) Run Sata uboot SCRIPT
./disk_create_shv
But before I will attempt all this I would like to know if the sata boot procedure, if implemented properly, would make a revival of the box possible.
I have been working with single board computers and electronics way long ago, so assume I could manage a JTAG recovery. However I have found no information about that with reference to the PogoPro system. Only de V4. And I assume that this procedure cannot be used as is for the PogoPro. And it is already bricked, no need to repeat it ;)
I have also noticed the mentioning of kwboot. But have no idea of that could do the job.
Hoping for the best.
hacksome
Edit 1:
I have tried kwboot with the standard serial interface but got an error message because of image format incompatibility.
root@john-NUC6CAYH:/home/kwboot/kwboot-tool# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.spl.2013.10.ox820.850mhz.mtd0.img -p uboot.spl.2013.10.ox820.850mhz.mtd0.img: Invalid image.
I assumed that the -p option would take care of the adjustment when using a standard image. But that assumption appeared to be false as well I guess.
At openwrt.org I read : https://openwrt.org/_export/xhtml/docs/techref/hardware/soc/soc.oxnas
..... kwboot-like serial recovery yet needs to be found…
So using kwboot to revive or program Oxnas devices seems undiscovered territory.
I have no idea of the detailed inner workings of kwboot. I have used X,Y and Z-modem protocols ages ago, know about hex S records for serial transfer to load ROM images to targets but that does not help me much now.
Maybe there is more needed then simple adjusting offset and is a more intelligent conversion needed from .img to .kwb format. More information is welcome.
Some further investigation about JTAG options seems to run into a dead end as well.
I have found general information about the chip used: NAS7820. The description matches the PogoPro functions and the information states that JTAG functionality is available on the chip.
I have scrutinized the PCB and found various scattered TPxx points on it but have no clue which function they have or where they are connect with.
The missing link appears to be how to connect a JTAG probe to the board. If that is even possible.... I also read that not all vendors have made JTAG functionality available. So it could be possible that JTAG support on the PogoPro ( I confirmed it is a Pro, because it has a miniPCI card for wireless) is not physically accessible. Or at best: not easy to find.
So my only hope left now is the sata boot. But before I try that I would like confirmation that it is a viable option.
hacksome
Edit 2:
I found some info about JTAG and PogoPro:
looking at the PCB I saw a none installed header with 14 pins labeled HD5. A search for this :
https://archlinuxarm.org/forum/viewtopic.php?t=1640
2 things: the HD5 seems to be the JTAG header, but info about the pin layout is not available.....
The other thing is that it is indicated in the thread that sata boot might work.........
The latter however is not verified as far as I know.
to be continued?
I would gladly want to figure out the JTAG route. Even if that is more complicated.
So any info about the actual JTAG pinout would be appreciated.
hacksome