[SOLVED] Troubleshooting GoPiGo 2 failed. log.txt attached


#1

I got my GoPiGo all assembled and I got all the networking figured out.
Great instructions btw. Thx.
However, when I turn it upside down and run via VNC desktop “Test and Troubleshoot > Troubleshoot GoPiGo”, nothing happened.
There was no movement at all.
I just got a message asking me to post the log file to the forums.
Log file is below.
There are several weird errors in here that I do not understand.
Any suggestions would be appreciated.

 ?   >cat log.txt 

Check space left
================
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       3.5G  2.8G  578M  83% /
devtmpfs        182M     0  182M   0% /dev
tmpfs            38M  444K   37M   2% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs            75M     0   75M   0% /run/shm
/dev/mmcblk0p1   56M   20M   37M  36% /boot

Check for dependencies
======================
python 2.7.3-4+deb7u1 install ok installed
python-pip 1.1-3 install ok installed
git 1:1.7.10.4-1+wheezy1+rpi2 install ok installed
libi2c-dev 3.1.1+svn-1 install ok installed
python-serial 2.5-2.1 install ok installed
python-rpi.gpio 0.5.11-1 install ok installed
i2c-tools 3.1.1+svn-1 install ok installed
python-smbus 3.1.1+svn-1 install ok installed
arduino 1:1.0.1+dfsg-7 install ok installed
minicom 2.6.1-1 install ok installed
scratch 1.4.20131203-2 install ok installed

wiringPi Found
wiringPi Found
I2C already removed from blacklist
SPI already removed from blacklist

Check for addition in /modules
==============================
I2C-dev already there
i2c-bcm2708 already there
spi-dev already there

Hardware revision
=================
gpio version: 2.29
Copyright (c) 2012-2015 Gordon Henderson
This is free software with ABSOLUTELY NO WARRANTY.
For details type: gpio -warranty

Raspberry Pi Details:
  Type: Model B+, Revision: 1.2, Memory: 512MB, Maker: Sony 
  Device tree is enabled.
  This Raspberry Pi supports user-level GPIO access.
    -> See the man-page for more details

Check the /dev folder
=====================
i2c-1
spidev0.0
spidev0.1
ttyAMA0

Checking for Atmega chip
========================

avrdude: Version 5.10, compiled on Jun 18 2012 at 12:38:29
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "/etc/avrdude.conf"
         User configuration file is "/root/.avrduderc"
         User configuration file does not exist or is not a regular file, skipping

         Using Port                    : unknown
         Using Programmer              : gpio
         AVR Part                      : ATMEGA328P
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PC2
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           eeprom        65     5     4    0 no       1024    4      0  3600  3600 0xff 0xff
           flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
           lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

         Programmer Type : GPIO
         Description     : Use sysfs interface to bitbang GPIO lines

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e950f

avrdude done.  Thank you.

Checking I2C bus for devices
============================

Checking I2C bus 0
==================
Error: Could not open file <code>/dev/i2c-0' or</code>/dev/i2c/0': No such file or directory

Checking I2C bus 1
==================
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

Checking for firmware version and CPU Speed and Voltage
=======================================================
v -1
CPU speed: -1
-1 V

CHECKING ENCODER READINGS
-1 -1
Both motors moving Forward with LED On
after 5 sec -1 -1
Both motors stopped with LED Off
-1 after stop cmd -1 -1
-1 after 2 more sec -1 -1
Both motors moving back with LED On
after 5 sec -1 -1
Both motors stopped with LED Off
-1 after stop cmd -1 -1
-1 after 2 more sec  -1 -1

CHECKING ENCODER TARGETING

Initial encoder read vals: -1 -1
Traceback (most recent call last):
  File "/home/pi/Desktop/GoPiGo/Software/Python/tests/enc_tgt_test.py", line 69, in <module>
    enc_stat=read_enc_status()
  File "build/bdist.linux-armv7l/egg/gopigo.py", line 521, in read_enc_status
  File "build/bdist.linux-armv7l/egg/gopigo.py", line 513, in read_status
IOError: [Errno 5] Input/output error

#2

Update: I tried following the steps on the Troubleshooting page.

It said to upgrade the software.

When I selected the “DI Software update” icon it gave 3 options for things to upgrade.

  1. Raspbian
  2. DI Software
  3. Firmware

I wasn’t sure which to upgrade, so I decided to upgrade each of them.

I started with Raspbian.

PROBLEM: After upgrading Raspbian, I can no longer launch either “Test and Troubleshoot” or “DI Software Update”.

This software does not seem to be very robust.

What’s the fix?


#3

I’m looking at your first post, and that indicated that you needed to upgrade the GoPiGo firmware.

You should see the following:
Checking I2C bus 1

 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

00: – -- – -- – 08 – -- – -- – -- –
10: – -- – -- – -- – -- – -- – -- – -- – --
20: – -- – -- – -- – -- – -- – -- – -- – --
30: – -- – -- – -- – -- – -- – -- – -- – --
40: – -- – -- – -- – -- – -- – -- – -- – --
50: – -- – -- – -- – -- – -- – -- – -- – --
60: – -- – -- – -- – -- – -- – -- – -- – --
70: – -- – -- – -- – --

So doing the DI_Update was a good step. However I’m unclear about your present status. Did you let the Raspbian update go till the end, or did you interrupt it before it was done? It can be a lengthy operation. Did you do a reboot as requested?
What happens when you click on “Test and Troubleshoot”, or “DI Software Update”?


#4

That’s great info. Thanks.

Pretty sure the Raspbian upgrade completed fully.
Here’s what the screen looked like:
http://ibin.co/2YtwgjcQCGjg
Yes, I rebooted.

Unfortunately, after the Raspbian update I am no longer able to launch the “Di Software Update” program, so I can’t get to the place where I start the firmware upgrade.

When I click on “DI Software Update” now, it does not give me the 3 options that it gave me before.
It just jumps directly into the Raspbian install again.

Here’s how it starts:
http://ibin.co/2Yu1NPT7aT4y

Here’s how it ends: (Notice the error message)
http://ibin.co/2Yu28YSDDqr9

Here’s the log file.

 ?   >cat Dexter_Software_Update_log_2016_03_02__21_01_31.txt 
Script started on Wed 02 Mar 2016 09:01:31 PM UTC
Traceback (most recent call last):
  File "/home/pi/di_update/Raspbian_For_Robots/raspbian_for_robots_update.py", line 1, in <module>
    import wx
ImportError: No module named wx
Script done on Wed 02 Mar 2016 09:01:32 PM UTC

Looks like a missing wx module is causing some problems.

When I click on the “Test and Troubleshoot” shortcut
A terminal displays very briefly but then dies before doing anything.

Here’s what I see before it dies.
http://ibin.co/2YuBpZg52Lhg


#5

This specific issue seems like it was caused by cutting off the update early. We’ve seen it before.

The best solution is to run these commands:

sudo apt-get install python-wxgtk2.8 python-wxtools wx2.8-i18n --force-yes			
sudo apt-get install python-psutil --force-yes

If you run those commands, will the software update run again?

If not, you may need to run to the command

sudo sh ~/update_backup.sh

This is a nuclear option we built in; it should install enough to get you back on your feet, and then run the software update.


#6

Oh, and after you get the software update software running again, you should try to run the firmware update (selecting the GoPiGo in the dropdown on the software update window).


#7

Ahhh…
Success!!!
Thanks.

After updating the firmware the tests seem to run correctly.
I received only one error…

Checking I2C bus 0

Error: Could not open file /dev/i2c-0’ or/dev/i2c/0’: No such file or directory

… But it did not seem to stop the wheels from spinning.
Gracias.

 ?   >cat log.txt 

Check space left
================
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       3.5G  2.8G  569M  84% /
devtmpfs        182M     0  182M   0% /dev
tmpfs            38M  436K   37M   2% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs            75M     0   75M   0% /run/shm
/dev/mmcblk0p1   56M   20M   37M  36% /boot

Check for dependencies
======================
python 2.7.3-4+deb7u1 install ok installed
python-pip 1.1-3 install ok installed
git 1:1.7.10.4-1+wheezy1+rpi2 install ok installed
libi2c-dev 3.1.1+svn-1 install ok installed
python-serial 2.5-2.1 install ok installed
python-rpi.gpio 0.5.11-1 install ok installed
i2c-tools 3.1.1+svn-1 install ok installed
python-smbus 3.1.1+svn-1 install ok installed
arduino 1:1.0.1+dfsg-7 install ok installed
minicom 2.6.1-1 install ok installed
scratch 1.4.20131203-2 install ok installed

wiringPi Found
wiringPi Found
I2C already removed from blacklist
SPI already removed from blacklist

Check for addition in /modules
==============================
I2C-dev already there
i2c-bcm2708 already there
spi-dev already there

Hardware revision
=================
gpio version: 2.29
Copyright (c) 2012-2015 Gordon Henderson
This is free software with ABSOLUTELY NO WARRANTY.
For details type: gpio -warranty

Raspberry Pi Details:
  Type: Model B+, Revision: 1.2, Memory: 512MB, Maker: Sony 
  Device tree is enabled.
  This Raspberry Pi supports user-level GPIO access.
    -> See the man-page for more details

Check the /dev folder
=====================
i2c-1
spidev0.0
spidev0.1
ttyAMA0

Checking for Atmega chip
========================

avrdude: Version 5.10, compiled on Jun 18 2012 at 12:38:29
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "/etc/avrdude.conf"
         User configuration file is "/root/.avrduderc"
         User configuration file does not exist or is not a regular file, skipping

         Using Port                    : unknown
         Using Programmer              : gpio
         AVR Part                      : ATMEGA328P
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PC2
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           eeprom        65     5     4    0 no       1024    4      0  3600  3600 0xff 0xff
           flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
           lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

         Programmer Type : GPIO
         Description     : Use sysfs interface to bitbang GPIO lines

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e950f

avrdude done.  Thank you.

Checking I2C bus for devices
============================

Checking I2C bus 0
==================
Error: Could not open file <code>/dev/i2c-0' or</code>/dev/i2c/0': No such file or directory

Checking I2C bus 1
==================
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- 08 -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

Checking for firmware version and CPU Speed and Voltage
=======================================================
v 1.6
CPU speed: 2
7.75 V

CHECKING ENCODER READINGS
0 0
Both motors moving Forward with LED On
after 5 sec 102 105
Both motors stopped with LED Off
None after stop cmd 106 108
None after 2 more sec 107 109
Both motors moving back with LED On
after 5 sec 207 215
Both motors stopped with LED Off
None after stop cmd 211 218
None after 2 more sec  212 218

CHECKING ENCODER TARGETING

Initial encoder read vals: 0 1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  0
Final encoder read vals: 73 75

Initial encoder read vals: 0 1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  0
Final encoder read vals: 73 75

Initial encoder read vals: 0 1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  0
Final encoder read vals: 73 76

Initial encoder read vals: 0 1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  0
Final encoder read vals: 73 75

Initial encoder read vals: 0 1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  1
Enc tgt Status:  0
Final encoder read vals: 73 76

#8

Hey alexryan,
Great to hear that it is working now. That error is completely harmless. It is there to check if the i2c-0 but works which used to work in the older versions of the Raspberry Pi. Just make sure that you use a batter with voltage higher than 9V.

-Karan