[Help] Failed to update A5 USB PID/VID for BeagleBone revA3 Box!

Dear All,

I follow the link and steps as the following for BeagleBone Rev A3. My BeagleBone can not boot for NFS root file system. Please help me to solve this problem!

http://circuitco.com/support/index.php?title=BeagleBone

Trouble Installing USB Drivers [A3 and A4]

There have been numerous cases where people have had issues installing their USB drivers on the Rev A3 and A4 boards. This can be helped by making the PID/VID change that is being done for the revision A5 board. This will enable the standard signed drivers that come from FTDI to be automatically loaded when the board is plugged in. Following are the steps for programming the new VID/PID.

NOTE: Make sure you do this exactly as described. No shortcuts! It is possible to use the FTDI GUI SW to do this as well, however, there is a chance you can lock the EEPROM on the FTDI part in which case the board will no longer function and replacing the EEPROM is the only solution.

NOTE: This procedure is for Windows only! The FTDI utilities do not support any other OS.

  1. Download the file BBA5_PIDVID.
  2. Unzip the file to a seperate directory.
  3. Follow this link to the FTDI D2XX drivers page. Download the setup executable file of the 2.08.14 WHQL Certified version under Windows.
  4. Run the downloaded executable file to install the drivers.
  5. Remove the SD card from the BeagleBone.
  6. Insert the BeagleBone into a PC usb port.
  7. Go to the directory where you unzipped the file and select “EEPROMA5.bat”. This will open a command window and run the batch file.
  8. Unplug the board from the PC when it is done.

Boot Failed Log messages :
U-Boot SPL 2011.09 (Jan 30 2012 - 22:14:05)
Texas Instruments Revision detection unimplemented
Could not read the EEPROM; something fundamentally wrong on the I2C bus.
read_eeprom() failure
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img

U-Boot 2011.09 (Jan 30 2012 - 22:14:05)

I2C: ready
DRAM: 256 MiB
WARNING: Caches not enabled
Could not read the EEPROM; something fundamentally wrong on the I2C bus.
NAND: HW ECC Hamming Code selected
No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

Net: cpsw
Hit any key to stop autoboot: 0
SD/MMC found on device 0
reading uEnv.txt

300 bytes read
Loaded environment from uEnv.txt
Importing environment from mmc …
Running uenvcmd …
Booting from network…
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.1.119
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.1.156; our IP address is 192.168.1.119
Filename ‘uImage-am335x-evm.bin’.
Load address: 0x82000000
Loading: #################################T ################################

The EEPROM it cannot read is NOT the EEPROM that containds the PID/VID. They are seperate EEPROMS devices… One is on the FTDI device, PID/VID. and the other one is on the AM335x processor. THe issue you are having is not related to the PID/VID EEPROM. Something else has gone wrong here. If you wrote to the EEPROM on board. then this could cause this issue.

Gerald

Thanks Gerald very much!

Something else has gone wrong here. If you wrote to the EEPROM on board. then this could cause this issue.
I don’t know what is “wrote to the EEPROM on board”. I did not do any to write EEPROM steps.
I just follow the steps posts on the web site. When I saw red color message in the DOS Box.
I went back to turn on my origin boot procedure to check. Then I got those message.

Do you have any solution to solve my failed boot with NFS mount issue?
Or to send back RMA?

Thanks again!

Sunny Liu

2012/4/7 Gerald Coley <gerald@beagleboard.org>

If the pullups are not enabled in UBoot, you can get the I2C timeout error where it is looking for the other devices on the expansion cards that may not be there. If it is trying to read the EEPROM on the board and gets this error, then something has happened to the EEPROM on the board or something may be holding the I2C bus from something that may be plugged into the expansion bus.

NFS mount is usually a SW issue. Have you tried booting with the original card that shipped with the board?

Gerald

2012/4/9 Gerald Coley <gerald@beagleboard.org>

If the pullups are not enabled in UBoot, you can get the I2C timeout error where it is looking for the other devices on the expansion cards that may not be there. If it is trying to read the EEPROM on the board and gets this error, then something has happened to the EEPROM on the board or something may be holding the I2C bus from something that may be plugged into the expansion bus.

NFS mount is usually a SW issue. Have you tried booting with the original card that shipped with the board?

No, I did a mistake to remove origin image.
I tried root file system is not NFS. It is failed too!
Somethingwrong to happne in the I2C.1 Bus (omap_i2c omap_i2c.1: controller timed out)

Full log messages :

U-Boot SPL 2011.09 (Jan 30 2012 - 22:14:05)
Texas Instruments Revision detection unimplemented
Could not read the EEPROM; something fundamentally wrong on the I2C bus.
read_eeprom() failure
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img

U-Boot 2011.09 (Jan 30 2012 - 22:14:05)

I2C: ready
DRAM: 256 MiB
WARNING: Caches not enabled
Could not read the EEPROM; something fundamentally wrong on the I2C bus.
NAND: HW ECC Hamming Code selected
No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

Net: cpsw
Hit any key to stop autoboot: 3  2  1  0
SD/MMC found on device 0
reading uEnv.txt

64 bytes read
Loaded environment from uEnv.txt
Importing environment from mmc …
reading uImage

3078608 bytes read

Booting kernel from Legacy Image at 80007fc0 …

Image Name: Linux-3.1.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3078544 Bytes = 2.9 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK
XIP Kernel Image … OK
OK

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[ 0.071357] omap_l3_smx omap_l3_smx.0: couldn’t find resource
[ 1.172987] omap_i2c omap_i2c.1: controller timed out
[ 1.192922] Could not set LED4 to fully on
[ 2.192857] omap_i2c omap_i2c.1: controller timed out
[ 3.212989] omap_i2c omap_i2c.1: controller timed out
[ 4.232853] omap_i2c omap_i2c.1: controller timed out
[ 5.303083] omap_i2c omap_i2c.1: controller timed out
[ 6.342874] omap_i2c omap_i2c.1: controller timed out
[ 7.383039] omap_i2c omap_i2c.1: controller timed out
[ 8.422813] omap_i2c omap_i2c.1: controller timed out
[ 8.465040] mtdoops: mtd device (mtddev=name/number) must be supplied
[ 9.472936] omap_i2c omap_i2c.1: controller timed out
[ 10.492961] omap_i2c omap_i2c.1: controller timed out
[ 11.512865] omap_i2c omap_i2c.1: controller timed out
[ 12.532875] omap_i2c omap_i2c.1: controller timed out
[ 13.553161] omap_i2c omap_i2c.1: controller timed out
[ 14.572882] omap_i2c omap_i2c.1: controller timed out
[ 15.593072] omap_i2c omap_i2c.1: controller timed out
[ 16.612856] omap_i2c omap_i2c.1: controller timed out
[ 16.644386] omap2_set_init_voltage: Fail set voltage-dpll_mpu_ck(f=500000000 v=1100000)on vddmpu
[ 16.653681] omap2_set_init_voltage: unable to set vdd_mpu

2012/4/9 Gerald Coley <gerald@beagleboard.org>

If the pullups are not enabled in UBoot, you can get the I2C timeout error where it is looking for the other devices on the expansion cards that may not be there. If it is trying to read the EEPROM on the board and gets this error, then something has happened to the EEPROM on the board or something may be holding the I2C bus from something that may be plugged into the expansion bus.

This BeagleBone doesn’t plugged any expansion bus.
The u-boot source code is from ti-sdk-am335x-evm-05.03.02.00-Linux-x86-Install. I only re-build the u-boot image only. I didn’t modify any source code.
To check the schematic, don’t see any pull high for the I2C1 bus.

Does it be solved to modify u-boot?

Sunny

If you tried the code that shipped with the board and it fails, http://circuitco.com/support/index.php?title=BeagleBone#Image_Files
then changing then code that already works is not going to fix your board. You need try the RMA process.

Gerald

To check u-boot source code. To Find the error is from I2C (i2c0) read U7 EEPROM device (CAT24C256W).
So, u-boot and kernel can not read in BeagleBone Identify messages ( 0xAA, 0x55, 0x33, 0xEE … In BONESRM (A3) 7.11 EEPROM page 46).
I remember there was a link to show how to write back those board identify data into EEPROM.(?)
Could you give me the link?

http://circuitco.com/support/index.php?title=BeagleBone#Image_Files
I will try the image later.

You need try the RMA process
When those trying are failed again! I will go RMA next Monday.

2012/4/10 Gerald Coley <gerald@beagleboard.org>

I do not remember the link. It is not something we promote doing. You can do a search on the message archives to see if you can find it.

Gerald

2012/4/11 Gerald Coley <gerald@beagleboard.org>

I do not remember the link. It is not something we promote doing. You can do a search on the message archives to see if you can find it.

Gerald

I did find it!

To check u-boot source code. To Find the error is from I2C (i2c0) read U7 EEPROM device (CAT24C256W).
So, u-boot and kernel can not read in BeagleBone Identify messages ( 0xAA, 0x55, 0x33, 0xEE … In BONESRM (A3) 7.11 EEPROM page 46).
I remember there was a link to show how to write back those board identify data into EEPROM.(?)
Could you give me the link?

http://circuitco.com/support/index.php?title=BeagleBone#Image_Files
I will try the image later.

Only first time boot seems OK! Because I didn’t connect with minicom to see log messages.
Don’t know what is going on! After to start my vmWare and Ubuntu, to start minicom,
Didn’t see normal message to login.
To Press RESET Button! Something going wrong seriously!
Ethernet LED is Orange Color! Not Green Color,
To try many times, to see the following messages. Ethernet LED color always is Orange color.
I will send back for RMA!

U-Boot SPL 2011.09-00000-gf63b270-dirty (Nov 14 2011 - 10:37:14)
Texas Instruments Revision detection unimplemented
Could not read the EEPROM; something fundamentally wrong on the I2C bus.
read_eeprom() failure
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img

U-Boot 2011.09-00000-gf63b270-dirty (Nov 14 2011 - 10:37:14)

I2C: ready
DRAM: 256 MiB
Could not read the EEPROM; something fundamentally wrong on the I2C bus.
NAND: HW ECC Hamming Code selected
No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

Net: cpsw
Hit any key to stop autoboot: 0
SD/MMC found on device 0
reading uEnv.txt

33 bytes read
Loaded environment from uEnv.txt
Importing environment from mmc …
reading uImage

3031456 bytes read

Booting kernel from Legacy Image at 80007fc0 …

Image Name: Angstrom/3.1/beaglebone
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3031392 Bytes = 2.9 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK
XIP Kernel Image … OK
OK

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[ 0.067576] omap_l3_smx omap_l3_smx.0: couldn’t find resource
[ 1.140467] omap_i2c omap_i2c.1: controller timed out
[ 2.180323] omap_i2c omap_i2c.1: controller timed out
[ 3.220466] omap_i2c omap_i2c.1: controller timed out
[ 4.260322] omap_i2c omap_i2c.1: controller timed out
[ 4.311773] omap2_set_init_voltage: unable to get clk dpll1_ck
[ 4.317927] omap2_set_init_voltage: unable to set vdd_mpu_iva
[ 4.324039] omap2_set_init_voltage: unable to get clk l3_ick
[ 4.330001] omap2_set_init_voltage: unable to set vdd_core

Request the RMA. Do not send until approved.

Gerald

2012/4/11 Gerald Coley <gerald@beagleboard.org>

Request the RMA. Do not send until approved.

Gerald

How to pass the approved?

Submit the request and you will get a response back with instructions. http://beagleboard.org/support/rma

Gerald

2012/4/12 Gerald Coley <gerald@beagleboard.org>

Submit the request and you will get a response back with instructions. http://beagleboard.org/support/rma

Gerald

Yes, I did. I got RMA approved!