[News]

News: Glomation introduced new wireless ready low cost GESBC-9260S

[davest]

davest

davest

Show davest's last posts.

Show general stats for davest.

• 
• Super Hero
• Posts: 22

I have read through the other topics but am too much of a newbe to linux to adapt them to what I need.

I am locked out of my 9260 because I ran a program right out of boot.  I have downloaded the debian FS from the Glomation website and uncompressed/untared it to a USB drive.

Question 1: what U-boot commands do I need to run to boot from the USB drive?

Question 2: How do I then mount the FS on the internal flash so I can edit my way out of this?

Dave

 

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

The boot command is the same, only the boot arguments need to be changed.   The printenv command can print out all current U-boot environment variable settings.   The set command can be used to set the environment variable for example,

set bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=5 mtdparts=atmel_nand:1M(bootloader),3M(kernel),-(rootfs)

to set the boot argument to use USB as root file system.  Please note the MTD device name of the NAND FLASH is at91_nand for kernel version 2.6.25.x and atmel_nand for kernel version 2.6.27.x and up.

You can save the setting use saveenv command so the board can boot using USB root file system as default.   Or just run the following command to use the USB as root file system just for this time only,

nand read.jffs2 0x21000000 0x100000 0x200000; bootm 0x21000000


The NAND FLASH is partitioned by the mtdparts argument passed to the kernel if it is present.  The partition scheme used by above example which is used by the factory default sets the 3rd partition as the root partition when using NAND FLASH partition as root file system.   The device will appear as /dev/mtdblock2 in the Linux file system.  You can mount the MTD partition with the following command,

mount -t jffs2 /dev/mtdblock2 /mnt

[davest]

davest

davest

Show davest's last posts.

Show general stats for davest.

• 
• Super Hero
• Posts: 22

Hi,

That caused a lot of things to happen.  The last line on the list is a kernel panic.

I have attached the entire log.

Dave

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

The kernel booted properly and everything else looks OK.  Please make sure you have a valid root file system on your USB drive.

[davest]

davest

davest

Show davest's last posts.

Show general stats for davest.

• 
• Super Hero
• Posts: 22

Hi,

I don't know how to prove that.  The USB was filled from your website file.


Let's just start at step 1.

What is the name of the file that the kernel is looking for? I can then look into that file to see where it goes from there.

Dave

P.S.  The flash drive is in FAT format. Does that require different commands to U-boot?

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

The U-boot doesn't care what format the root file system is but the Linux kernel does.  Please try to format the drive as ext2 or ext3 and untar the file system again.  You can also use the RAM disk approach if you just want to un-brick the MTD partition.  The steps of running off RAM disk is described here http://glomation.net/smf/index.php/topic,8.0.html

[davest]

davest

davest

Show davest's last posts.

Show general stats for davest.

• 
• Super Hero
• Posts: 22

Thanks,

I followed the instructions in the link up to where the ramdisk booted.  I then mounted the onboard flash instead.

I could then edit the file I needed to re-gain control of the booting.

Dave

[johns]

johns

johns

Show johns's last posts.

Show general stats for johns.

• 
• Super Hero
• Posts: 5

[NOTE:]

I recently purchased a 9260 and am currently trying to boot from a USB without success.  The kernel fails to mount the file system.  After reading through the discussions here, using my linux desktop running ubuntu, I ….
Previously it was a dos format (FAT).  So
1.ran the x terminal
2.identified the device by using ..$ mount at the command line. Device was /dev/sdb1
3.used ubuntu gui to unmount the file
4.formatted the device ..$ sudo mkfs.ext3 /dev/sdb1. (that went just fine)
5.labeled the drive ..$ sudo e2label /dev/sdb1 lnx_usb
6.removed the device then re-inserted to easily remount the USB stick.
7.Verified all was good .. label was correct but I didn't read write permissions
8.set permissions rwx for all groups and users ..$ sudo chmod a-rwx lnx_usb
9.verified permissions using my GUI
10.moved the debian tar file, from the website, to the USB.
11.Extracted all then removed the debian file.
12.Set the boot args accordingly on the 9260.  Here is a excerpt of the boot.
bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=5 mtdparts=atmel_nand:1M(bootloader),3M(kernel),-(rootfs)
13.Saved the environment Uboot> saveenv
NOTE:
The kernel is 2.6.27.4
I checked the root directory an nothing is in it.  I am a newbie to linux so that may be normal or the extraction didn't work for me.
I have attached a printenv and boot copy for review.

I would appreciate any input that would he

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

The boot log shows that the USB device was detected but there was no indication that it was detected as a storage device.  It could 1) the delay wasn't long enough for the USB storage device driver to fully initialize, 2) the USB device was not compatible with the driver.

Give a longer delay to see if it helps.

[johns]

johns

johns

Show johns's last posts.

Show general stats for johns.

• 
• Super Hero
• Posts: 5

[great]

I followed your suggestion and it worked great.  teh dealy is now set to 10 instead of 5.
Seems I have slow USB.