Debian Wheezy on Pogoplug Pro V3 March 04, 2015 08:40AM |
Registered: 10 years ago Posts: 54 |
Re: Debian Wheezy on Pogoplug Pro V3 March 04, 2015 02:46PM |
Admin Registered: 13 years ago Posts: 19,007 |
Re: Debian Wheezy on Pogoplug Pro V3 March 08, 2015 11:59PM |
Registered: 10 years ago Posts: 54 |
Re: Debian Wheezy on Pogoplug Pro V3 March 09, 2015 12:55AM |
Admin Registered: 13 years ago Posts: 19,007 |
Re: Debian Wheezy on Pogoplug Pro V3 March 09, 2015 01:53AM |
Registered: 10 years ago Posts: 54 |
Re: Debian Wheezy on Pogoplug Pro V3 March 09, 2015 02:22AM |
Registered: 10 years ago Posts: 54 |
Quote
bodhi
1. uBoot envs config and mtd partitions must be defined as followed in your rootfs
cat /etc/fw_env.config # pogoplug v3 /dev/mtd0 0x00100000 0x20000 0x20000 cat /proc/mtd dev: size erasesize name mtd0: 00e00000 00020000 "boot" mtd1: 07200000 00020000 "data"
If you don't have /etc/fw_env.config file in your system, then you are running either stock Pogo OS, or earlier version of Arch Linux ARM. Go ahead and create this file with the above content. MTD parts are not importan for booting and it can be adjusted later.
2. The env image pogopro_uboot_env.img should only be flashed if your rootfs has FDT kernel. If your kernel is an older non-FDT kernel then do not flash this env image. If you plan to run with the new rootfs then flash this image.
3. Be sure to save your current uBoot image in mtd0, or have a backup image saved somewhere as precaution.
Re: Debian Wheezy on Pogoplug Pro V3 March 09, 2015 01:28PM |
Registered: 10 years ago Posts: 1,037 |
Re: Debian Wheezy on Pogoplug Pro V3 March 09, 2015 02:51PM |
Admin Registered: 13 years ago Posts: 19,007 |
Re: Debian Wheezy on Pogoplug Pro V3 March 11, 2015 01:53AM |
Registered: 10 years ago Posts: 54 |
Quote
bodhi
9. Erase 1 block starting 0x00100000 (See caveat in step 2, do not do this step this if the kernel is stock kernel, or not a FDT kernel)
/usr/sbin/flash_erase /dev/mtd0 0x00100000 1 Erasing 128 Kibyte @ 100000 -- 100 % complete
10. Flash uboot environment to 0x00100000 (See caveat in step 2, do not flash this if the kernel is not FDT)
/usr/sbin/nandwrite -s 1048576 /dev/mtd0 pogopro_uboot_env.img Writing data to block 8 at offset 0x100000
Re: Debian Wheezy on Pogoplug Pro V3 March 11, 2015 02:03AM |
Admin Registered: 13 years ago Posts: 19,007 |
> /usr/sbin/flash_erase /dev/mtd0 0x00100000 1 > > Erasing 128 Kibyte @ 100000 -- 100 % complete >>
> /usr/sbin/nandwrite -s 1048576 /dev/mtd0 > pogopro_uboot_env.img > > Writing data to block 8 at offset 0x100000 >> [/quote]
Re: Debian Wheezy on Pogoplug Pro V3 March 11, 2015 02:38AM |
Registered: 10 years ago Posts: 54 |
Re: Debian Wheezy on Pogoplug Pro V3 March 11, 2015 08:25AM |
Registered: 10 years ago Posts: 54 |
Quote
bodhi
INSTALLATION:
Installation can be done on any Linux box, with a fresh USB drive (SD card or HDD would work fine too). It is assuming the USB drive is mounted at /media/sdb1.
1. Format a new Ext3 USB drive, and label it rootfs. Note: if your existing uBoot env for rootfs type is ext2, then you might want to keep it consistent and use Ext2 USB drive. It will work with Ext3 drive without problem, though.
For example:
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts rootfstype=ext2
2. Mount the drive on a Linux box. As root user, cd to top level directory and extract it.
cd /media/sdb1 tar -xjf Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
3. edit /media/sdb1/etc/fstab entry for /dev/root to match the rootfstype of your usb_rootfstype (however, you can keep it as Ext2 without problem in booting an Ext3 partition).
/dev/root / ext2 noatime,errors=remount-ro 0 1
4. Create uImage with embbeded DTB to run with older u-boot. Please see Note 2 below if you are running this kernel witht the new U-Boot.
Pogo Pro vs. Pogo Classic: If you're installing this on a Pogo V3 Classic (no PCI), replace the ox820-pogoplug-pro.dtb below with ox820-pogoplug-classic.dtb.
cd /media/sdb1/boot cp -a zImage-3.17.0-oxnas-tld-1 zImage-3.17.0-oxnas-tld-1.fdt cat dts/ox820-pogoplug-pro.dtb >> zImage-3.17.0-oxnas-tld-1.fdt mkimage -A arm -O linux -C none -T kernel -a 0x60008000 -e 0x60008000 -n 'Linux-3.3.17.0-oxnas-tld-1' -d zImage-3.17.0-oxnas-tld-1.fdt uImage sync
Quote
bodhi
Flashing Instruction:
1. uBoot envs config and mtd partitions must be defined as followed in your rootfs
cat /etc/fw_env.config # pogoplug v3 /dev/mtd0 0x00100000 0x20000 0x20000 cat /proc/mtd dev: size erasesize name mtd0: 00e00000 00020000 "boot" mtd1: 07200000 00020000 "data"
If you don't have /etc/fw_env.config file in your system, then you are running either stock Pogo OS, or earlier version of Arch Linux ARM. Go ahead and create this file with the above content. MTD parts are not importan for booting and it can be adjusted later.
2. The env image pogopro_uboot_env.img should only be flashed if your rootfs has FDT kernel. If your kernel is an older non-FDT kernel then do not flash this env image. If you plan to run with the new rootfs then flash this image.
3. Be sure to save your current uBoot image in mtd0, or have a backup image saved somewhere as precaution.
Dumping NAND mtd0:
nanddump -nf mtd0 /dev/mtd0
4. Be sure there is no bad block in the first 1M of your NAND (check dmesg). This is very important, if there is bad block in the first 1M, don't flash u-boot, because you will almost certainly brick your box. Please post your question here (there is a work around for it).
Example of bad block in mtd0:
dmesg | grep -i 'bad' [ 2.413231] Scanning device for bad blocks [ 2.417731] Bad eraseblock 3 at 0x000000060000
This bad block resides within mtd0 (block 0 to block 7). So u-boot should not beflashed.
5. Extract the archive to /tmp
cd /tmp tar -xf uboot.2013.10-tld-4.ox820.bodhi.tar
Be extra careful with the next 5 commands, you should see output that look like below in steps 6 through 10. If there is error, then do not reboot, post your problem here so we can help.
6. Erase 6 blocks on mtd0
/usr/sbin/flash_erase /dev/mtd0 0x0 6 Erasing 128 Kibyte @ a0000 -- 100 % complete
7. Flash encoded spl stage1 to 0x0
/usr/sbin/nandwrite /dev/mtd0 uboot.spl.2013.10.ox820.850mhz.mtd0.img Writing data to block 0 at offset 0x0
8. Flash u-boot to 0x40000
/usr/sbin/nandwrite -s 262144 /dev/mtd0 uboot.2013.10-tld-4.ox820.mtd0.img Writing data to block 2 at offset 0x40000 Writing data to block 3 at offset 0x60000 Writing data to block 4 at offset 0x80000 Writing data to block 5 at offset 0xa0000
9. Erase 1 block starting 0x00100000 (See caveat in step 2, do not do this step this if the kernel is stock kernel, or not a FDT kernel)
/usr/sbin/flash_erase /dev/mtd0 0x00100000 1 Erasing 128 Kibyte @ 100000 -- 100 % complete
10. Flash uboot environment to 0x00100000 (See caveat in step 2, do not flash this if the kernel is not FDT)
/usr/sbin/nandwrite -s 1048576 /dev/mtd0 pogopro_uboot_env.img Writing data to block 8 at offset 0x100000
Re: Debian Wheezy on Pogoplug Pro V3 March 11, 2015 04:28PM |
Admin Registered: 13 years ago Posts: 19,007 |
> cd /media/sdb1/boot > cp -a zImage-3.17.0-oxnas-tld-1 > zImage-3.17.0-oxnas-tld-1.fdt > cat dts/ox820-pogoplug-pro.dtb >> > zImage-3.17.0-oxnas-tld-1.fdt > mkimage -A arm -O linux -C none -T kernel -a > 0x60008000 -e 0x60008000 -n > 'Linux-3.3.17.0-oxnas-tld-1' -d > zImage-3.17.0-oxnas-tld-1.fdt uImage > sync >> [/quote]
mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-3.18.5-oxnas-tld-1 -d /media/sdb1/boot/vmlinuz-3.18.5-oxnas-tld-1 /media/sdb1/boot/uImage sync
Re: Debian Wheezy on Pogoplug Pro V3 March 12, 2015 12:22AM |
Registered: 10 years ago Posts: 54 |
Re: Debian Wheezy on Pogoplug Pro V3 March 12, 2015 03:51AM |
Registered: 10 years ago Posts: 54 |
Quote
bodhi
INSTALLATION:
A. Installation to run with new U-Boot in NAND (see new U-Boot thread here)
1. Backup your current uImage and uInitrd and other kernel files. In the /boot directory, these are files for your current kernel (xx.xx.xx is the version number):
uInitrd
uImage
initrd.img-xx.xx.xx-xxx
System.map-xx.xx.xx-xxx
vmlinuz-xx.xx.xx-xxx
config-xx.xx.xx-xxx
2. Extract the kernel in the archive:
cd /boot tar -xjf linux-3.18.5-oxnas-tld-1-bodhi.tar.bz2
3. Create a dts directory for the dtb files
cd /boot mkdir dts mv ox820-pogoplug-pro.dtb dts/ mv ox820-pogoplug-classic.dtb dts/
4. And install it with dpkg. If you encounter error with flash-kernel when running dpkg, then remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):
apt-get remove flash-kernel dpkg -i linux-image-3.18.5-oxnas-tld-1_1_armel.deb
5. Create uImage and uInitrd manually:
mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-3.18.5-oxnas-tld-1 -d /boot/vmlinuz-3.18.5-oxnas-tld-1 /boot/uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-3.18.5-oxnas-tld-1 -d /boot/initrd.img-3.18.5-oxnas-tld-1 /boot/uInitrd
6. Setup U-Boot envs:
Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrong values will lock you out of the box until you can connect a serial console.
Pogo Pro vs. Pogo Classic: If you're installing this on a Pogo V3 Classic (no PCI), replace the ox820-pogoplug-pro.dtb below with ox820-pogoplug-classic.dtb.
Set up booting envs:
fw_setenv uinitrd_addr '0x60e00000' fw_setenv uimage_addr '0x60500000' fw_setenv dtb_addr '0x62c00000' fw_setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10' fw_setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr' fw_setenv dt_load_dtb 'ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb' fw_setenv dt_load_initrd 'ext2load usb 0:1 $uinitrd_addr /boot/uInitrd' fw_setenv dt_load_uimage 'ext2load usb 0:1 $uimage_addr /boot/uImage' fw_setenv dt_usb_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm' fw_setenv dt_usb_bootcmd 'run usb_set_bootargs; run dt_usb_boot' fw_setenv dt_bootcmd_usb 'usb start; run dt_usb_bootcmd; usb stop; reset' fw_setenv bootcmd 'run dt_bootcmd_usb'
7. Sync. Double check your u-boot envs, make sure there is no error. And reboot
sync fw_printenv reboot
Re: Debian Wheezy on Pogoplug Pro V3 March 12, 2015 02:48PM |
Admin Registered: 13 years ago Posts: 19,007 |
Re: Debian Wheezy on Pogoplug Pro V3 March 13, 2015 11:36AM |
Registered: 10 years ago Posts: 54 |
Re: Debian Wheezy on Pogoplug Pro V3 March 13, 2015 12:25PM |
Registered: 10 years ago Posts: 1,037 |
Re: Debian Wheezy on Pogoplug Pro V3 March 13, 2015 03:39PM |
Admin Registered: 13 years ago Posts: 19,007 |
Re: Debian Wheezy on Pogoplug Pro V3 March 14, 2015 12:16AM |
Registered: 10 years ago Posts: 54 |
Re: Debian Wheezy on Pogoplug Pro V3 April 03, 2015 01:24PM |
Registered: 9 years ago Posts: 5 |
Re: Debian Wheezy on Pogoplug Pro V3 April 03, 2015 04:30PM |
Admin Registered: 13 years ago Posts: 19,007 |
Re: Debian Wheezy on Pogoplug Pro V3 April 03, 2015 06:58PM |
Registered: 9 years ago Posts: 429 |
Re: Debian Wheezy on Pogoplug Pro V3 May 13, 2015 12:47AM |
Registered: 10 years ago Posts: 54 |
Re: Debian Wheezy on Pogoplug Pro V3 May 13, 2015 02:54AM |
Admin Registered: 13 years ago Posts: 19,007 |
Re: Debian Wheezy on Pogoplug Pro V3 May 13, 2015 12:18PM |
Registered: 10 years ago Posts: 54 |
Re: Debian Wheezy on Pogoplug Pro V3 May 13, 2015 04:11PM |
Admin Registered: 13 years ago Posts: 19,007 |
Re: Debian Wheezy on Pogoplug Pro V3 May 19, 2015 12:22AM |
Registered: 10 years ago Posts: 54 |
distron
Re: Debian Wheezy on Pogoplug Pro V3 September 27, 2015 03:18AM |
Re: Debian Wheezy on Pogoplug Pro V3 September 27, 2015 02:15PM |
Admin Registered: 13 years ago Posts: 19,007 |
usb_init=run usb_scan; setenv usb_root LABEL=ROOTFSYou will need to label your USB Debian rootfs partition that way. Assuming on another Linux box, it is assigned sdb1
tune2fs -L ROOTFS /dev/sdb1