Boot Issues/Solutions ( all deviced BUT usb drive MUST be unplugged?) ppv4 mobille

Hey guys im not new to arm distros been running arch on my GoFlex Home for 2 years LOVE it :P
my issue is not unique ive heard many people complain about their devices only booting when ONLY the thubmbdrive/rootfs device is plugged, that sucks especially if your using services that want all filesystems mounted e.g. transmission/pogoplug services....
over at archlinux forums people shrug it off say Oh well **** happens but there has to be a way to work around this, i want to maybe put the arch kernel into nand, ramdisk that mounts filesystems in order maybe? at anyrate if there is anyone here who wants an actual solution or knows one please reply :D

*Devices*
Goflex Home- Transmission, vnc server(for kicks), Pogoplug services, Motion/home security DVR, 1.5TBNAS currently sshfs acess ONLY(archlinux)

PogoPlugMobileV4-Webmin, Transmission, Pogoplug services, Samba Server, cool red led+ green hearbeat,USBip(server for remote acess to usb devices) (archlinux)

*I Love ARM*

dbstrand24 Wrote:
-------------------------------------------------------
> Hey guys im not new to arm distros been running
> arch on my GoFlex Home for 2 years LOVE it :P
> my issue is not unique ive heard many people
> complain about their devices only booting when
> ONLY the thubmbdrive/rootfs device is plugged,
> that sucks especially if your using services that
> want all filesystems mounted e.g.
> transmission/pogoplug services....
> over at archlinux forums people shrug it off say
> Oh well **** happens but there has to be a way to
> work around this, i want to maybe put the arch
> kernel into nand, ramdisk that mounts filesystems
> in order maybe? at anyrate if there is anyone here
> who wants an actual solution or knows one please
> reply :D

Running Arch, the correct solution to make sure you boot the right disk drive while multiple disk drives are plugged in, is to use initrd (no need to take drastic measure as messing with mtd!).Arch Linux ARM does not set up to use this, so you'd need to create one yourself. Then create the uInitrd in the boot drive. Finally, use the disk label in bootargs. Without initrd, Linux kernel command line won't accept rootfs label.

See this thread:
http://forum.doozan.com/read.php?3,8044,8152#msg-8152

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

makes sense now i forgot, when i installed arch on the gfh mtd0 was replaced with a preconfigured uboot... Dude :P thanx bodhi

[root@m4dh4x0rz-PogoplugMobile-V4 ~]# fw_printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
CASset=min
MALLOC_len=1
ethprime=egiga0
load_nand=nboot 0x800000 0 0x200000
load_nand2=nboot 0x800000 0 0x500000
boot=bootm 0x800000
boot_nand=run load_nand boot || run load_nand2 boot
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
ethaddr=00:**:31:**:**:**
cesvcid=***********HEW7EG8YYT2476
ceboardver=PPV4A1
ipaddr=192.168.58.233
serverip=192.168.58.188
bootargs=console=ttyS0,115200 root=ubi0:rootfs ubi.mtd=4,2048 rootfstype=ubifs
stdin=serial
stdout=serial
stderr=serial
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=1
disaMvPnp=no
hddPowerCtrl=no
pcieTune=no
arcNumber=3960
mainlineLinux=yes
bootcmd=if usb start; then run alarm_boot; else nand read 0x800000 0x100000 0x73d0c; go 0x800000; fi
alarm_boot=ide reset; run alarm_revert; if ide part 0; then run alarm_ide; else setenv isDisk no; fi; run alarm_usb
alarm_revert=if fatls usb 0:1 /revert; then setenv mainlineLinux no; setenv arcNumber; setenv bootcmd run boot_nand; saveenv; reset; fi
alarm_args=setenv bootargs console=ttyS0,115200 root=$device rootwait rootfstype=ext3
alarm_which=if test $isDisk = yes; then setenv device /dev/sdb1; else setenv device /dev/sda1; fi
alarm_ide=if ext2load ide 0:1 0x800000 /boot/uImage; then setenv device /dev/sda1; run alarm_args; bootm 0x800000; else setenv isDisk yes; fi
alarm_usb=if ext2load usb 0:1 0x800000 /boot/uImage; then run alarm_which; run alarm_args; bootm 0x800000; fi


Great too late for this but i screwed the variables up i think...

stuck at flashing green light
*its midnight i have a headache lol*

ran

# fw_setenv usb_init "usb start; setenv usb_root LABEL=rootfs"

i either missed something cause ov my headache or i changed wrong variable



Edited 2 time(s). Last edit at 10/22/2013 01:57AM by dbstrand24.

Oh crap... i see what i did

Please tell me i dont need to jtag it...
No def no jtag :P uart/serial ... u boot should be able to be fixed w/o jtag...



Edited 2 time(s). Last edit at 10/22/2013 02:29AM by dbstrand24.

dbstrand24 Wrote:
-------------------------------------------------------
> Oh crap... i see what i did
>
> Please tell me i dont need to jtag it...
> No def no jtag :P uart/serial ... u boot should be
> able to be fixed w/o jtag...

You got it! UART booting to recover.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Fun stuffs lol how would one go about doing this on linux?
ive done jtag stuffs from windows... any sugestions on how to interface with the board? if i can i'll build the adapter, but i have no clue how uart works :P

this is hillarious its turned into a uboot thread lol MODS please move :P

This is a good place as any to start :P



Edited 2 time(s). Last edit at 10/22/2013 03:23AM by dbstrand24.

dbstrand24 Wrote:
-------------------------------------------------------
> Fun stuffs lol how would one go about doing this
> on linux?
> ive done jtag stuffs from windows... any
> sugestions on how to interface with the board? if
> i can i'll build the adapter, but i have no clue
> how uart works :P
>
> this is hillarious its turned into a uboot thread
> lol MODS please move :P

No need to build jtag. Just boot with UART serial and undo the envs that you did. See this thread again for UART booting:
http://forum.doozan.com/read.php?3,13603

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Ok got the idea ima head to bed thurs i'll order cables and with any luck i'll be up and running in a week or two, my pc has rs232 so i can probably just break out the multimeter and trial and error till i get tx/rx :P hell i need a new soldering iron and multimeter...

or ... http://www.amazon.com/PL2303HX-RS232-Cable-module-Converter/dp/B008AGDTA4/ref=pd_sim_cps_3



Edited 1 time(s). Last edit at 10/22/2013 03:33AM by dbstrand24.

dbstrand24 Wrote:
-------------------------------------------------------
> Ok got the idea ima head to bed thurs i'll order
> cables and with any luck i'll be up and running in
> a week or two, my pc has rs232 so i can probably
> just break out the multimeter and trial and error
> till i get tx/rx :P hell i need a new soldering
> iron and multimeter...

Ok, last post before I get some sleep :) you can definitely use 3 small pins ( the type that pins new shirts in boxes) and push them into the solder buttons, temporarily. You only need to to connect 3 wire clips to them, and connect the wires to the serial module converter (I did this on my Pogo Mobile, and it works well, no soldering needed). The serial pin outs are well known (see Arch site).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I know I dont HAVE to solder it :P but hey, if i muck something up again the interface will be useful :Pi've go millions of wires/spare parts/electronics :P i'll put together some kind of easy to connect interface

Bodhi :P

[m4dh4x0r@m4dh4x0rz-Desk ~]$ ssh root@192.168.0.46
The authenticity of host '192.168.0.46 (192.168.0.46)' can't be established.
RSA key fingerprint is 81:de:c3:09:1c:83:4c:e3:90:2a:6a:ac:21:de:94:41.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.46' (RSA) to the list of known hosts.
root@192.168.0.46's password:
~ #

HAHA idk how but some how it booted the stock pogo firmware lol

upon closer inspection of the install script :::

echo "## UPDATING ENVIRONMENT"
/usr/local/cloudengines/bin/blparam arcNumber=3960 > /dev/null
/usr/local/cloudengines/bin/blparam mainlineLinux=yes > /dev/null
/usr/local/cloudengines/bin/blparam bootcmd='if usb start; then run alarm_boot; else nand read 0x800000 0x100000 0x73d0c; go 0
/usr/local/cloudengines/bin/blparam alarm_boot='ide reset; run alarm_revert; if ide part 0; then run alarm_ide; else setenv is
/usr/local/cloudengines/bin/blparam alarm_revert='if fatls usb 0:1 /revert; then setenv mainlineLinux no; setenv arcNumber; se
/usr/local/cloudengines/bin/blparam alarm_args='setenv bootargs console=ttyS0,115200 root=$device rootwait rootfstype=ext3' >
/usr/local/cloudengines/bin/blparam alarm_which='if test $isDisk = yes; then setenv device /dev/sdb1; else setenv device /dev/
/usr/local/cloudengines/bin/blparam alarm_ide='if ext2load ide 0:1 0x800000 /boot/uImage; then setenv device /dev/sda1; run al
/usr/local/cloudengines/bin/blparam alarm_usb='if ext2load usb 0:1 0x800000 /boot/uImage; then run alarm_which; run alarm_args

I should have looked at my routers dhcp leases!! looks like it boots nand as a sort of back up, i didnt print the env after i re wrote it :P BUT looks like its all good :P still that first boot_cmd : /usr/local/cloudengines/bin/blparam bootcmd='if usb start; then run alarm_boot; else nand read 0x800000 0x100000 0x73d0c; go 0

saved me :P

Or NOT... damn it
now it wont boot ...



Edited 1 time(s). Last edit at 10/22/2013 11:44PM by dbstrand24.