Documentation:NGW/NGW100 Known issues
From AVRFreaks Wiki
Contents |
[edit] USB VBUS not routed
On the Network Gateway the VBUS from the USB host is connected to a test point next to the USB connector. For a USB device to comply the USB specifications, the device must sense the VBUS and not communicate, enable pull-up or pull-down on the USB data lines before VBUS is applied from the host.
Workaround: If designing a USB device with the Network Gateway as a reference, connect voltage limited VBUS to a GPIO pin. VBUS is 5V, GPIO tolerates 3.3V ! The Linux OS must also be patched to use the GPIO signal. Here is an example of a possible VBUS fix.
[edit] NGW100 Arrived with no working network interface
Boot Message
* mounting filesystems: /usr * setup eth0 ... [ FAILED ] * Network ... [ FAILED ] * get board type for GPIO ... 'NGW'
If you Type ifconfig at the shell you get
~ # ifconfig eth0 ifconfig: SIOCSIFADDR: No such device
[edit] Side Note
Out of the box NGW100, u-boot may not support setenv, saveenv or be able to flash itself.
See UbootPatches to get U-Boot 1.2.0.atmel.1 or newer but to do this
you may also need a JTAGICE mkII & a flasher program such as
AVR Studio or Avrdude or Documentation:AVR32_Embedded_Development/Avr32program
However with a fully functional u-boot you will also be able to:
o test sdram o download to sdram a new, test kernel via tftp and boot it o flash a tested kernel o flash root file system (erase, cp.b jffs2)
Hint: Atmel please update u-boot in new NGW100 skipments.
[edit] Solution
From the serial console reboot NGW100
Press Space when asked to enter UBoot (You only have 2 seconds)
setenv ethaddr (type MAC address derived from link below) setenv eth1addr (type MAC address derived from link below) printenv saveenv boot
Warning on the MAC address
Not all MAC address's will work
Then on reboot you should see this:
* setup eth0 ... [ OK ] (10.11.12.1) * setup eth1 ... [ OK ] * network ... [ OK ]
For more info avrfreaks Fourm
