Troubleshootings

Sometimes the filesystems goes in read-only mode.

Format rootfs partition in ext4 with journaling option disabled (read how to..,).

The standard AT91Bootstrap bootloader, written by default on the Dataflash memory on the Netus G20 module, has a software features inherited from the Atmel software development kit that erase the first sector of the Dataflash when the line A31 (Pin J6.21 on the FOX Board G20) is mantained to 0 by an external hardware.

When this happen the FOX Board G20 (or the Netus G20 module) doesn't boot anymore.

This problem doesn't affects who don't use the J6.21 pin (A31) because this pin is mantained to 1 by an internal pull-up resistor

To rewrite the Dataflash follow this procedure: Restore the Netus dataflash content. The AT91Bootstrap.bin binary file available on this article is already fixed.

When the RTC backup battery is removed the FOX Board G20 doesn't work or is unable to start. After some months of regular working the discharge of the backup battery will hang the board till you will replace the battery.

Before proceeding check if your board is already fixed. The board delivered after March 9th 2010 are already fixed and have two diodes soldered by hand near the Acme Systems logo on the FOX Board G20 bottom side.

Remove the Lithium battery

Remove the R40 resistor located on the FOX Board G20 bottom side near the Acme logo:

Solder two diodes 1N4148 as shown below. Be careful with the diodes polarity. Pass the second diode anode terminal to the top side through the hole on the PCB.

Pay attention on the solder point 2 to solder also together the PCB pad underneath.

On the top side remove the Netus G20 module and solder the diode terminal on the 3V3Aux pad of the Netus PS1 module as shown below. Be careful that the diode terminal doesn't touch any other contact on the circuit.

Plug again the Netus G20 and the backup battery on their placements. The FOX Board is ready to work also without the RTC battery now.

On the FOX Board G20 shipped before 22nd of December 2009, if the power supply fails just after the RomBOOT message printed at startup on the Debug Port the FOX Board G20 doesn't boot up anymore. The only way to let it work again is to remove the RTC battery.

This problem is due to the following line on u-boot firmware located on the dataflash:

at91_sys_write(AT91_RSTC_MR, AT91_RSTC_KEY |
			     (AT91_RSTC_ERSTL & (0x0D << 8)) |
			     AT91_RSTC_URSTEN);

The source file is board/atmel/at91sam9260ek/at91sam9260ek.c

The patch and uboot.bin binary files available on this page will fix this problem: How to compile u-Boot

To rewrite the Dataflash follow this procedure: Restore the Netus dataflash content

1. Check if is available a DCHP server on your LAN. If not set a static IP address. If yes proceed to the point.
2. Linux saves in the file /etc/udev/rules.d/70-persistent-net.rules the MAC address of the eth0 port. This address is saved on dataflash memory. If you already used the microSD card on another FOX Board G20 or if you are using a cloned microSD or if you are changed the dataflash factory default contents probably the MAC address saved on the microSD doesn't match with the MAC saved in microSD. In this case the LAN interface doesn't come up. To fix it delete the /etc/udev/rules.d/70-persistent-net.rules on the microSD and restart the board.

Set the systems time and write it on the RTC

$ date MMDDHHMMYYYY
$ hwclock -w

There are no available x64 drivers using the automatic driver search utility of Microsoft, i created this one to resolve this issue.

1. Connect the front USB to the Netus and to your PC
2. Turn on the Netus closing the jumper.
3. Remove the jumper.
4. Windows Vista/7 x64 will show the device as “unknow device” and won't find any driver.
5. Go to Start→Control Panel→Device Manager
6. Search for Port (COM & LPT) devices list
7. You'll find the “Unknow Device”
8. Right Click on the device→Properties
9. Select DRIVER Tab
10. Select Update Driver
11. Browse to the folder where the usb_netus.zip was unzipped and select it
12. At the end of the installation process accept when you'll receive the notification declaring that the driver isn't signed.

The reason is due to the fact that Windows captures the device before Virtual Box and block it to avoid other accesses.

The solution is:

1. Connect the USB/SD device to the PC (without any virtual image running)
2. Select the virtual image
3. Go to Settings→Ports tab
4. Click on the '+' button
5. Select the USB device
6. Confirm
7. UNPLUG the device
8. START your linux distro on virtual box
9. While booting PLUG the device.
10. Check if the USB device (right clicking on the plug icon on a on the bottom right of the interface) has a checkmark otherwise select on that list.
11. To check if the process is correct you shouldn't see the device available inside the Windows Explorer/File Manager, 'cause it is used by virtualbox and its access is denied to Windows.