BiPOM Forum
General => GadgetPC => Topic started by: franklin97355 on May 19, 2010, 10:30:06 am
-
Your instructions for installing Debian uses a virtual Ubuntu box and virtual Debian inage. are there instructions on how to do this from a native Debian computer? Thanks.
-
Please read the latest page of
http://www.bipom.com/documents/boards/gadgetpc/GadgetPC%20Debian%20Installation%20Guide.pdf
"6. Alternative releases for advanced Linux users".
All you need is to download the prepared images and copy a disk hard drive
Also, you can install Debian on QEMU and then copy to a real disk hard drive ( USB Flash or microSD).
This link provides a detailed instruction
http://dev.emcelettronica.com/installing-debian-arm-qemu
-
That will teach me to "Read The Entire Manual " :-[
Thanks for your patience and support.
-
OK, after I get the files on the flash drive and plug it in it flashes for a few seconds, the USB serial port makes a connection but I can not communicate on either the usb serial or the TTL serial ports. What do I have to do next?
-
Please show a log your board sends to a console
http://www.bipom.com/cgi-bin/yabb2/YaBB.pl?num=1258826725
Note, the board sends bootstrap/u-boot debug messages
even without USB flash
-
I am getting nothing on the console port but with the original GadgetPC flash I get a ligin prompt on the USB connection. What baud rate should I be using? I\'ve tried 9600, 57600 and 115200.
-
115200
-
Here is the tail of the info I got...
some lines were reduced to lowercase because the forum software says I\'m using all caps
registered new interface driver usb-storage
usb mass storage support registered.
udc: at91_udc version 3 may 2006
g_serial gadget: gadget serial v2.4
g_serial gadget: g_serial ready
mice: ps/2 mouse device common for all mice
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
irq 1/rtc0: irqf_disabled is not guaranteed on shared irqs
rtc-at91sam9 at91_rtt.0: rtc0: set time!
i2c-gpio i2c-gpio: using pins 55 (sda) and 56 (scl)
linux video capture interface: v2.00
at91sam9 watchdog: sorry, watchdog is disabled
at91_wdt: probe of at91_wdt failed with error -5
sdhci: secure digital host controller interface driver
sdhci: copyright(c) pierre ossman
advanced linux sound architecture driver version 1.0.20.
usbcore: registered new interface driver snd-usb-audio
usbcore: registered new interface driver snd-usb-caiaq
alsa device list:
no soundcards found.
tcp cubic registered
net: registered protocol family 17
vfp support v0.3: not present
rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock
ramdisk: couldn\'t find valid ram disk image starting at 0.
list of all partitions:
no filesystem could mount root, tried: ext3 ext2 cramfs vfat romfs
kernel panic - not syncing: vfs: unable to mount root fs on unknown-block(1,0)
[<c002a4ec>] (unwind_backtrace+0x0/0xdc) from [<c02509f4>] (panic+0x40/0x110)
[<c02509f4>] (panic+0x40/0x110) from [<c0008fb8>] (mount_block_root+0x25c/0x2ac)
[<c0008fb8>] (mount_block_root+0x25c/0x2ac) from [<c00091d0>] (prepare_namespace+0x164/0x1bc)
[<c00091d0>] (prepare_namespace+0x164/0x1bc) from [<c000859c>] (kernel_init+0xb8/0xe4)
[<c000859c>] (kernel_init+0xb8/0xe4) from [<c003ce80>] (do_exit+0x0/0x5ac)
[<c003ce80>] (do_exit+0x0/0x5ac) from [<00000001>] (0x1)
g_serial gadget: full speed config #2: cdc acm config
-
Did you configure GadgetPC loaders to run Debian ?
Please read
http://www.bipom.com/documents/boards/gadgetpc/Commands%20to%20set%20up%20UBOOT%20environment%20to%20boot%20GadgetPC.pdf
1) To run Debian on GadgetPC, type the following at the U-BOOT prompt:
setenv bootcmd \'usb start; fatload usb 0:1 0x21000000 uImage; bootm 0x21000000\'
setenv bootargs \'mem=32M console=ttyS1,115200 root=/dev/sda2 rw rootwait\'
saveenv
( You do not need any mmfs.gz or gpcfs.gz at all )
2) To run ARM9 Linux on GadgetPC, type the following at the U-BOOT prompt:
setenv bootcmd \'usb start; fatload usb 0:1 0x21000000 uimage; fatload usb 0:1 0x20410000 gpcfs.gz; bootm 0x21000000\'
setenv bootargs \'mem=32M console=ttyS1,115200 root=/dev/ram0 rw initrd=0x20410000,0x800000 ramdisk_size=8200\'
saveenv
-
Thank you, I now have a login prompt but the user \'root\' with the password \'user\' does not work. Also after the line loading uImage I get garbage until the login prompt any ideas? Also how do I change the settings for the IP being used as it is not in my network range.
Thanks again.
-
1) On my Arm-Debian the default system has two users
login "user", with password "user" , and
login "root", with password "root"
I installed following the instructions from section 6 of Debian Installation guide.
2)Garbage through the serial port can be because of speed mismatch between GadgetPC\'s serial port and your terminal emulator\'s serial port settings. If you followed the "long" Debian installation (not section 6), there\'s a part where some lines must be changed in /etc/inittab to set the correct terminal and it\'s parameters for, make sure you edit that file correctly. If that isn\'t the problem i really wouldn\'t know.
3) The configuration parameters for the wireless usb card are in /etc/network/interfaces. I think configuration of this is fairly standard for Debian systems and some googling for topics such as "debian interfaces configuration" or "debian network configuration" or "debian WUA1340 configuration" should help you. Sorry to not be of much help in this, I was about to go do those searches myself!
(also there\'s a post somewhere in this forum about debian+gadgetPc+wireless+WPA, which maybe can also be of help)
-
Thank you Juan, I\'m working through some of these links and trying the ideas but have not yet hit on the "Magic Combo" I once got the router to see the GadgetPC\'s mac address but no communications yet. I\'ll keep working on this and let everyone know what I find.
-
Still not working. I downloaded the latest copies of the files and checked the U-Boot which is now including the lines mentioned. I went into /etc/network/interfaces and changed the password and ssid and changed wlan0 to wlan1 since the system does not know wlan0. If I run iwconfig after making the changes and restarting the network it does not know the essid and I have to add that manually. The wireless card starts and my router sees the mac address but I cannot communicate and if I ping I get destination unreachable. I have set it to use a static IP since if I try dhcp it will time out after a session of dhcpdiscovers. I\'m open to suggestions.
-
show logs of ifconfig, iwconfig
-
debian-armel:~# iwconfig
lo no wireless extensions.
wmaster0 no wireless extensions.
wlan1 ieee 802.11bg essid:""
mode:managed frequency:2.412 ghz access point: not-associated
tx-power=18 dbm
retry min limit:7 rts thr:off fragment thr:off
encryption key:off
power management:off
link quality:0 signal level:0 noise level:0
rx invalid nwid:0 rx invalid crypt:0 rx invalid frag:0
tx excessive retries:0 invalid misc:0 missed beacon:0
debian-armel:~# ifconfig
lo link encap:local loopback
inet addr:127.0.0.1 mask:255.0.0.0
up loopback running mtu:16436 metric:1
rx packets:52 errors:0 dropped:0 overruns:0 frame:0
tx packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
rx bytes:4632 (4.5 kib) tx bytes:4632 (4.5 kib)
wlan1 link encap:ethernet hwaddr 00:24:01:9e:99:9c
inet addr:192.168.1.212 bcast:192.168.1.255 mask:255.255.255.0
up broadcast multicast mtu:1500 metric:1
rx packets:0 errors:0 dropped:0 overruns:0 frame:0
tx packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
rx bytes:0 (0.0 b) tx bytes:0 (0.0 b)
wmaster0 link encap:unspec hwaddr 00-24-01-9e-99-9c-00-00-00-00-00-00-00-00-00-00
up running mtu:0 metric:1
rx packets:0 errors:0 dropped:0 overruns:0 frame:0
tx packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
rx bytes:0 (0.0 b) tx bytes:0 (0.0 b)
-
Also on login it show the software has a date of 6Feb2010 but I thought I had a latter version or at least a download with a later date.
-
It seemed the hardware worked. But the wireless interface is not configured. ESSID is empty (ieee 802.11bg essid:"")
Here are the typical commands you need to add to /etc/network/interfaces. Your network has to support WPA
encryption
# The wireless network interface
auto wlan1
iface wlan1 inet static
address 192.168.1.212
netmask 255.255.255.0
gateway 192.168.1.1
wpa-psk "your password"
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA2
wpa-ssid "your ESSID"
As the 1st step try to execute the commands by hands.
If everything works you can add to /etc/network/interfaces
-
Yes it\'s set that way. I even redownloaded, extracted and installed the latest versions of the software from the ftp site and now it loads like it was before but does not see a wireless device at all ifconfig and iwconfig do not see any devices and the lan card does not flash at all.
-
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
#auto eth1
#iface eth1 inet static
#address 192.168.1.210
#netmask 255.255.255.0
#gateway 192.168.1.1
# The 2nd network interface
#auto eth1:0
#iface eth1:0 inet static
#address 192.168.1.211
#netmask 255.255.255.0
#gateway 192.168.1.1
#allow-hotplug eth0
#iface eth0 inet dhcp
#allow-hotplug eth1
#iface eth1 inet dhcp
#allow-hotplug eth2
#iface eth2 inet dhcp
# The wireless network WPA2-PSK interface
#allow-hotplug wlan1
#iface wlan1 inet dhcp
#pre-up iwconfig wlan1 rate 54M
auto wlan1
iface wlan1 inet static
address 192.168.1.212
netmask 255.255.255.0
gateway 192.168.1.1
wpa-psk xxxxxxxx
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA2
wpa-ssid franklin
-
Well, after redownloading, extracting and loading files to a freshly formatted USB drive, changing the ESSID using iwconfig since changing it in interfaces did not work, adjusting the router setup and reconfiguring my wifes computer after she yelled at me that she no longer could get to the network (darn router security) I have a GadgetPC that can see the network! I\'ll let you know how I\'m doing with the rest of my project as it progresses. Thanks for all the help you guys have given me in my quest for communications.