Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Newby Install
20-09-2011, 11:48 AM,
#1
Newby Install
Hi guys

New here, so please be gentle! I've made my own tiny 4550 board from the schematics on-line and have Pinguino on my Open Suse 11.4 PC.

If I run Pinguino from the su account and enter (or load from file) the basic LED flash tutorial code, when I hit the compile button nothing appears in the output part of the GUI but in the command terminal that I used to start the program I get:

Traceback (most recent call last):
File "./pinguinobeta9-05.py", line 642, in OnVerify
retour=self.compile(filename)
File "./pinguinobeta9-05.py", line 916, in compile
stdout=fichier, stderr=STDOUT)
File "/usr/lib/python2.7/subprocess.py", line 672, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1201, in _execute_child
raise child_exception
OSError: [Errno 13] Permission denied

Can anyone help?

Thanks,

Mark.
Reply
20-09-2011, 05:19 PM,
#2
RE: Newby Install
(20-09-2011, 11:48 AM)g0mgx Wrote: Hi guys

New here, so please be gentle! I've made my own tiny 4550 board from the schematics on-line and have Pinguino on my Open Suse 11.4 PC.

If I run Pinguino from the su account and enter (or load from file) the basic LED flash tutorial code, when I hit the compile button nothing appears in the output part of the GUI but in the command terminal that I used to start the program I get:

Traceback (most recent call last):
File "./pinguinobeta9-05.py", line 642, in OnVerify
retour=self.compile(filename)
File "./pinguinobeta9-05.py", line 916, in compile
stdout=fichier, stderr=STDOUT)
File "/usr/lib/python2.7/subprocess.py", line 672, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1201, in _execute_child
raise child_exception
OSError: [Errno 13] Permission denied

Can anyone help?

Thanks,

Mark.

Some more information. dmesg gives me:

[ 3677.122785] usb 6-3: USB disconnect, address 2
[ 3688.096034] usb 6-3: new full speed USB device using ohci_hcd and address 3
[ 3688.275097] usb 6-3: New USB device found, idVendor=04d8, idProduct=feaa
[ 3688.275104] usb 6-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3688.275110] usb 6-3: Product: Pinguino Project
[ 3688.275115] usb 6-3: Manufacturer: Jean-Pierre MANDON
[ 3688.275119] usb 6-3: SerialNumber: 1

and ls usb:

Bus 006 Device 003: ID 04d8:feaa Microchip Technology, Inc.

I've been through the install instructions on the Wiki here: http://wiki.pinguino.cc/index.php/Main_Page

but still no change in the error message....

Thanks!
Reply
20-09-2011, 08:14 PM,
#3
RE: Newby Install
Hi,
Congratulation for your board !
The problem seems that you don't have the right permission on usb port.
What version of Pinguino do you have ? x.2 or 9.5 ?

Anyway, check if you are in the plugdev group : groups $USER
If not : sudo useradd -G plugdev $USER
or sudo usermod -a -G plugdev $USER

Check also this file : /etc/udev/rules.d/41-microchip.rules
You should have something like that :
<quote>
# Pinguino (PIC18F)
ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="feaa", MODE="0660",GROUP="plugdev"
</quote>
On some linux installations, you may need to use SYSFS instead of ATTRS
If you change the file, tell Linux to reload udev rules by entering the following in the terminal window : sudo udevadm trigger
You can find a 41-microchip.rules file in directory extra from x.2
Régis
It is easier to complain than it is to do, but it is better to do than it is to complain.
Reply
20-09-2011, 09:30 PM,
#4
RE: Newby Install
(20-09-2011, 08:14 PM)regis Wrote: Hi,
Congratulation for your board !
The problem seems that you don't have the right permission on usb port.
What version of Pinguino do you have ? x.2 or 9.5 ?

Anyway, check if you are in the plugdev group : groups $USER
If not : sudo useradd -G plugdev $USER
or sudo usermod -a -G plugdev $USER

Check also this file : /etc/udev/rules.d/41-microchip.rules
You should have something like that :
<quote>
# Pinguino (PIC18F)
ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="feaa", MODE="0660",GROUP="plugdev"
</quote>
On some linux installations, you may need to use SYSFS instead of ATTRS
If you change the file, tell Linux to reload udev rules by entering the following in the terminal window : sudo udevadm trigger
You can find a 41-microchip.rules file in directory extra from x.2
Régis

Hi!

Thanks for the pointers;

I've got Pingino version 9 - the file I run is pinguinobeta9-05.py

I don't have a plugdev group, might it be called something else on Suse? My user account is in groups microchip and user.

My 41-microchip.rules contains:

# Pinguino
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="feaa", MODE="0660",GROUP="microchip"

Any use?
Reply
20-09-2011, 11:04 PM,
#5
RE: Newby Install
Check permissions on source/stdout and do "sudo chmod 777 source/stdout" if necessary, then try as normal user (without su or sudo) as it should work.


(20-09-2011, 09:30 PM)g0mgx Wrote:
(20-09-2011, 08:14 PM)regis Wrote: Hi,
Congratulation for your board !
The problem seems that you don't have the right permission on usb port.
What version of Pinguino do you have ? x.2 or 9.5 ?

Anyway, check if you are in the plugdev group : groups $USER
If not : sudo useradd -G plugdev $USER
or sudo usermod -a -G plugdev $USER

Check also this file : /etc/udev/rules.d/41-microchip.rules
You should have something like that :
<quote>
# Pinguino (PIC18F)
ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="feaa", MODE="0660",GROUP="plugdev"
</quote>
On some linux installations, you may need to use SYSFS instead of ATTRS
If you change the file, tell Linux to reload udev rules by entering the following in the terminal window : sudo udevadm trigger
You can find a 41-microchip.rules file in directory extra from x.2
Régis

Hi!

Thanks for the pointers;

I've got Pingino version 9 - the file I run is pinguinobeta9-05.py

I don't have a plugdev group, might it be called something else on Suse? My user account is in groups microchip and user.

My 41-microchip.rules contains:

# Pinguino
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="feaa", MODE="0660",GROUP="microchip"

Any use?

It is easier to complain than it is to do, but it is better to do than it is to complain.
Reply
21-09-2011, 08:11 AM,
#6
RE: Newby Install
Hmmm; I don't have a source/stdout... the source directory contains:

drwx------ 2 mark users 4096 Sep 20 16:12 .
drwx------ 13 mark users 4096 Sep 20 16:15 ..
-rw------- 1 mark users 1940 Sep 17 18:58 common_types.h
-rw------- 1 mark users 82271 Sep 17 18:58 main.asm
-rw------- 1 mark users 3188 Sep 17 18:58 main.c
-rw------- 1 mark users 39424 Sep 17 18:58 main.cod
-rw------- 1 mark users 225530 Sep 17 18:58 main.lst
-rw------- 1 mark users 58329 Sep 17 18:58 main.map
-rw------- 1 mark users 93106 Sep 17 18:58 main.o
-rw------- 1 root root 136 Sep 20 16:12 user.c


(20-09-2011, 11:04 PM)regis Wrote: Check permissions on source/stdout and do "sudo chmod 777 source/stdout" if necessary, then try as normal user (without su or sudo) as it should work.


(20-09-2011, 09:30 PM)g0mgx Wrote:
(20-09-2011, 08:14 PM)regis Wrote: Hi,
Congratulation for your board !
The problem seems that you don't have the right permission on usb port.
What version of Pinguino do you have ? x.2 or 9.5 ?

Anyway, check if you are in the plugdev group : groups $USER
If not : sudo useradd -G plugdev $USER
or sudo usermod -a -G plugdev $USER

Check also this file : /etc/udev/rules.d/41-microchip.rules
You should have something like that :
<quote>
# Pinguino (PIC18F)
ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="feaa", MODE="0660",GROUP="plugdev"
</quote>
On some linux installations, you may need to use SYSFS instead of ATTRS
If you change the file, tell Linux to reload udev rules by entering the following in the terminal window : sudo udevadm trigger
You can find a 41-microchip.rules file in directory extra from x.2
Régis

Hi!

Thanks for the pointers;

I've got Pingino version 9 - the file I run is pinguinobeta9-05.py

I don't have a plugdev group, might it be called something else on Suse? My user account is in groups microchip and user.

My 41-microchip.rules contains:

# Pinguino
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="feaa", MODE="0660",GROUP="microchip"

Any use?

Reply
21-09-2011, 09:46 AM,
#7
RE: Newby Install
I don't think this is a usb permissions thing. Looking at the error message again and then taking a peek at the pinguinobeta9-05.py file at the appropriate line it's the compile command that's failing.

The first thing I note is that the location of sdcc is hard coded as /tools/bin/sdcc whereas mine is located at /usr/local/bin/sdcc. So I changed that and now I see a different error. I thought the best thing would be to re-create the compile command as a stand alone shell script; so I have:

/usr/local/bin/sdcc -mpic16 --denable-peeps --obanksel=9 --opt-code-size --optimize-cmp --optimize-df -p18f4550 -I include -I /usr/local/share/sdcc/include/pic16 source/main.c

Initially this told me that I didn't have the 18f4550.h file and then the 18f2445.h file. I found these listed as part of the include files that should be part of sdcc and placed them in the sdcc/include/pic16 directory. Now the error is:

source/main.c:25:19: error: macro.h: No such file or directory
In file included from source/main.c:28:

I was confident (and still am) that I have installed sdcc correctly. sdcc -v gives me:

SDCC : mcs51/gbz80/z80/ds390/pic16/pic14/TININative/ds400/hc08 3.0.0 #6037 (Oct 31 2010) (Linux)

I get the impression that there is something quite simple missing here on my install? The sdcc-3.0.0-i386-unknown-linux2.5-tar-bz2 file doesn't have these .h files in the include/pic16 file structure.

Any ideas? please? Wrong sdcc?

(21-09-2011, 08:11 AM)g0mgx Wrote: Hmmm; I don't have a source/stdout... the source directory contains:

drwx------ 2 mark users 4096 Sep 20 16:12 .
drwx------ 13 mark users 4096 Sep 20 16:15 ..
-rw------- 1 mark users 1940 Sep 17 18:58 common_types.h
-rw------- 1 mark users 82271 Sep 17 18:58 main.asm
-rw------- 1 mark users 3188 Sep 17 18:58 main.c
-rw------- 1 mark users 39424 Sep 17 18:58 main.cod
-rw------- 1 mark users 225530 Sep 17 18:58 main.lst
-rw------- 1 mark users 58329 Sep 17 18:58 main.map
-rw------- 1 mark users 93106 Sep 17 18:58 main.o
-rw------- 1 root root 136 Sep 20 16:12 user.c


(20-09-2011, 11:04 PM)regis Wrote: Check permissions on source/stdout and do "sudo chmod 777 source/stdout" if necessary, then try as normal user (without su or sudo) as it should work.


(20-09-2011, 09:30 PM)g0mgx Wrote:
(20-09-2011, 08:14 PM)regis Wrote: Hi,
Congratulation for your board !
The problem seems that you don't have the right permission on usb port.
What version of Pinguino do you have ? x.2 or 9.5 ?

Anyway, check if you are in the plugdev group : groups $USER
If not : sudo useradd -G plugdev $USER
or sudo usermod -a -G plugdev $USER

Check also this file : /etc/udev/rules.d/41-microchip.rules
You should have something like that :
<quote>
# Pinguino (PIC18F)
ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="feaa", MODE="0660",GROUP="plugdev"
</quote>
On some linux installations, you may need to use SYSFS instead of ATTRS
If you change the file, tell Linux to reload udev rules by entering the following in the terminal window : sudo udevadm trigger
You can find a 41-microchip.rules file in directory extra from x.2
Régis

Hi!

Thanks for the pointers;

I've got Pingino version 9 - the file I run is pinguinobeta9-05.py

I don't have a plugdev group, might it be called something else on Suse? My user account is in groups microchip and user.

My 41-microchip.rules contains:

# Pinguino
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="feaa", MODE="0660",GROUP="microchip"

Any use?

Reply
21-09-2011, 01:31 PM,
#8
RE: Newby Install
Hi,
Actually Pinguino must use its own SDCC version with its own linker files so don't change the paths. It can't work !
Régis


(21-09-2011, 09:46 AM)g0mgx Wrote: I don't think this is a usb permissions thing. Looking at the error message again and then taking a peek at the pinguinobeta9-05.py file at the appropriate line it's the compile command that's failing.

The first thing I note is that the location of sdcc is hard coded as /tools/bin/sdcc whereas mine is located at /usr/local/bin/sdcc. So I changed that and now I see a different error. I thought the best thing would be to re-create the compile command as a stand alone shell script; so I have:

/usr/local/bin/sdcc -mpic16 --denable-peeps --obanksel=9 --opt-code-size --optimize-cmp --optimize-df -p18f4550 -I include -I /usr/local/share/sdcc/include/pic16 source/main.c

Initially this told me that I didn't have the 18f4550.h file and then the 18f2445.h file. I found these listed as part of the include files that should be part of sdcc and placed them in the sdcc/include/pic16 directory. Now the error is:

source/main.c:25:19: error: macro.h: No such file or directory
In file included from source/main.c:28:

I was confident (and still am) that I have installed sdcc correctly. sdcc -v gives me:

SDCC : mcs51/gbz80/z80/ds390/pic16/pic14/TININative/ds400/hc08 3.0.0 #6037 (Oct 31 2010) (Linux)

I get the impression that there is something quite simple missing here on my install? The sdcc-3.0.0-i386-unknown-linux2.5-tar-bz2 file doesn't have these .h files in the include/pic16 file structure.

Any ideas? please? Wrong sdcc?

(21-09-2011, 08:11 AM)g0mgx Wrote: Hmmm; I don't have a source/stdout... the source directory contains:

drwx------ 2 mark users 4096 Sep 20 16:12 .
drwx------ 13 mark users 4096 Sep 20 16:15 ..
-rw------- 1 mark users 1940 Sep 17 18:58 common_types.h
-rw------- 1 mark users 82271 Sep 17 18:58 main.asm
-rw------- 1 mark users 3188 Sep 17 18:58 main.c
-rw------- 1 mark users 39424 Sep 17 18:58 main.cod
-rw------- 1 mark users 225530 Sep 17 18:58 main.lst
-rw------- 1 mark users 58329 Sep 17 18:58 main.map
-rw------- 1 mark users 93106 Sep 17 18:58 main.o
-rw------- 1 root root 136 Sep 20 16:12 user.c


(20-09-2011, 11:04 PM)regis Wrote: Check permissions on source/stdout and do "sudo chmod 777 source/stdout" if necessary, then try as normal user (without su or sudo) as it should work.


(20-09-2011, 09:30 PM)g0mgx Wrote:
(20-09-2011, 08:14 PM)regis Wrote: Hi,
Congratulation for your board !
The problem seems that you don't have the right permission on usb port.
What version of Pinguino do you have ? x.2 or 9.5 ?

Anyway, check if you are in the plugdev group : groups $USER
If not : sudo useradd -G plugdev $USER
or sudo usermod -a -G plugdev $USER

Check also this file : /etc/udev/rules.d/41-microchip.rules
You should have something like that :
<quote>
# Pinguino (PIC18F)
ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="feaa", MODE="0660",GROUP="plugdev"
</quote>
On some linux installations, you may need to use SYSFS instead of ATTRS
If you change the file, tell Linux to reload udev rules by entering the following in the terminal window : sudo udevadm trigger
You can find a 41-microchip.rules file in directory extra from x.2
Régis

Hi!

Thanks for the pointers;

I've got Pingino version 9 - the file I run is pinguinobeta9-05.py

I don't have a plugdev group, might it be called something else on Suse? My user account is in groups microchip and user.

My 41-microchip.rules contains:

# Pinguino
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="feaa", MODE="0660",GROUP="microchip"

Any use?

It is easier to complain than it is to do, but it is better to do than it is to complain.
Reply
21-09-2011, 05:15 PM,
#9
RE: Newby Install
Now that was a really great clue!

I found another PC I had here and installed Ubuntu 11.4; then I used an install script for Pinguino I found on the forum somewhere that downloaded, installed and configured version Beta 7.

That was working perfectly. I then installed the latest version tar and that is also working perfectly under Ubuntu.

So I have deleted everything and tried a fresh install under Suse repeating the steps above (converting the Ubuntu script into the same for Suse) and have that successfully working also now.

Thanks for all your help.

Mark.



(21-09-2011, 01:31 PM)regis Wrote: Hi,
Actually Pinguino must use its own SDCC version with its own linker files so don't change the paths. It can't work !
Régis


(21-09-2011, 09:46 AM)g0mgx Wrote: I don't think this is a usb permissions thing. Looking at the error message again and then taking a peek at the pinguinobeta9-05.py file at the appropriate line it's the compile command that's failing.

The first thing I note is that the location of sdcc is hard coded as /tools/bin/sdcc whereas mine is located at /usr/local/bin/sdcc. So I changed that and now I see a different error. I thought the best thing would be to re-create the compile command as a stand alone shell script; so I have:

/usr/local/bin/sdcc -mpic16 --denable-peeps --obanksel=9 --opt-code-size --optimize-cmp --optimize-df -p18f4550 -I include -I /usr/local/share/sdcc/include/pic16 source/main.c

Initially this told me that I didn't have the 18f4550.h file and then the 18f2445.h file. I found these listed as part of the include files that should be part of sdcc and placed them in the sdcc/include/pic16 directory. Now the error is:

source/main.c:25:19: error: macro.h: No such file or directory
In file included from source/main.c:28:

I was confident (and still am) that I have installed sdcc correctly. sdcc -v gives me:

SDCC : mcs51/gbz80/z80/ds390/pic16/pic14/TININative/ds400/hc08 3.0.0 #6037 (Oct 31 2010) (Linux)

I get the impression that there is something quite simple missing here on my install? The sdcc-3.0.0-i386-unknown-linux2.5-tar-bz2 file doesn't have these .h files in the include/pic16 file structure.

Any ideas? please? Wrong sdcc?

(21-09-2011, 08:11 AM)g0mgx Wrote: Hmmm; I don't have a source/stdout... the source directory contains:

drwx------ 2 mark users 4096 Sep 20 16:12 .
drwx------ 13 mark users 4096 Sep 20 16:15 ..
-rw------- 1 mark users 1940 Sep 17 18:58 common_types.h
-rw------- 1 mark users 82271 Sep 17 18:58 main.asm
-rw------- 1 mark users 3188 Sep 17 18:58 main.c
-rw------- 1 mark users 39424 Sep 17 18:58 main.cod
-rw------- 1 mark users 225530 Sep 17 18:58 main.lst
-rw------- 1 mark users 58329 Sep 17 18:58 main.map
-rw------- 1 mark users 93106 Sep 17 18:58 main.o
-rw------- 1 root root 136 Sep 20 16:12 user.c


(20-09-2011, 11:04 PM)regis Wrote: Check permissions on source/stdout and do "sudo chmod 777 source/stdout" if necessary, then try as normal user (without su or sudo) as it should work.


(20-09-2011, 09:30 PM)g0mgx Wrote: Hi!

Thanks for the pointers;

I've got Pingino version 9 - the file I run is pinguinobeta9-05.py

I don't have a plugdev group, might it be called something else on Suse? My user account is in groups microchip and user.

My 41-microchip.rules contains:

# Pinguino
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="feaa", MODE="0660",GROUP="microchip"

Any use?

Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)