| View previous topic :: View next topic |
| Author |
Message |
smead
Joined: 23 Jul 2006 Posts: 65 Location: USA
|
Posted: Fri Jul 28, 2006 10:22 pm Post subject: parport issues |
|
|
I've been able to get openocd working with the configure command as follows:
./configure --enable-parport
but of course it takes root to start it.
but after make clean and doing this configure:
./configure --enable-parport_ppdev and make, make install I get these messages:
watt:/home/smead/c_code/arm/lpc2103_bd# openocd -f lpc2103_openocd_wig.cfg
Info: openocd.c:82 main(): Open On-Chip Debugger (2006-07-15 12:00 CEST)
Info: configuration.c:50 configuration_output_handler(): Command parport_port not found
Info: configuration.c:50 configuration_output_handler(): Command parport_cable not found
Error: jtag.c:1189 jtag_init(): No valid jtag interface found (parport_ppdev)
clues?? |
|
| Back to top |
|
 |
Dominic
Joined: 03 Jan 2006 Posts: 516
|
Posted: Sat Jul 29, 2006 2:16 am Post subject: |
|
|
Hey,
--enable-parport_ppdev is just an option to the 'parport' driver. You still have to use --enable-parport, too, if you want to access the PC's parallel port using the PPDEV interface.
The same is true for the giveio interface on Windows. You have to use both --enable-parport and --enable-parport_giveio.
Regards,
Dominic |
|
| Back to top |
|
 |
smead
Joined: 23 Jul 2006 Posts: 65 Location: USA
|
Posted: Sat Jul 29, 2006 10:51 pm Post subject: |
|
|
Dominic,
Thanks for the help but it didn't work for me. I tried both orders of options.
#when it doesn't work I get this as user or root
openocd -f lpc2103_openocd_wig.cfg
Info: openocd.c:82 main(): Open On-Chip Debugger (2006-07-15 12:00 CEST)
Error: parport.c:318 parport_init(): cannot open device. check it exists and that user read and write rights are set
It may have something to do with my setup. I don't have lpd running, and have been using the parport for jtag interface to the TI msp430F family. Here's some more information.
watt:/usr/local/bin# ls -l /dev/par*
crw-rw---- 1 root lp 99, 0 Jul 21 15:01 /dev/parport0
watt:/usr/local/bin# lsmod |grep parport
parport_pc 37796 1
parport 43272 3 ppdev,lp,parport_pc
Do I need to knock lp and parport_pc off parport?
It's not a big hardship to start openocd as root, but it would be nice to avoid it.
BTW, I've been able to use GDB on the Olimex LPC2103 board using Linux, so I''m very thankful for your efforts. All and all, openocd has been the easiest install and configure of several development platforms I'm using. |
|
| Back to top |
|
 |
Dominic
Joined: 03 Jan 2006 Posts: 516
|
Posted: Sun Jul 30, 2006 2:43 am Post subject: |
|
|
Hi,
you could try removing the lp module, but it shouldn't hurt if it's loaded.
When using ppdev to access the parallel port, make sure you have
parport_port 0 (the default)
in your config file. Maybe your problem is because of a config file that specifies parport_port 0x378.
I'll change the error message to display the name of the device or the number of the port it tried to open, to make these cases more easier to spot.
Regards,
Dominic |
|
| Back to top |
|
 |
|