MOD711
Locked
|
Hello eLua people.
We are trying to use OpenOCD to flash a .bin eLua image in the MOD711 from ScTec. But we are having a problem here that we can't figure out the solution. When we finish all the steps of the tutorial in the site, this error message appears: Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST) Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open ftdi device: device not found Any idea how to fix it? Thanks, Teo -------------- next part -------------- An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/98d7d2a3/attachment.html |
|
|
Resending to list, as usual ... :)
---------- Forwarded message ---------- From: Bogdan Marinescu <bogdan.marinescu at gmail.com> Date: Wed, Oct 29, 2008 at 10:21 PM Subject: Re: [Elua-dev] MOD711 To: T?o Benjamin <teo.benjamin at gmail.com> Hi, What kind of JTAG adapter are you using? Bogdan On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > Hello eLua people. > We are trying to use OpenOCD to flash a .bin eLua image in the MOD711 from > ScTec. > But we are having a problem here that we can't figure out the solution. > When we finish all the steps of the tutorial in the site, this error > message appears: > > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST) > Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open ftdi device: > device not found > > > Any idea how to fix it? > > Thanks, > Teo > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/a6633dc6/attachment.html |
|
|
The same we sent you last month... ;)
We tried this in Linux and this message appears. We tried in Windows and the message was this one: Open On-Chip Debugger (2008-06-19 19:00) svn: 717 URL: http://svn.berlios.de/svnroot/repos/openocd/trunk Info: options.c:50 configuration_output_handler(): couldn't open script file str7prg.cfg Error: jtag.c:1511 jtag_interface_init(): JTAG interface has to be specified, see "interface" command On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < bogdan.marinescu at gmail.com> wrote: > Resending to list, as usual ... :) > > > ---------- Forwarded message ---------- > From: Bogdan Marinescu <bogdan.marinescu at gmail.com> > Date: Wed, Oct 29, 2008 at 10:21 PM > Subject: Re: [Elua-dev] MOD711 > To: T?o Benjamin <teo.benjamin at gmail.com> > > > Hi, > > What kind of JTAG adapter are you using? > > Bogdan > > On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > >> Hello eLua people. >> We are trying to use OpenOCD to flash a .bin eLua image in the MOD711 from >> ScTec. >> But we are having a problem here that we can't figure out the solution. >> When we finish all the steps of the tutorial in the site, this error >> message appears: >> >> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >> CEST) >> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open ftdi device: >> device not found >> >> >> Any idea how to fix it? >> >> Thanks, >> Teo >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/56606f63/attachment.html |
|
|
Well, my tutorial also says this (feels kinda strange quoting myself :) ):
"The board comes with its own JTAG adadpter, but it uses a parallel interface, and since my computer doesn't have one, I used the ARM-USB-TINY<http://www.olimex.com/dev/arm-usb-tiny.html>from Olimex" So you'll need to change your interface description. I think you should use this: #interface interface parport parport_port 0x378 parport_cable wiggler jtag_speed 0 instead of this: # JTAG interface interface ft2232 ft2232_device_desc "Olimex OpenOCD JTAG TINY A" ft2232_layout olimex-jtag jtag_speed 20 jtag_nsrst_delay 200 jtag_ntrst_delay 200 in the "str7prg.cfg" file. Change "0x378" to the correct value if you're not using LPT1. Also, see this thread for more details/troubleshooting data: http://en.mikrocontroller.net/topic/81646#new Good luck! Bogdan On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > The same we sent you last month... ;) > We tried this in Linux and this message appears. > > We tried in Windows and the message was this one: > > Open On-Chip Debugger (2008-06-19 19:00) svn: 717 > URL: http://svn.berlios.de/svnroot/repos/openocd/trunk > Info: options.c:50 configuration_output_handler(): couldn't open script > file > str7prg.cfg > Error: jtag.c:1511 jtag_interface_init(): JTAG interface has to be > specified, > see "interface" command > > > > On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < > bogdan.marinescu at gmail.com> wrote: > >> Resending to list, as usual ... :) >> >> >> ---------- Forwarded message ---------- >> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >> Date: Wed, Oct 29, 2008 at 10:21 PM >> Subject: Re: [Elua-dev] MOD711 >> To: T?o Benjamin <teo.benjamin at gmail.com> >> >> >> Hi, >> >> What kind of JTAG adapter are you using? >> >> Bogdan >> >> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >> >>> Hello eLua people. >>> We are trying to use OpenOCD to flash a .bin eLua image in the MOD711 >>> from ScTec. >>> But we are having a problem here that we can't figure out the solution. >>> When we finish all the steps of the tutorial in the site, this error >>> message appears: >>> >>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>> CEST) >>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open ftdi device: >>> device not found >>> >>> >>> Any idea how to fix it? >>> >>> Thanks, >>> Teo >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/04f7bfa6/attachment.html |
|
|
Resending to erveryone now...
Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST) Error: parport.c:359 parport_init(): cannot open device. check it exists and that user read and write rights are set I'll have a look on the link you sent... On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < bogdan.marinescu at gmail.com> wrote: > Well, my tutorial also says this (feels kinda strange quoting myself :) ): > > "The board comes with its own JTAG adadpter, but it uses a parallel > interface, and since my computer doesn't have one, I used the ARM-USB-TINY<http://www.olimex.com/dev/arm-usb-tiny.html>from Olimex" > > So you'll need to change your interface description. I think you should use > this: > > #interface > interface parport > parport_port 0x378 > parport_cable wiggler > jtag_speed 0 > > instead of this: > > # JTAG interface > interface ft2232 > ft2232_device_desc "Olimex OpenOCD JTAG TINY A" > ft2232_layout olimex-jtag > jtag_speed 20 > jtag_nsrst_delay 200 > jtag_ntrst_delay 200 > > in the "str7prg.cfg" file. > Change "0x378" to the correct value if you're not using LPT1. > Also, see this thread for more details/troubleshooting data: > > http://en.mikrocontroller.net/topic/81646#new > > Good luck! > > Bogdan > > > On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > >> The same we sent you last month... ;) >> We tried this in Linux and this message appears. >> >> We tried in Windows and the message was this one: >> >> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >> Info: options.c:50 configuration_output_handler(): couldn't open >> script file >> str7prg.cfg >> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has to be >> specified, >> see "interface" command >> >> >> >> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >> bogdan.marinescu at gmail.com> wrote: >> >>> Resending to list, as usual ... :) >>> >>> >>> ---------- Forwarded message ---------- >>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>> Date: Wed, Oct 29, 2008 at 10:21 PM >>> Subject: Re: [Elua-dev] MOD711 >>> To: T?o Benjamin <teo.benjamin at gmail.com> >>> >>> >>> Hi, >>> >>> What kind of JTAG adapter are you using? >>> >>> Bogdan >>> >>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>> >>>> Hello eLua people. >>>> We are trying to use OpenOCD to flash a .bin eLua image in the MOD711 >>>> from ScTec. >>>> But we are having a problem here that we can't figure out the solution. >>>> When we finish all the steps of the tutorial in the site, this error >>>> message appears: >>>> >>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>> CEST) >>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open ftdi >>>> device: device not found >>>> >>>> >>>> Any idea how to fix it? >>>> >>>> Thanks, >>>> Teo >>>> >>>> _______________________________________________ >>>> Elua-dev mailing list >>>> Elua-dev at lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>> >>>> >>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/be03328f/attachment-0001.html |
|
|
In reply to this post by BogdanM
This is in Linux...
On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < bogdan.marinescu at gmail.com> wrote: > This comes from Windows or Linux? In Windows, you need to use giveio. In > Linux you should probably set the right permission to /dev/parport0. > > > On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > >> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >> CEST) >> Error: parport.c:359 parport_init(): cannot open device. check it exists >> and that user read and write rights are set >> >> I'll have a look on the link you sent... >> >> >> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >> bogdan.marinescu at gmail.com> wrote: >> >>> Well, my tutorial also says this (feels kinda strange quoting myself :) >>> ): >>> >>> "The board comes with its own JTAG adadpter, but it uses a parallel >>> interface, and since my computer doesn't have one, I used the >>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html> from Olimex" >>> >>> So you'll need to change your interface description. I think you should >>> use this: >>> >>> #interface >>> interface parport >>> parport_port 0x378 >>> parport_cable wiggler >>> jtag_speed 0 >>> >>> instead of this: >>> >>> # JTAG interface >>> interface ft2232 >>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>> ft2232_layout olimex-jtag >>> jtag_speed 20 >>> jtag_nsrst_delay 200 >>> jtag_ntrst_delay 200 >>> >>> in the "str7prg.cfg" file. >>> Change "0x378" to the correct value if you're not using LPT1. >>> Also, see this thread for more details/troubleshooting data: >>> >>> http://en.mikrocontroller.net/topic/81646#new >>> >>> Good luck! >>> >>> Bogdan >>> >>> >>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>> >>>> The same we sent you last month... ;) >>>> We tried this in Linux and this message appears. >>>> >>>> We tried in Windows and the message was this one: >>>> >>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>> Info: options.c:50 configuration_output_handler(): couldn't open >>>> script file >>>> str7prg.cfg >>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has to be >>>> specified, >>>> see "interface" command >>>> >>>> >>>> >>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>> bogdan.marinescu at gmail.com> wrote: >>>> >>>>> Resending to list, as usual ... :) >>>>> >>>>> >>>>> ---------- Forwarded message ---------- >>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>> Subject: Re: [Elua-dev] MOD711 >>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>> >>>>> >>>>> Hi, >>>>> >>>>> What kind of JTAG adapter are you using? >>>>> >>>>> Bogdan >>>>> >>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin <teo.benjamin at gmail.com >>>>> > wrote: >>>>> >>>>>> Hello eLua people. >>>>>> We are trying to use OpenOCD to flash a .bin eLua image in the MOD711 >>>>>> from ScTec. >>>>>> But we are having a problem here that we can't figure out the >>>>>> solution. >>>>>> When we finish all the steps of the tutorial in the site, this error >>>>>> message appears: >>>>>> >>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>>> CEST) >>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open ftdi >>>>>> device: device not found >>>>>> >>>>>> >>>>>> Any idea how to fix it? >>>>>> >>>>>> Thanks, >>>>>> Teo >>>>>> >>>>>> _______________________________________________ >>>>>> Elua-dev mailing list >>>>>> Elua-dev at lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>> >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Elua-dev mailing list >>>>> Elua-dev at lists.berlios.de >>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>> >>>>> >>>> >>> >> > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/6ae0d0df/attachment.html |
|
|
Then try setting the right permissions to /dev/parport0, or just sudo
openocd ... I don't know, never tried Linux with this parport interface. On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > This is in Linux... > > > On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < > bogdan.marinescu at gmail.com> wrote: > >> This comes from Windows or Linux? In Windows, you need to use giveio. In >> Linux you should probably set the right permission to /dev/parport0. >> >> >> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >> >>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>> CEST) >>> Error: parport.c:359 parport_init(): cannot open device. check it >>> exists and that user read and write rights are set >>> >>> I'll have a look on the link you sent... >>> >>> >>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>> bogdan.marinescu at gmail.com> wrote: >>> >>>> Well, my tutorial also says this (feels kinda strange quoting myself :) >>>> ): >>>> >>>> "The board comes with its own JTAG adadpter, but it uses a parallel >>>> interface, and since my computer doesn't have one, I used the >>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html> from Olimex" >>>> >>>> So you'll need to change your interface description. I think you should >>>> use this: >>>> >>>> #interface >>>> interface parport >>>> parport_port 0x378 >>>> parport_cable wiggler >>>> jtag_speed 0 >>>> >>>> instead of this: >>>> >>>> # JTAG interface >>>> interface ft2232 >>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>> ft2232_layout olimex-jtag >>>> jtag_speed 20 >>>> jtag_nsrst_delay 200 >>>> jtag_ntrst_delay 200 >>>> >>>> in the "str7prg.cfg" file. >>>> Change "0x378" to the correct value if you're not using LPT1. >>>> Also, see this thread for more details/troubleshooting data: >>>> >>>> http://en.mikrocontroller.net/topic/81646#new >>>> >>>> Good luck! >>>> >>>> Bogdan >>>> >>>> >>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>>> >>>>> The same we sent you last month... ;) >>>>> We tried this in Linux and this message appears. >>>>> >>>>> We tried in Windows and the message was this one: >>>>> >>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>> Info: options.c:50 configuration_output_handler(): couldn't open >>>>> script file >>>>> str7prg.cfg >>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has to be >>>>> specified, >>>>> see "interface" command >>>>> >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>> bogdan.marinescu at gmail.com> wrote: >>>>> >>>>>> Resending to list, as usual ... :) >>>>>> >>>>>> >>>>>> ---------- Forwarded message ---------- >>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> What kind of JTAG adapter are you using? >>>>>> >>>>>> Bogdan >>>>>> >>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>> teo.benjamin at gmail.com> wrote: >>>>>> >>>>>>> Hello eLua people. >>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in the MOD711 >>>>>>> from ScTec. >>>>>>> But we are having a problem here that we can't figure out the >>>>>>> solution. >>>>>>> When we finish all the steps of the tutorial in the site, this error >>>>>>> message appears: >>>>>>> >>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>>>> CEST) >>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open ftdi >>>>>>> device: device not found >>>>>>> >>>>>>> >>>>>>> Any idea how to fix it? >>>>>>> >>>>>>> Thanks, >>>>>>> Teo >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Elua-dev mailing list >>>>>>> Elua-dev at lists.berlios.de >>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Elua-dev mailing list >>>>>> Elua-dev at lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>> >>>>>> >>>>> >>>> >>> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/17e3dd8d/attachment.html |
|
|
I did sudo openocd and an error message appeared.
Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST) Error: configuration.c:121 parse_config_file(): couldn't open config file I'm not quite sure how to set the permission to parport0 properly. Thanks for the help On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < bogdan.marinescu at gmail.com> wrote: > Then try setting the right permissions to /dev/parport0, or just sudo > openocd ... I don't know, never tried Linux with this parport interface. > > > On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > >> This is in Linux... >> >> >> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >> bogdan.marinescu at gmail.com> wrote: >> >>> This comes from Windows or Linux? In Windows, you need to use giveio. In >>> Linux you should probably set the right permission to /dev/parport0. >>> >>> >>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>> >>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>> CEST) >>>> Error: parport.c:359 parport_init(): cannot open device. check it >>>> exists and that user read and write rights are set >>>> >>>> I'll have a look on the link you sent... >>>> >>>> >>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>> bogdan.marinescu at gmail.com> wrote: >>>> >>>>> Well, my tutorial also says this (feels kinda strange quoting myself :) >>>>> ): >>>>> >>>>> "The board comes with its own JTAG adadpter, but it uses a parallel >>>>> interface, and since my computer doesn't have one, I used the >>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html> from >>>>> Olimex" >>>>> >>>>> So you'll need to change your interface description. I think you should >>>>> use this: >>>>> >>>>> #interface >>>>> interface parport >>>>> parport_port 0x378 >>>>> parport_cable wiggler >>>>> jtag_speed 0 >>>>> >>>>> instead of this: >>>>> >>>>> # JTAG interface >>>>> interface ft2232 >>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>> ft2232_layout olimex-jtag >>>>> jtag_speed 20 >>>>> jtag_nsrst_delay 200 >>>>> jtag_ntrst_delay 200 >>>>> >>>>> in the "str7prg.cfg" file. >>>>> Change "0x378" to the correct value if you're not using LPT1. >>>>> Also, see this thread for more details/troubleshooting data: >>>>> >>>>> http://en.mikrocontroller.net/topic/81646#new >>>>> >>>>> Good luck! >>>>> >>>>> Bogdan >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin <teo.benjamin at gmail.com >>>>> > wrote: >>>>> >>>>>> The same we sent you last month... ;) >>>>>> We tried this in Linux and this message appears. >>>>>> >>>>>> We tried in Windows and the message was this one: >>>>>> >>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>> Info: options.c:50 configuration_output_handler(): couldn't open >>>>>> script file >>>>>> str7prg.cfg >>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has to be >>>>>> specified, >>>>>> see "interface" command >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>> >>>>>>> Resending to list, as usual ... :) >>>>>>> >>>>>>> >>>>>>> ---------- Forwarded message ---------- >>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> What kind of JTAG adapter are you using? >>>>>>> >>>>>>> Bogdan >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>> >>>>>>>> Hello eLua people. >>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in the >>>>>>>> MOD711 from ScTec. >>>>>>>> But we are having a problem here that we can't figure out the >>>>>>>> solution. >>>>>>>> When we finish all the steps of the tutorial in the site, this error >>>>>>>> message appears: >>>>>>>> >>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>> 09:00 CEST) >>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open ftdi >>>>>>>> device: device not found >>>>>>>> >>>>>>>> >>>>>>>> Any idea how to fix it? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Teo >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Elua-dev mailing list >>>>>>>> Elua-dev at lists.berlios.de >>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Elua-dev mailing list >>>>>>> Elua-dev at lists.berlios.de >>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/bafc50eb/attachment-0001.html |
|
|
I mean "sudo openocd" with the same "openocd" parameters you used before.
Something like this: $ sudo openocd -f str7prg.cfg On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > I did sudo openocd and an error message appeared. > > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST) > Error: configuration.c:121 parse_config_file(): couldn't open config file > > I'm not quite sure how to set the permission to parport0 properly. > > Thanks for the help > > > On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < > bogdan.marinescu at gmail.com> wrote: > >> Then try setting the right permissions to /dev/parport0, or just sudo >> openocd ... I don't know, never tried Linux with this parport interface. >> >> >> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >> >>> This is in Linux... >>> >>> >>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>> bogdan.marinescu at gmail.com> wrote: >>> >>>> This comes from Windows or Linux? In Windows, you need to use giveio. >>>> In Linux you should probably set the right permission to /dev/parport0. >>>> >>>> >>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>>> >>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>> CEST) >>>>> Error: parport.c:359 parport_init(): cannot open device. check it >>>>> exists and that user read and write rights are set >>>>> >>>>> I'll have a look on the link you sent... >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>> bogdan.marinescu at gmail.com> wrote: >>>>> >>>>>> Well, my tutorial also says this (feels kinda strange quoting myself >>>>>> :) ): >>>>>> >>>>>> "The board comes with its own JTAG adadpter, but it uses a parallel >>>>>> interface, and since my computer doesn't have one, I used the >>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html> from >>>>>> Olimex" >>>>>> >>>>>> So you'll need to change your interface description. I think you >>>>>> should use this: >>>>>> >>>>>> #interface >>>>>> interface parport >>>>>> parport_port 0x378 >>>>>> parport_cable wiggler >>>>>> jtag_speed 0 >>>>>> >>>>>> instead of this: >>>>>> >>>>>> # JTAG interface >>>>>> interface ft2232 >>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>> ft2232_layout olimex-jtag >>>>>> jtag_speed 20 >>>>>> jtag_nsrst_delay 200 >>>>>> jtag_ntrst_delay 200 >>>>>> >>>>>> in the "str7prg.cfg" file. >>>>>> Change "0x378" to the correct value if you're not using LPT1. >>>>>> Also, see this thread for more details/troubleshooting data: >>>>>> >>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>> >>>>>> Good luck! >>>>>> >>>>>> Bogdan >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>> teo.benjamin at gmail.com> wrote: >>>>>> >>>>>>> The same we sent you last month... ;) >>>>>>> We tried this in Linux and this message appears. >>>>>>> >>>>>>> We tried in Windows and the message was this one: >>>>>>> >>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>> Info: options.c:50 configuration_output_handler(): couldn't open >>>>>>> script file >>>>>>> str7prg.cfg >>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has to be >>>>>>> specified, >>>>>>> see "interface" command >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>> >>>>>>>> Resending to list, as usual ... :) >>>>>>>> >>>>>>>> >>>>>>>> ---------- Forwarded message ---------- >>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>> >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> What kind of JTAG adapter are you using? >>>>>>>> >>>>>>>> Bogdan >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>> >>>>>>>>> Hello eLua people. >>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in the >>>>>>>>> MOD711 from ScTec. >>>>>>>>> But we are having a problem here that we can't figure out the >>>>>>>>> solution. >>>>>>>>> When we finish all the steps of the tutorial in the site, this >>>>>>>>> error message appears: >>>>>>>>> >>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>> 09:00 CEST) >>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open ftdi >>>>>>>>> device: device not found >>>>>>>>> >>>>>>>>> >>>>>>>>> Any idea how to fix it? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Teo >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Elua-dev mailing list >>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Elua-dev mailing list >>>>>>>> Elua-dev at lists.berlios.de >>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/b3f02a8c/attachment.html |
|
|
I'm sorry, I wasn't any clear.
When I do this ($ sudo openocd -f str7prg.cfg) the same error occours. No matter what I try now, it happens... hehe But if I do only "sudo openocd", that other error message shows up, but I don't know if that means something. I'm trying to figure out how to set the right permission to parport0. if I do "ls -l /dev/parport0" the terminal shows me: crw-rw---- 1 lp scanner 99, 0 2008-10-14 15:39 /dev/parport0 I don't know right now what to do... On Wed, Oct 29, 2008 at 7:02 PM, Bogdan Marinescu < bogdan.marinescu at gmail.com> wrote: > I mean "sudo openocd" with the same "openocd" parameters you used before. > Something like this: > > $ sudo openocd -f str7prg.cfg > > > On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > >> I did sudo openocd and an error message appeared. >> >> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >> CEST) >> Error: configuration.c:121 parse_config_file(): couldn't open config >> file >> >> I'm not quite sure how to set the permission to parport0 properly. >> >> Thanks for the help >> >> >> On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < >> bogdan.marinescu at gmail.com> wrote: >> >>> Then try setting the right permissions to /dev/parport0, or just sudo >>> openocd ... I don't know, never tried Linux with this parport interface. >>> >>> >>> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>> >>>> This is in Linux... >>>> >>>> >>>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>>> bogdan.marinescu at gmail.com> wrote: >>>> >>>>> This comes from Windows or Linux? In Windows, you need to use giveio. >>>>> In Linux you should probably set the right permission to /dev/parport0. >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin <teo.benjamin at gmail.com >>>>> > wrote: >>>>> >>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>>> CEST) >>>>>> Error: parport.c:359 parport_init(): cannot open device. check it >>>>>> exists and that user read and write rights are set >>>>>> >>>>>> I'll have a look on the link you sent... >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>> >>>>>>> Well, my tutorial also says this (feels kinda strange quoting myself >>>>>>> :) ): >>>>>>> >>>>>>> "The board comes with its own JTAG adadpter, but it uses a parallel >>>>>>> interface, and since my computer doesn't have one, I used the >>>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html> from >>>>>>> Olimex" >>>>>>> >>>>>>> So you'll need to change your interface description. I think you >>>>>>> should use this: >>>>>>> >>>>>>> #interface >>>>>>> interface parport >>>>>>> parport_port 0x378 >>>>>>> parport_cable wiggler >>>>>>> jtag_speed 0 >>>>>>> >>>>>>> instead of this: >>>>>>> >>>>>>> # JTAG interface >>>>>>> interface ft2232 >>>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>>> ft2232_layout olimex-jtag >>>>>>> jtag_speed 20 >>>>>>> jtag_nsrst_delay 200 >>>>>>> jtag_ntrst_delay 200 >>>>>>> >>>>>>> in the "str7prg.cfg" file. >>>>>>> Change "0x378" to the correct value if you're not using LPT1. >>>>>>> Also, see this thread for more details/troubleshooting data: >>>>>>> >>>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>>> >>>>>>> Good luck! >>>>>>> >>>>>>> Bogdan >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>> >>>>>>>> The same we sent you last month... ;) >>>>>>>> We tried this in Linux and this message appears. >>>>>>>> >>>>>>>> We tried in Windows and the message was this one: >>>>>>>> >>>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>>> Info: options.c:50 configuration_output_handler(): couldn't open >>>>>>>> script file >>>>>>>> str7prg.cfg >>>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has to be >>>>>>>> specified, >>>>>>>> see "interface" command >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>> >>>>>>>>> Resending to list, as usual ... :) >>>>>>>>> >>>>>>>>> >>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>>> >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> What kind of JTAG adapter are you using? >>>>>>>>> >>>>>>>>> Bogdan >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hello eLua people. >>>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in the >>>>>>>>>> MOD711 from ScTec. >>>>>>>>>> But we are having a problem here that we can't figure out the >>>>>>>>>> solution. >>>>>>>>>> When we finish all the steps of the tutorial in the site, this >>>>>>>>>> error message appears: >>>>>>>>>> >>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>>> 09:00 CEST) >>>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open ftdi >>>>>>>>>> device: device not found >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Any idea how to fix it? >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Teo >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Elua-dev mailing list >>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Elua-dev mailing list >>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Elua-dev mailing list >>>> Elua-dev at lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>> >>>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/d567f5a8/attachment-0001.html |
|
|
Weird. Try this:
parport_port 0 instead of this: parport_port 0x378 in str7prg.cfg, and then $ sudo openocd -f str7prg.cfg On Wed, Oct 29, 2008 at 11:10 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > I'm sorry, I wasn't any clear. > When I do this ($ sudo openocd -f str7prg.cfg) the same error occours. No > matter what I try now, it happens... hehe > But if I do only "sudo openocd", that other error message shows up, but I > don't know if that means something. > > I'm trying to figure out how to set the right permission to parport0. > if I do "ls -l /dev/parport0" the terminal shows me: > crw-rw---- 1 lp scanner 99, 0 2008-10-14 15:39 /dev/parport0 > > I don't know right now what to do... > > > On Wed, Oct 29, 2008 at 7:02 PM, Bogdan Marinescu < > bogdan.marinescu at gmail.com> wrote: > >> I mean "sudo openocd" with the same "openocd" parameters you used before. >> Something like this: >> >> $ sudo openocd -f str7prg.cfg >> >> >> On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >> >>> I did sudo openocd and an error message appeared. >>> >>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>> CEST) >>> Error: configuration.c:121 parse_config_file(): couldn't open config >>> file >>> >>> I'm not quite sure how to set the permission to parport0 properly. >>> >>> Thanks for the help >>> >>> >>> On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < >>> bogdan.marinescu at gmail.com> wrote: >>> >>>> Then try setting the right permissions to /dev/parport0, or just sudo >>>> openocd ... I don't know, never tried Linux with this parport interface. >>>> >>>> >>>> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>>> >>>>> This is in Linux... >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>>>> bogdan.marinescu at gmail.com> wrote: >>>>> >>>>>> This comes from Windows or Linux? In Windows, you need to use giveio. >>>>>> In Linux you should probably set the right permission to /dev/parport0. >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin < >>>>>> teo.benjamin at gmail.com> wrote: >>>>>> >>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>>>> CEST) >>>>>>> Error: parport.c:359 parport_init(): cannot open device. check it >>>>>>> exists and that user read and write rights are set >>>>>>> >>>>>>> I'll have a look on the link you sent... >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>> >>>>>>>> Well, my tutorial also says this (feels kinda strange quoting myself >>>>>>>> :) ): >>>>>>>> >>>>>>>> "The board comes with its own JTAG adadpter, but it uses a parallel >>>>>>>> interface, and since my computer doesn't have one, I used the >>>>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html> from >>>>>>>> Olimex" >>>>>>>> >>>>>>>> So you'll need to change your interface description. I think you >>>>>>>> should use this: >>>>>>>> >>>>>>>> #interface >>>>>>>> interface parport >>>>>>>> parport_port 0x378 >>>>>>>> parport_cable wiggler >>>>>>>> jtag_speed 0 >>>>>>>> >>>>>>>> instead of this: >>>>>>>> >>>>>>>> # JTAG interface >>>>>>>> interface ft2232 >>>>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>>>> ft2232_layout olimex-jtag >>>>>>>> jtag_speed 20 >>>>>>>> jtag_nsrst_delay 200 >>>>>>>> jtag_ntrst_delay 200 >>>>>>>> >>>>>>>> in the "str7prg.cfg" file. >>>>>>>> Change "0x378" to the correct value if you're not using LPT1. >>>>>>>> Also, see this thread for more details/troubleshooting data: >>>>>>>> >>>>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>>>> >>>>>>>> Good luck! >>>>>>>> >>>>>>>> Bogdan >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>> >>>>>>>>> The same we sent you last month... ;) >>>>>>>>> We tried this in Linux and this message appears. >>>>>>>>> >>>>>>>>> We tried in Windows and the message was this one: >>>>>>>>> >>>>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>>>> Info: options.c:50 configuration_output_handler(): couldn't >>>>>>>>> open script file >>>>>>>>> str7prg.cfg >>>>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has to >>>>>>>>> be specified, >>>>>>>>> see "interface" command >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Resending to list, as usual ... :) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> What kind of JTAG adapter are you using? >>>>>>>>>> >>>>>>>>>> Bogdan >>>>>>>>>> >>>>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hello eLua people. >>>>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in the >>>>>>>>>>> MOD711 from ScTec. >>>>>>>>>>> But we are having a problem here that we can't figure out the >>>>>>>>>>> solution. >>>>>>>>>>> When we finish all the steps of the tutorial in the site, this >>>>>>>>>>> error message appears: >>>>>>>>>>> >>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>>>> 09:00 CEST) >>>>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open ftdi >>>>>>>>>>> device: device not found >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Any idea how to fix it? >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Teo >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Elua-dev mailing list >>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Elua-dev mailing list >>>>> Elua-dev at lists.berlios.de >>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Elua-dev mailing list >>>> Elua-dev at lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>> >>>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/69e7cacb/attachment.html |
|
|
Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST)
Error: configuration.c:121 parse_config_file(): couldn't open config file On Wed, Oct 29, 2008 at 7:13 PM, Bogdan Marinescu < bogdan.marinescu at gmail.com> wrote: > Weird. Try this: > > parport_port 0 > > instead of this: > > parport_port 0x378 > > in str7prg.cfg, and then > > $ sudo openocd -f str7prg.cfg > > On Wed, Oct 29, 2008 at 11:10 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > >> I'm sorry, I wasn't any clear. >> When I do this ($ sudo openocd -f str7prg.cfg) the same error occours. No >> matter what I try now, it happens... hehe >> But if I do only "sudo openocd", that other error message shows up, but I >> don't know if that means something. >> >> I'm trying to figure out how to set the right permission to parport0. >> if I do "ls -l /dev/parport0" the terminal shows me: >> crw-rw---- 1 lp scanner 99, 0 2008-10-14 15:39 /dev/parport0 >> >> I don't know right now what to do... >> >> >> On Wed, Oct 29, 2008 at 7:02 PM, Bogdan Marinescu < >> bogdan.marinescu at gmail.com> wrote: >> >>> I mean "sudo openocd" with the same "openocd" parameters you used before. >>> Something like this: >>> >>> $ sudo openocd -f str7prg.cfg >>> >>> >>> On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>> >>>> I did sudo openocd and an error message appeared. >>>> >>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>> CEST) >>>> Error: configuration.c:121 parse_config_file(): couldn't open config >>>> file >>>> >>>> I'm not quite sure how to set the permission to parport0 properly. >>>> >>>> Thanks for the help >>>> >>>> >>>> On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < >>>> bogdan.marinescu at gmail.com> wrote: >>>> >>>>> Then try setting the right permissions to /dev/parport0, or just sudo >>>>> openocd ... I don't know, never tried Linux with this parport interface. >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin <teo.benjamin at gmail.com >>>>> > wrote: >>>>> >>>>>> This is in Linux... >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>> >>>>>>> This comes from Windows or Linux? In Windows, you need to use >>>>>>> giveio. In Linux you should probably set the right permission to >>>>>>> /dev/parport0. >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin < >>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>> >>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>> 09:00 CEST) >>>>>>>> Error: parport.c:359 parport_init(): cannot open device. check it >>>>>>>> exists and that user read and write rights are set >>>>>>>> >>>>>>>> I'll have a look on the link you sent... >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>> >>>>>>>>> Well, my tutorial also says this (feels kinda strange quoting >>>>>>>>> myself :) ): >>>>>>>>> >>>>>>>>> "The board comes with its own JTAG adadpter, but it uses a parallel >>>>>>>>> interface, and since my computer doesn't have one, I used the >>>>>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html> from >>>>>>>>> Olimex" >>>>>>>>> >>>>>>>>> So you'll need to change your interface description. I think you >>>>>>>>> should use this: >>>>>>>>> >>>>>>>>> #interface >>>>>>>>> interface parport >>>>>>>>> parport_port 0x378 >>>>>>>>> parport_cable wiggler >>>>>>>>> jtag_speed 0 >>>>>>>>> >>>>>>>>> instead of this: >>>>>>>>> >>>>>>>>> # JTAG interface >>>>>>>>> interface ft2232 >>>>>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>>>>> ft2232_layout olimex-jtag >>>>>>>>> jtag_speed 20 >>>>>>>>> jtag_nsrst_delay 200 >>>>>>>>> jtag_ntrst_delay 200 >>>>>>>>> >>>>>>>>> in the "str7prg.cfg" file. >>>>>>>>> Change "0x378" to the correct value if you're not using LPT1. >>>>>>>>> Also, see this thread for more details/troubleshooting data: >>>>>>>>> >>>>>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>>>>> >>>>>>>>> Good luck! >>>>>>>>> >>>>>>>>> Bogdan >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> The same we sent you last month... ;) >>>>>>>>>> We tried this in Linux and this message appears. >>>>>>>>>> >>>>>>>>>> We tried in Windows and the message was this one: >>>>>>>>>> >>>>>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>>>>> Info: options.c:50 configuration_output_handler(): couldn't >>>>>>>>>> open script file >>>>>>>>>> str7prg.cfg >>>>>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has to >>>>>>>>>> be specified, >>>>>>>>>> see "interface" command >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Resending to list, as usual ... :) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> What kind of JTAG adapter are you using? >>>>>>>>>>> >>>>>>>>>>> Bogdan >>>>>>>>>>> >>>>>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hello eLua people. >>>>>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in the >>>>>>>>>>>> MOD711 from ScTec. >>>>>>>>>>>> But we are having a problem here that we can't figure out the >>>>>>>>>>>> solution. >>>>>>>>>>>> When we finish all the steps of the tutorial in the site, this >>>>>>>>>>>> error message appears: >>>>>>>>>>>> >>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>>>>> 09:00 CEST) >>>>>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open >>>>>>>>>>>> ftdi device: device not found >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Any idea how to fix it? >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> Teo >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Elua-dev mailing list >>>>>> Elua-dev at lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Elua-dev mailing list >>>>> Elua-dev at lists.berlios.de >>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Elua-dev mailing list >>>> Elua-dev at lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>> >>>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/3b65370d/attachment-0001.html |
|
|
:| Puzzled. That error shouldn't appear at all if you run "openocd" from the
directory in which "str7prg.cfg" exists. Try this: $ sudo chmod 666 /dev/parport0 Then simply: $ openocd -f str7prg.cfg (from the right directory). I'm running out of ideas ... On Wed, Oct 29, 2008 at 11:17 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST) > Error: configuration.c:121 parse_config_file(): couldn't open config file > > > On Wed, Oct 29, 2008 at 7:13 PM, Bogdan Marinescu < > bogdan.marinescu at gmail.com> wrote: > >> Weird. Try this: >> >> parport_port 0 >> >> instead of this: >> >> parport_port 0x378 >> >> in str7prg.cfg, and then >> >> $ sudo openocd -f str7prg.cfg >> >> On Wed, Oct 29, 2008 at 11:10 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >> >>> I'm sorry, I wasn't any clear. >>> When I do this ($ sudo openocd -f str7prg.cfg) the same error occours. No >>> matter what I try now, it happens... hehe >>> But if I do only "sudo openocd", that other error message shows up, but I >>> don't know if that means something. >>> >>> I'm trying to figure out how to set the right permission to parport0. >>> if I do "ls -l /dev/parport0" the terminal shows me: >>> crw-rw---- 1 lp scanner 99, 0 2008-10-14 15:39 /dev/parport0 >>> >>> I don't know right now what to do... >>> >>> >>> On Wed, Oct 29, 2008 at 7:02 PM, Bogdan Marinescu < >>> bogdan.marinescu at gmail.com> wrote: >>> >>>> I mean "sudo openocd" with the same "openocd" parameters you used >>>> before. Something like this: >>>> >>>> $ sudo openocd -f str7prg.cfg >>>> >>>> >>>> On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>>> >>>>> I did sudo openocd and an error message appeared. >>>>> >>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>> CEST) >>>>> Error: configuration.c:121 parse_config_file(): couldn't open config >>>>> file >>>>> >>>>> I'm not quite sure how to set the permission to parport0 properly. >>>>> >>>>> Thanks for the help >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < >>>>> bogdan.marinescu at gmail.com> wrote: >>>>> >>>>>> Then try setting the right permissions to /dev/parport0, or just sudo >>>>>> openocd ... I don't know, never tried Linux with this parport interface. >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin < >>>>>> teo.benjamin at gmail.com> wrote: >>>>>> >>>>>>> This is in Linux... >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>> >>>>>>>> This comes from Windows or Linux? In Windows, you need to use >>>>>>>> giveio. In Linux you should probably set the right permission to >>>>>>>> /dev/parport0. >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin < >>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>> >>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>> 09:00 CEST) >>>>>>>>> Error: parport.c:359 parport_init(): cannot open device. check it >>>>>>>>> exists and that user read and write rights are set >>>>>>>>> >>>>>>>>> I'll have a look on the link you sent... >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Well, my tutorial also says this (feels kinda strange quoting >>>>>>>>>> myself :) ): >>>>>>>>>> >>>>>>>>>> "The board comes with its own JTAG adadpter, but it uses a >>>>>>>>>> parallel interface, and since my computer doesn't have one, I used the >>>>>>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html> from >>>>>>>>>> Olimex" >>>>>>>>>> >>>>>>>>>> So you'll need to change your interface description. I think you >>>>>>>>>> should use this: >>>>>>>>>> >>>>>>>>>> #interface >>>>>>>>>> interface parport >>>>>>>>>> parport_port 0x378 >>>>>>>>>> parport_cable wiggler >>>>>>>>>> jtag_speed 0 >>>>>>>>>> >>>>>>>>>> instead of this: >>>>>>>>>> >>>>>>>>>> # JTAG interface >>>>>>>>>> interface ft2232 >>>>>>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>>>>>> ft2232_layout olimex-jtag >>>>>>>>>> jtag_speed 20 >>>>>>>>>> jtag_nsrst_delay 200 >>>>>>>>>> jtag_ntrst_delay 200 >>>>>>>>>> >>>>>>>>>> in the "str7prg.cfg" file. >>>>>>>>>> Change "0x378" to the correct value if you're not using LPT1. >>>>>>>>>> Also, see this thread for more details/troubleshooting data: >>>>>>>>>> >>>>>>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>>>>>> >>>>>>>>>> Good luck! >>>>>>>>>> >>>>>>>>>> Bogdan >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> The same we sent you last month... ;) >>>>>>>>>>> We tried this in Linux and this message appears. >>>>>>>>>>> >>>>>>>>>>> We tried in Windows and the message was this one: >>>>>>>>>>> >>>>>>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>>>>>> Info: options.c:50 configuration_output_handler(): couldn't >>>>>>>>>>> open script file >>>>>>>>>>> str7prg.cfg >>>>>>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has to >>>>>>>>>>> be specified, >>>>>>>>>>> see "interface" command >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Resending to list, as usual ... :) >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> What kind of JTAG adapter are you using? >>>>>>>>>>>> >>>>>>>>>>>> Bogdan >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hello eLua people. >>>>>>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in the >>>>>>>>>>>>> MOD711 from ScTec. >>>>>>>>>>>>> But we are having a problem here that we can't figure out the >>>>>>>>>>>>> solution. >>>>>>>>>>>>> When we finish all the steps of the tutorial in the site, this >>>>>>>>>>>>> error message appears: >>>>>>>>>>>>> >>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>>>>>> 09:00 CEST) >>>>>>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open >>>>>>>>>>>>> ftdi device: device not found >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Any idea how to fix it? >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks, >>>>>>>>>>>>> Teo >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Elua-dev mailing list >>>>>>> Elua-dev at lists.berlios.de >>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Elua-dev mailing list >>>>>> Elua-dev at lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Elua-dev mailing list >>>>> Elua-dev at lists.berlios.de >>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Elua-dev mailing list >>>> Elua-dev at lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>> >>>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/433e67c0/attachment.html |
|
|
Now I did "parport_port 0", the Terminal does absolutely nothing.
I do sudo openocd -f str7prg.cfg and the normal message appears: Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST) After that I keep waiting while nothing happens... The last error was my mistake. I'm sorry!!! What is happening is this now... But you should be very tired. It's time to sleep in Romania. Do not loose your sleep whith this! Thanks a lot! On Wed, Oct 29, 2008 at 7:23 PM, Bogdan Marinescu < bogdan.marinescu at gmail.com> wrote: > :| Puzzled. That error shouldn't appear at all if you run "openocd" from > the directory in which "str7prg.cfg" exists. Try this: > > $ sudo chmod 666 /dev/parport0 > > Then simply: > > $ openocd -f str7prg.cfg > > (from the right directory). > > I'm running out of ideas ... > > > On Wed, Oct 29, 2008 at 11:17 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > >> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >> CEST) >> Error: configuration.c:121 parse_config_file(): couldn't open config >> file >> >> >> On Wed, Oct 29, 2008 at 7:13 PM, Bogdan Marinescu < >> bogdan.marinescu at gmail.com> wrote: >> >>> Weird. Try this: >>> >>> parport_port 0 >>> >>> instead of this: >>> >>> parport_port 0x378 >>> >>> in str7prg.cfg, and then >>> >>> $ sudo openocd -f str7prg.cfg >>> >>> On Wed, Oct 29, 2008 at 11:10 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>> >>>> I'm sorry, I wasn't any clear. >>>> When I do this ($ sudo openocd -f str7prg.cfg) the same error occours. >>>> No matter what I try now, it happens... hehe >>>> But if I do only "sudo openocd", that other error message shows up, but >>>> I don't know if that means something. >>>> >>>> I'm trying to figure out how to set the right permission to parport0. >>>> if I do "ls -l /dev/parport0" the terminal shows me: >>>> crw-rw---- 1 lp scanner 99, 0 2008-10-14 15:39 /dev/parport0 >>>> >>>> I don't know right now what to do... >>>> >>>> >>>> On Wed, Oct 29, 2008 at 7:02 PM, Bogdan Marinescu < >>>> bogdan.marinescu at gmail.com> wrote: >>>> >>>>> I mean "sudo openocd" with the same "openocd" parameters you used >>>>> before. Something like this: >>>>> >>>>> $ sudo openocd -f str7prg.cfg >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin <teo.benjamin at gmail.com >>>>> > wrote: >>>>> >>>>>> I did sudo openocd and an error message appeared. >>>>>> >>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>>> CEST) >>>>>> Error: configuration.c:121 parse_config_file(): couldn't open config >>>>>> file >>>>>> >>>>>> I'm not quite sure how to set the permission to parport0 properly. >>>>>> >>>>>> Thanks for the help >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < >>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>> >>>>>>> Then try setting the right permissions to /dev/parport0, or just sudo >>>>>>> openocd ... I don't know, never tried Linux with this parport interface. >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin < >>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>> >>>>>>>> This is in Linux... >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>> >>>>>>>>> This comes from Windows or Linux? In Windows, you need to use >>>>>>>>> giveio. In Linux you should probably set the right permission to >>>>>>>>> /dev/parport0. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin < >>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>>> 09:00 CEST) >>>>>>>>>> Error: parport.c:359 parport_init(): cannot open device. check >>>>>>>>>> it exists and that user read and write rights are set >>>>>>>>>> >>>>>>>>>> I'll have a look on the link you sent... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Well, my tutorial also says this (feels kinda strange quoting >>>>>>>>>>> myself :) ): >>>>>>>>>>> >>>>>>>>>>> "The board comes with its own JTAG adadpter, but it uses a >>>>>>>>>>> parallel interface, and since my computer doesn't have one, I used the >>>>>>>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html> from >>>>>>>>>>> Olimex" >>>>>>>>>>> >>>>>>>>>>> So you'll need to change your interface description. I think you >>>>>>>>>>> should use this: >>>>>>>>>>> >>>>>>>>>>> #interface >>>>>>>>>>> interface parport >>>>>>>>>>> parport_port 0x378 >>>>>>>>>>> parport_cable wiggler >>>>>>>>>>> jtag_speed 0 >>>>>>>>>>> >>>>>>>>>>> instead of this: >>>>>>>>>>> >>>>>>>>>>> # JTAG interface >>>>>>>>>>> interface ft2232 >>>>>>>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>>>>>>> ft2232_layout olimex-jtag >>>>>>>>>>> jtag_speed 20 >>>>>>>>>>> jtag_nsrst_delay 200 >>>>>>>>>>> jtag_ntrst_delay 200 >>>>>>>>>>> >>>>>>>>>>> in the "str7prg.cfg" file. >>>>>>>>>>> Change "0x378" to the correct value if you're not using LPT1. >>>>>>>>>>> Also, see this thread for more details/troubleshooting data: >>>>>>>>>>> >>>>>>>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>>>>>>> >>>>>>>>>>> Good luck! >>>>>>>>>>> >>>>>>>>>>> Bogdan >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> The same we sent you last month... ;) >>>>>>>>>>>> We tried this in Linux and this message appears. >>>>>>>>>>>> >>>>>>>>>>>> We tried in Windows and the message was this one: >>>>>>>>>>>> >>>>>>>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>>>>>>> Info: options.c:50 configuration_output_handler(): couldn't >>>>>>>>>>>> open script file >>>>>>>>>>>> str7prg.cfg >>>>>>>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has >>>>>>>>>>>> to be specified, >>>>>>>>>>>> see "interface" command >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Resending to list, as usual ... :) >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Hi, >>>>>>>>>>>>> >>>>>>>>>>>>> What kind of JTAG adapter are you using? >>>>>>>>>>>>> >>>>>>>>>>>>> Bogdan >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hello eLua people. >>>>>>>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in the >>>>>>>>>>>>>> MOD711 from ScTec. >>>>>>>>>>>>>> But we are having a problem here that we can't figure out the >>>>>>>>>>>>>> solution. >>>>>>>>>>>>>> When we finish all the steps of the tutorial in the site, this >>>>>>>>>>>>>> error message appears: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger >>>>>>>>>>>>>> (2007-09-05 09:00 CEST) >>>>>>>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open >>>>>>>>>>>>>> ftdi device: device not found >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Any idea how to fix it? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>> Teo >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Elua-dev mailing list >>>>>>>> Elua-dev at lists.berlios.de >>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Elua-dev mailing list >>>>>>> Elua-dev at lists.berlios.de >>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Elua-dev mailing list >>>>>> Elua-dev at lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Elua-dev mailing list >>>>> Elua-dev at lists.berlios.de >>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Elua-dev mailing list >>>> Elua-dev at lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>> >>>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/c48b13eb/attachment-0001.html |
|
|
I'm not loosing my time, I just don't know what to do anymore. If you have
any kernel modules that are using the LPT port (such as printer drivers) try to unload them and then try with "openocd" again. "dmesg" might also help with some diagnostic messages in this situation. Try googling for something like "openocd lpt linux stuck" or "not working", you might find some useful threads. As a last resort, use a Windows system :) (in this case go back to parport_port 0x378 instead of parport_port 0, and also google for "giveio", you'll need it). I will go to sleep now, indeed :) Hope you'll be able to solve your problem soon. Ah, and one last thing ... the board is powered, right ? :) Best, Bogdan On Wed, Oct 29, 2008 at 11:36 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > Now I did "parport_port 0", the Terminal does absolutely nothing. > I do sudo openocd -f str7prg.cfg and the normal message appears: > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST) > > After that I keep waiting while nothing happens... > > The last error was my mistake. I'm sorry!!! > What is happening is this now... > > But you should be very tired. It's time to sleep in Romania. Do not loose > your sleep whith this! > Thanks a lot! > > > On Wed, Oct 29, 2008 at 7:23 PM, Bogdan Marinescu < > bogdan.marinescu at gmail.com> wrote: > >> :| Puzzled. That error shouldn't appear at all if you run "openocd" from >> the directory in which "str7prg.cfg" exists. Try this: >> >> $ sudo chmod 666 /dev/parport0 >> >> Then simply: >> >> $ openocd -f str7prg.cfg >> >> (from the right directory). >> >> I'm running out of ideas ... >> >> >> On Wed, Oct 29, 2008 at 11:17 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >> >>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>> CEST) >>> Error: configuration.c:121 parse_config_file(): couldn't open config >>> file >>> >>> >>> On Wed, Oct 29, 2008 at 7:13 PM, Bogdan Marinescu < >>> bogdan.marinescu at gmail.com> wrote: >>> >>>> Weird. Try this: >>>> >>>> parport_port 0 >>>> >>>> instead of this: >>>> >>>> parport_port 0x378 >>>> >>>> in str7prg.cfg, and then >>>> >>>> $ sudo openocd -f str7prg.cfg >>>> >>>> On Wed, Oct 29, 2008 at 11:10 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>>> >>>>> I'm sorry, I wasn't any clear. >>>>> When I do this ($ sudo openocd -f str7prg.cfg) the same error occours. >>>>> No matter what I try now, it happens... hehe >>>>> But if I do only "sudo openocd", that other error message shows up, but >>>>> I don't know if that means something. >>>>> >>>>> I'm trying to figure out how to set the right permission to parport0. >>>>> if I do "ls -l /dev/parport0" the terminal shows me: >>>>> crw-rw---- 1 lp scanner 99, 0 2008-10-14 15:39 /dev/parport0 >>>>> >>>>> I don't know right now what to do... >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 7:02 PM, Bogdan Marinescu < >>>>> bogdan.marinescu at gmail.com> wrote: >>>>> >>>>>> I mean "sudo openocd" with the same "openocd" parameters you used >>>>>> before. Something like this: >>>>>> >>>>>> $ sudo openocd -f str7prg.cfg >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin < >>>>>> teo.benjamin at gmail.com> wrote: >>>>>> >>>>>>> I did sudo openocd and an error message appeared. >>>>>>> >>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>>>> CEST) >>>>>>> Error: configuration.c:121 parse_config_file(): couldn't open >>>>>>> config file >>>>>>> >>>>>>> I'm not quite sure how to set the permission to parport0 properly. >>>>>>> >>>>>>> Thanks for the help >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < >>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>> >>>>>>>> Then try setting the right permissions to /dev/parport0, or just >>>>>>>> sudo openocd ... I don't know, never tried Linux with this parport >>>>>>>> interface. >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin < >>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>> >>>>>>>>> This is in Linux... >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> This comes from Windows or Linux? In Windows, you need to use >>>>>>>>>> giveio. In Linux you should probably set the right permission to >>>>>>>>>> /dev/parport0. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin < >>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>>>> 09:00 CEST) >>>>>>>>>>> Error: parport.c:359 parport_init(): cannot open device. check >>>>>>>>>>> it exists and that user read and write rights are set >>>>>>>>>>> >>>>>>>>>>> I'll have a look on the link you sent... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Well, my tutorial also says this (feels kinda strange quoting >>>>>>>>>>>> myself :) ): >>>>>>>>>>>> >>>>>>>>>>>> "The board comes with its own JTAG adadpter, but it uses a >>>>>>>>>>>> parallel interface, and since my computer doesn't have one, I used the >>>>>>>>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html> from >>>>>>>>>>>> Olimex" >>>>>>>>>>>> >>>>>>>>>>>> So you'll need to change your interface description. I think you >>>>>>>>>>>> should use this: >>>>>>>>>>>> >>>>>>>>>>>> #interface >>>>>>>>>>>> interface parport >>>>>>>>>>>> parport_port 0x378 >>>>>>>>>>>> parport_cable wiggler >>>>>>>>>>>> jtag_speed 0 >>>>>>>>>>>> >>>>>>>>>>>> instead of this: >>>>>>>>>>>> >>>>>>>>>>>> # JTAG interface >>>>>>>>>>>> interface ft2232 >>>>>>>>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>>>>>>>> ft2232_layout olimex-jtag >>>>>>>>>>>> jtag_speed 20 >>>>>>>>>>>> jtag_nsrst_delay 200 >>>>>>>>>>>> jtag_ntrst_delay 200 >>>>>>>>>>>> >>>>>>>>>>>> in the "str7prg.cfg" file. >>>>>>>>>>>> Change "0x378" to the correct value if you're not using LPT1. >>>>>>>>>>>> Also, see this thread for more details/troubleshooting data: >>>>>>>>>>>> >>>>>>>>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>>>>>>>> >>>>>>>>>>>> Good luck! >>>>>>>>>>>> >>>>>>>>>>>> Bogdan >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> The same we sent you last month... ;) >>>>>>>>>>>>> We tried this in Linux and this message appears. >>>>>>>>>>>>> >>>>>>>>>>>>> We tried in Windows and the message was this one: >>>>>>>>>>>>> >>>>>>>>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>>>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>>>>>>>> Info: options.c:50 configuration_output_handler(): couldn't >>>>>>>>>>>>> open script file >>>>>>>>>>>>> str7prg.cfg >>>>>>>>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has >>>>>>>>>>>>> to be specified, >>>>>>>>>>>>> see "interface" command >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Resending to list, as usual ... :) >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>> >>>>>>>>>>>>>> What kind of JTAG adapter are you using? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Bogdan >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hello eLua people. >>>>>>>>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in >>>>>>>>>>>>>>> the MOD711 from ScTec. >>>>>>>>>>>>>>> But we are having a problem here that we can't figure out the >>>>>>>>>>>>>>> solution. >>>>>>>>>>>>>>> When we finish all the steps of the tutorial in the site, >>>>>>>>>>>>>>> this error message appears: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger >>>>>>>>>>>>>>> (2007-09-05 09:00 CEST) >>>>>>>>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open >>>>>>>>>>>>>>> ftdi device: device not found >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Any idea how to fix it? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>> Teo >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Elua-dev mailing list >>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Elua-dev mailing list >>>>>>>> Elua-dev at lists.berlios.de >>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Elua-dev mailing list >>>>>>> Elua-dev at lists.berlios.de >>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Elua-dev mailing list >>>>>> Elua-dev at lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Elua-dev mailing list >>>>> Elua-dev at lists.berlios.de >>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Elua-dev mailing list >>>> Elua-dev at lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>> >>>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/4e520c7e/attachment.html |
|
|
Hahahahahahahaha!
After the 100th time, I had this fear... But it's powered, don't worry. hehehe I'll go home soon and probably work at this tomorow. Thanks for your help. It was really usefull. Teo On Wed, Oct 29, 2008 at 7:41 PM, Bogdan Marinescu < bogdan.marinescu at gmail.com> wrote: > I'm not loosing my time, I just don't know what to do anymore. If you have > any kernel modules that are using the LPT port (such as printer drivers) try > to unload them and then try with "openocd" again. "dmesg" might also help > with some diagnostic messages in this situation. Try googling for something > like "openocd lpt linux stuck" or "not working", you might find some useful > threads. As a last resort, use a Windows system :) (in this case go back to > parport_port 0x378 instead of parport_port 0, and also google for "giveio", > you'll need it). > I will go to sleep now, indeed :) Hope you'll be able to solve your problem > soon. > Ah, and one last thing ... the board is powered, right ? :) > > Best, > Bogdan > > > On Wed, Oct 29, 2008 at 11:36 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > >> Now I did "parport_port 0", the Terminal does absolutely nothing. >> I do sudo openocd -f str7prg.cfg and the normal message appears: >> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >> CEST) >> >> After that I keep waiting while nothing happens... >> >> The last error was my mistake. I'm sorry!!! >> What is happening is this now... >> >> But you should be very tired. It's time to sleep in Romania. Do not loose >> your sleep whith this! >> Thanks a lot! >> >> >> On Wed, Oct 29, 2008 at 7:23 PM, Bogdan Marinescu < >> bogdan.marinescu at gmail.com> wrote: >> >>> :| Puzzled. That error shouldn't appear at all if you run "openocd" from >>> the directory in which "str7prg.cfg" exists. Try this: >>> >>> $ sudo chmod 666 /dev/parport0 >>> >>> Then simply: >>> >>> $ openocd -f str7prg.cfg >>> >>> (from the right directory). >>> >>> I'm running out of ideas ... >>> >>> >>> On Wed, Oct 29, 2008 at 11:17 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>> >>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>> CEST) >>>> Error: configuration.c:121 parse_config_file(): couldn't open config >>>> file >>>> >>>> >>>> On Wed, Oct 29, 2008 at 7:13 PM, Bogdan Marinescu < >>>> bogdan.marinescu at gmail.com> wrote: >>>> >>>>> Weird. Try this: >>>>> >>>>> parport_port 0 >>>>> >>>>> instead of this: >>>>> >>>>> parport_port 0x378 >>>>> >>>>> in str7prg.cfg, and then >>>>> >>>>> $ sudo openocd -f str7prg.cfg >>>>> >>>>> On Wed, Oct 29, 2008 at 11:10 PM, T?o Benjamin <teo.benjamin at gmail.com >>>>> > wrote: >>>>> >>>>>> I'm sorry, I wasn't any clear. >>>>>> When I do this ($ sudo openocd -f str7prg.cfg) the same error occours. >>>>>> No matter what I try now, it happens... hehe >>>>>> But if I do only "sudo openocd", that other error message shows up, >>>>>> but I don't know if that means something. >>>>>> >>>>>> I'm trying to figure out how to set the right permission to parport0. >>>>>> if I do "ls -l /dev/parport0" the terminal shows me: >>>>>> crw-rw---- 1 lp scanner 99, 0 2008-10-14 15:39 /dev/parport0 >>>>>> >>>>>> I don't know right now what to do... >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 7:02 PM, Bogdan Marinescu < >>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>> >>>>>>> I mean "sudo openocd" with the same "openocd" parameters you used >>>>>>> before. Something like this: >>>>>>> >>>>>>> $ sudo openocd -f str7prg.cfg >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin < >>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>> >>>>>>>> I did sudo openocd and an error message appeared. >>>>>>>> >>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>> 09:00 CEST) >>>>>>>> Error: configuration.c:121 parse_config_file(): couldn't open >>>>>>>> config file >>>>>>>> >>>>>>>> I'm not quite sure how to set the permission to parport0 properly. >>>>>>>> >>>>>>>> Thanks for the help >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < >>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>> >>>>>>>>> Then try setting the right permissions to /dev/parport0, or just >>>>>>>>> sudo openocd ... I don't know, never tried Linux with this parport >>>>>>>>> interface. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin < >>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> This is in Linux... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> This comes from Windows or Linux? In Windows, you need to use >>>>>>>>>>> giveio. In Linux you should probably set the right permission to >>>>>>>>>>> /dev/parport0. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin < >>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>>>>> 09:00 CEST) >>>>>>>>>>>> Error: parport.c:359 parport_init(): cannot open device. check >>>>>>>>>>>> it exists and that user read and write rights are set >>>>>>>>>>>> >>>>>>>>>>>> I'll have a look on the link you sent... >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Well, my tutorial also says this (feels kinda strange quoting >>>>>>>>>>>>> myself :) ): >>>>>>>>>>>>> >>>>>>>>>>>>> "The board comes with its own JTAG adadpter, but it uses a >>>>>>>>>>>>> parallel interface, and since my computer doesn't have one, I used the >>>>>>>>>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html>from Olimex" >>>>>>>>>>>>> >>>>>>>>>>>>> So you'll need to change your interface description. I think >>>>>>>>>>>>> you should use this: >>>>>>>>>>>>> >>>>>>>>>>>>> #interface >>>>>>>>>>>>> interface parport >>>>>>>>>>>>> parport_port 0x378 >>>>>>>>>>>>> parport_cable wiggler >>>>>>>>>>>>> jtag_speed 0 >>>>>>>>>>>>> >>>>>>>>>>>>> instead of this: >>>>>>>>>>>>> >>>>>>>>>>>>> # JTAG interface >>>>>>>>>>>>> interface ft2232 >>>>>>>>>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>>>>>>>>> ft2232_layout olimex-jtag >>>>>>>>>>>>> jtag_speed 20 >>>>>>>>>>>>> jtag_nsrst_delay 200 >>>>>>>>>>>>> jtag_ntrst_delay 200 >>>>>>>>>>>>> >>>>>>>>>>>>> in the "str7prg.cfg" file. >>>>>>>>>>>>> Change "0x378" to the correct value if you're not using LPT1. >>>>>>>>>>>>> Also, see this thread for more details/troubleshooting data: >>>>>>>>>>>>> >>>>>>>>>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>>>>>>>>> >>>>>>>>>>>>> Good luck! >>>>>>>>>>>>> >>>>>>>>>>>>> Bogdan >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> The same we sent you last month... ;) >>>>>>>>>>>>>> We tried this in Linux and this message appears. >>>>>>>>>>>>>> >>>>>>>>>>>>>> We tried in Windows and the message was this one: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>>>>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>>>>>>>>> Info: options.c:50 configuration_output_handler(): >>>>>>>>>>>>>> couldn't open script file >>>>>>>>>>>>>> str7prg.cfg >>>>>>>>>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface has >>>>>>>>>>>>>> to be specified, >>>>>>>>>>>>>> see "interface" command >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Resending to list, as usual ... :) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>>>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>>>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>>>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> What kind of JTAG adapter are you using? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Bogdan >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hello eLua people. >>>>>>>>>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in >>>>>>>>>>>>>>>> the MOD711 from ScTec. >>>>>>>>>>>>>>>> But we are having a problem here that we can't figure out >>>>>>>>>>>>>>>> the solution. >>>>>>>>>>>>>>>> When we finish all the steps of the tutorial in the site, >>>>>>>>>>>>>>>> this error message appears: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger >>>>>>>>>>>>>>>> (2007-09-05 09:00 CEST) >>>>>>>>>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to open >>>>>>>>>>>>>>>> ftdi device: device not found >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Any idea how to fix it? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>> Teo >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Elua-dev mailing list >>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Elua-dev mailing list >>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Elua-dev mailing list >>>>>>>> Elua-dev at lists.berlios.de >>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Elua-dev mailing list >>>>>>> Elua-dev at lists.berlios.de >>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Elua-dev mailing list >>>>>> Elua-dev at lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Elua-dev mailing list >>>>> Elua-dev at lists.berlios.de >>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Elua-dev mailing list >>>> Elua-dev at lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>> >>>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081029/0c83e6ba/attachment-0001.html |
|
|
Back at work.
A bigger team now! On Wed, Oct 29, 2008 at 6:45 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > Hahahahahahahaha! > After the 100th time, I had this fear... But it's powered, don't worry. > hehehe > I'll go home soon and probably work at this tomorow. > Thanks for your help. It was really usefull. > > Teo > > > On Wed, Oct 29, 2008 at 7:41 PM, Bogdan Marinescu < > bogdan.marinescu at gmail.com> wrote: > >> I'm not loosing my time, I just don't know what to do anymore. If you have >> any kernel modules that are using the LPT port (such as printer drivers) try >> to unload them and then try with "openocd" again. "dmesg" might also help >> with some diagnostic messages in this situation. Try googling for something >> like "openocd lpt linux stuck" or "not working", you might find some useful >> threads. As a last resort, use a Windows system :) (in this case go back to >> parport_port 0x378 instead of parport_port 0, and also google for "giveio", >> you'll need it). >> I will go to sleep now, indeed :) Hope you'll be able to solve your >> problem soon. >> Ah, and one last thing ... the board is powered, right ? :) >> >> Best, >> Bogdan >> >> >> On Wed, Oct 29, 2008 at 11:36 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >> >>> Now I did "parport_port 0", the Terminal does absolutely nothing. >>> I do sudo openocd -f str7prg.cfg and the normal message appears: >>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>> CEST) >>> >>> After that I keep waiting while nothing happens... >>> >>> The last error was my mistake. I'm sorry!!! >>> What is happening is this now... >>> >>> But you should be very tired. It's time to sleep in Romania. Do not loose >>> your sleep whith this! >>> Thanks a lot! >>> >>> >>> On Wed, Oct 29, 2008 at 7:23 PM, Bogdan Marinescu < >>> bogdan.marinescu at gmail.com> wrote: >>> >>>> :| Puzzled. That error shouldn't appear at all if you run "openocd" from >>>> the directory in which "str7prg.cfg" exists. Try this: >>>> >>>> $ sudo chmod 666 /dev/parport0 >>>> >>>> Then simply: >>>> >>>> $ openocd -f str7prg.cfg >>>> >>>> (from the right directory). >>>> >>>> I'm running out of ideas ... >>>> >>>> >>>> On Wed, Oct 29, 2008 at 11:17 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>>> >>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>> CEST) >>>>> Error: configuration.c:121 parse_config_file(): couldn't open config >>>>> file >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 7:13 PM, Bogdan Marinescu < >>>>> bogdan.marinescu at gmail.com> wrote: >>>>> >>>>>> Weird. Try this: >>>>>> >>>>>> parport_port 0 >>>>>> >>>>>> instead of this: >>>>>> >>>>>> parport_port 0x378 >>>>>> >>>>>> in str7prg.cfg, and then >>>>>> >>>>>> $ sudo openocd -f str7prg.cfg >>>>>> >>>>>> On Wed, Oct 29, 2008 at 11:10 PM, T?o Benjamin < >>>>>> teo.benjamin at gmail.com> wrote: >>>>>> >>>>>>> I'm sorry, I wasn't any clear. >>>>>>> When I do this ($ sudo openocd -f str7prg.cfg) the same error >>>>>>> occours. No matter what I try now, it happens... hehe >>>>>>> But if I do only "sudo openocd", that other error message shows up, >>>>>>> but I don't know if that means something. >>>>>>> >>>>>>> I'm trying to figure out how to set the right permission to parport0. >>>>>>> if I do "ls -l /dev/parport0" the terminal shows me: >>>>>>> crw-rw---- 1 lp scanner 99, 0 2008-10-14 15:39 /dev/parport0 >>>>>>> >>>>>>> I don't know right now what to do... >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 7:02 PM, Bogdan Marinescu < >>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>> >>>>>>>> I mean "sudo openocd" with the same "openocd" parameters you used >>>>>>>> before. Something like this: >>>>>>>> >>>>>>>> $ sudo openocd -f str7prg.cfg >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin < >>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>> >>>>>>>>> I did sudo openocd and an error message appeared. >>>>>>>>> >>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>> 09:00 CEST) >>>>>>>>> Error: configuration.c:121 parse_config_file(): couldn't open >>>>>>>>> config file >>>>>>>>> >>>>>>>>> I'm not quite sure how to set the permission to parport0 properly. >>>>>>>>> >>>>>>>>> Thanks for the help >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < >>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Then try setting the right permissions to /dev/parport0, or just >>>>>>>>>> sudo openocd ... I don't know, never tried Linux with this parport >>>>>>>>>> interface. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin < >>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> This is in Linux... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> This comes from Windows or Linux? In Windows, you need to use >>>>>>>>>>>> giveio. In Linux you should probably set the right permission to >>>>>>>>>>>> /dev/parport0. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin < >>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>>>>>> 09:00 CEST) >>>>>>>>>>>>> Error: parport.c:359 parport_init(): cannot open device. >>>>>>>>>>>>> check it exists and that user read and write rights are set >>>>>>>>>>>>> >>>>>>>>>>>>> I'll have a look on the link you sent... >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Well, my tutorial also says this (feels kinda strange quoting >>>>>>>>>>>>>> myself :) ): >>>>>>>>>>>>>> >>>>>>>>>>>>>> "The board comes with its own JTAG adadpter, but it uses a >>>>>>>>>>>>>> parallel interface, and since my computer doesn't have one, I used the >>>>>>>>>>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html>from Olimex" >>>>>>>>>>>>>> >>>>>>>>>>>>>> So you'll need to change your interface description. I think >>>>>>>>>>>>>> you should use this: >>>>>>>>>>>>>> >>>>>>>>>>>>>> #interface >>>>>>>>>>>>>> interface parport >>>>>>>>>>>>>> parport_port 0x378 >>>>>>>>>>>>>> parport_cable wiggler >>>>>>>>>>>>>> jtag_speed 0 >>>>>>>>>>>>>> >>>>>>>>>>>>>> instead of this: >>>>>>>>>>>>>> >>>>>>>>>>>>>> # JTAG interface >>>>>>>>>>>>>> interface ft2232 >>>>>>>>>>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>>>>>>>>>> ft2232_layout olimex-jtag >>>>>>>>>>>>>> jtag_speed 20 >>>>>>>>>>>>>> jtag_nsrst_delay 200 >>>>>>>>>>>>>> jtag_ntrst_delay 200 >>>>>>>>>>>>>> >>>>>>>>>>>>>> in the "str7prg.cfg" file. >>>>>>>>>>>>>> Change "0x378" to the correct value if you're not using LPT1. >>>>>>>>>>>>>> Also, see this thread for more details/troubleshooting data: >>>>>>>>>>>>>> >>>>>>>>>>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>>>>>>>>>> >>>>>>>>>>>>>> Good luck! >>>>>>>>>>>>>> >>>>>>>>>>>>>> Bogdan >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> The same we sent you last month... ;) >>>>>>>>>>>>>>> We tried this in Linux and this message appears. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> We tried in Windows and the message was this one: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>>>>>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>>>>>>>>>> Info: options.c:50 configuration_output_handler(): >>>>>>>>>>>>>>> couldn't open script file >>>>>>>>>>>>>>> str7prg.cfg >>>>>>>>>>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface >>>>>>>>>>>>>>> has to be specified, >>>>>>>>>>>>>>> see "interface" command >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Resending to list, as usual ... :) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>>>>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>>>>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>>>>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> What kind of JTAG adapter are you using? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Bogdan >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hello eLua people. >>>>>>>>>>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in >>>>>>>>>>>>>>>>> the MOD711 from ScTec. >>>>>>>>>>>>>>>>> But we are having a problem here that we can't figure out >>>>>>>>>>>>>>>>> the solution. >>>>>>>>>>>>>>>>> When we finish all the steps of the tutorial in the site, >>>>>>>>>>>>>>>>> this error message appears: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger >>>>>>>>>>>>>>>>> (2007-09-05 09:00 CEST) >>>>>>>>>>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to >>>>>>>>>>>>>>>>> open ftdi device: device not found >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Any idea how to fix it? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>> Teo >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Elua-dev mailing list >>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Elua-dev mailing list >>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Elua-dev mailing list >>>>>>>> Elua-dev at lists.berlios.de >>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Elua-dev mailing list >>>>>>> Elua-dev at lists.berlios.de >>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Elua-dev mailing list >>>>>> Elua-dev at lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Elua-dev mailing list >>>>> Elua-dev at lists.berlios.de >>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Elua-dev mailing list >>>> Elua-dev at lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>> >>>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081031/8dc9237f/attachment-0001.html |
|
|
We now tried from a root shell (with su -), here's what is says:
root at feynman:/home/labmar/Desktop/STR7# openocd -f str7prg.cfg Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST) Warning: arm7_9_common.c:734 arm7_9_assert_reset(): srst resets test logic, too *#(stops here for a while)* Error: target_request.c:127 target_request(): unknown target request: 0f Error: target_request.c:127 target_request(): unknown target request: 0f Error: target_request.c:127 target_request(): unknown target request: 0f Error: target_request.c:127 target_request(): unknown target request: 0f Error: target_request.c:127 target_request(): unknown target request: 0f Error: target_request.c:127 target_request(): unknown target request: 0f Error: target_request.c:127 target_request(): unknown target request: 0f Error: target_request.c:127 target_request(): unknown target request: 0f Info: target.c:233 target_init_handler(): executing reset script 'str7_flashprogram.script' Info: configuration.c:50 configuration_output_handler(): dcc downloads are enabled Info: configuration.c:50 configuration_output_handler(): waiting for target halted... Info: configuration.c:50 configuration_output_handler(): timed out while waiting for target halt Error: target.c:1388 handle_wait_halt_command(): timed out while waiting for target halt Info: configuration.c:50 configuration_output_handler(): can't work with this flash while target is running Info: configuration.c:50 configuration_output_handler(): Command erase_sector not found Info: configuration.c:50 configuration_output_handler(): Command write_bank not found Warning: arm7_9_common.c:745 arm7_9_assert_reset(): srst resets test logic, too 2008/10/31 T?o Benjamin <teo.benjamin at gmail.com> > Back at work. > A bigger team now! > > > On Wed, Oct 29, 2008 at 6:45 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: > >> Hahahahahahahaha! >> After the 100th time, I had this fear... But it's powered, don't worry. >> hehehe >> I'll go home soon and probably work at this tomorow. >> Thanks for your help. It was really usefull. >> >> Teo >> >> >> On Wed, Oct 29, 2008 at 7:41 PM, Bogdan Marinescu < >> bogdan.marinescu at gmail.com> wrote: >> >>> I'm not loosing my time, I just don't know what to do anymore. If you >>> have any kernel modules that are using the LPT port (such as printer >>> drivers) try to unload them and then try with "openocd" again. "dmesg" might >>> also help with some diagnostic messages in this situation. Try googling for >>> something like "openocd lpt linux stuck" or "not working", you might find >>> some useful threads. As a last resort, use a Windows system :) (in this case >>> go back to parport_port 0x378 instead of parport_port 0, and also google for >>> "giveio", you'll need it). >>> I will go to sleep now, indeed :) Hope you'll be able to solve your >>> problem soon. >>> Ah, and one last thing ... the board is powered, right ? :) >>> >>> Best, >>> Bogdan >>> >>> >>> On Wed, Oct 29, 2008 at 11:36 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>> >>>> Now I did "parport_port 0", the Terminal does absolutely nothing. >>>> I do sudo openocd -f str7prg.cfg and the normal message appears: >>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>> CEST) >>>> >>>> After that I keep waiting while nothing happens... >>>> >>>> The last error was my mistake. I'm sorry!!! >>>> What is happening is this now... >>>> >>>> But you should be very tired. It's time to sleep in Romania. Do not >>>> loose your sleep whith this! >>>> Thanks a lot! >>>> >>>> >>>> On Wed, Oct 29, 2008 at 7:23 PM, Bogdan Marinescu < >>>> bogdan.marinescu at gmail.com> wrote: >>>> >>>>> :| Puzzled. That error shouldn't appear at all if you run "openocd" >>>>> from the directory in which "str7prg.cfg" exists. Try this: >>>>> >>>>> $ sudo chmod 666 /dev/parport0 >>>>> >>>>> Then simply: >>>>> >>>>> $ openocd -f str7prg.cfg >>>>> >>>>> (from the right directory). >>>>> >>>>> I'm running out of ideas ... >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 11:17 PM, T?o Benjamin <teo.benjamin at gmail.com >>>>> > wrote: >>>>> >>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>>> CEST) >>>>>> Error: configuration.c:121 parse_config_file(): couldn't open config >>>>>> file >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 7:13 PM, Bogdan Marinescu < >>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>> >>>>>>> Weird. Try this: >>>>>>> >>>>>>> parport_port 0 >>>>>>> >>>>>>> instead of this: >>>>>>> >>>>>>> parport_port 0x378 >>>>>>> >>>>>>> in str7prg.cfg, and then >>>>>>> >>>>>>> $ sudo openocd -f str7prg.cfg >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 11:10 PM, T?o Benjamin < >>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>> >>>>>>>> I'm sorry, I wasn't any clear. >>>>>>>> When I do this ($ sudo openocd -f str7prg.cfg) the same error >>>>>>>> occours. No matter what I try now, it happens... hehe >>>>>>>> But if I do only "sudo openocd", that other error message shows up, >>>>>>>> but I don't know if that means something. >>>>>>>> >>>>>>>> I'm trying to figure out how to set the right permission to >>>>>>>> parport0. >>>>>>>> if I do "ls -l /dev/parport0" the terminal shows me: >>>>>>>> crw-rw---- 1 lp scanner 99, 0 2008-10-14 15:39 /dev/parport0 >>>>>>>> >>>>>>>> I don't know right now what to do... >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 7:02 PM, Bogdan Marinescu < >>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>> >>>>>>>>> I mean "sudo openocd" with the same "openocd" parameters you used >>>>>>>>> before. Something like this: >>>>>>>>> >>>>>>>>> $ sudo openocd -f str7prg.cfg >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin < >>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> I did sudo openocd and an error message appeared. >>>>>>>>>> >>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>>> 09:00 CEST) >>>>>>>>>> Error: configuration.c:121 parse_config_file(): couldn't open >>>>>>>>>> config file >>>>>>>>>> >>>>>>>>>> I'm not quite sure how to set the permission to parport0 properly. >>>>>>>>>> >>>>>>>>>> Thanks for the help >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < >>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Then try setting the right permissions to /dev/parport0, or just >>>>>>>>>>> sudo openocd ... I don't know, never tried Linux with this parport >>>>>>>>>>> interface. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin < >>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> This is in Linux... >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> This comes from Windows or Linux? In Windows, you need to use >>>>>>>>>>>>> giveio. In Linux you should probably set the right permission to >>>>>>>>>>>>> /dev/parport0. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin < >>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger >>>>>>>>>>>>>> (2007-09-05 09:00 CEST) >>>>>>>>>>>>>> Error: parport.c:359 parport_init(): cannot open device. >>>>>>>>>>>>>> check it exists and that user read and write rights are set >>>>>>>>>>>>>> >>>>>>>>>>>>>> I'll have a look on the link you sent... >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Well, my tutorial also says this (feels kinda strange quoting >>>>>>>>>>>>>>> myself :) ): >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> "The board comes with its own JTAG adadpter, but it uses a >>>>>>>>>>>>>>> parallel interface, and since my computer doesn't have one, I used the >>>>>>>>>>>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html>from Olimex" >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> So you'll need to change your interface description. I think >>>>>>>>>>>>>>> you should use this: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> #interface >>>>>>>>>>>>>>> interface parport >>>>>>>>>>>>>>> parport_port 0x378 >>>>>>>>>>>>>>> parport_cable wiggler >>>>>>>>>>>>>>> jtag_speed 0 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> instead of this: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> # JTAG interface >>>>>>>>>>>>>>> interface ft2232 >>>>>>>>>>>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>>>>>>>>>>> ft2232_layout olimex-jtag >>>>>>>>>>>>>>> jtag_speed 20 >>>>>>>>>>>>>>> jtag_nsrst_delay 200 >>>>>>>>>>>>>>> jtag_ntrst_delay 200 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> in the "str7prg.cfg" file. >>>>>>>>>>>>>>> Change "0x378" to the correct value if you're not using LPT1. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Also, see this thread for more details/troubleshooting data: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Good luck! >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Bogdan >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The same we sent you last month... ;) >>>>>>>>>>>>>>>> We tried this in Linux and this message appears. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> We tried in Windows and the message was this one: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>>>>>>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>>>>>>>>>>> Info: options.c:50 configuration_output_handler(): >>>>>>>>>>>>>>>> couldn't open script file >>>>>>>>>>>>>>>> str7prg.cfg >>>>>>>>>>>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface >>>>>>>>>>>>>>>> has to be specified, >>>>>>>>>>>>>>>> see "interface" command >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Resending to list, as usual ... :) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>>>>>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>>>>>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>>>>>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> What kind of JTAG adapter are you using? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Bogdan >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hello eLua people. >>>>>>>>>>>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image in >>>>>>>>>>>>>>>>>> the MOD711 from ScTec. >>>>>>>>>>>>>>>>>> But we are having a problem here that we can't figure out >>>>>>>>>>>>>>>>>> the solution. >>>>>>>>>>>>>>>>>> When we finish all the steps of the tutorial in the site, >>>>>>>>>>>>>>>>>> this error message appears: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger >>>>>>>>>>>>>>>>>> (2007-09-05 09:00 CEST) >>>>>>>>>>>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to >>>>>>>>>>>>>>>>>> open ftdi device: device not found >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Any idea how to fix it? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>> Teo >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Elua-dev mailing list >>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Elua-dev mailing list >>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Elua-dev mailing list >>>>>>>> Elua-dev at lists.berlios.de >>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Elua-dev mailing list >>>>>>> Elua-dev at lists.berlios.de >>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Elua-dev mailing list >>>>>> Elua-dev at lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Elua-dev mailing list >>>>> Elua-dev at lists.berlios.de >>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Elua-dev mailing list >>>> Elua-dev at lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>> >>>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081031/67cc8553/attachment-0001.html |
|
|
I'm sorry, my experience with OpenOCD is very limited, and I have no idea
what these errors are. Some ideas: 1. ask on the OpenOCD mailing list. In my experience though, their mailing list is far from being "friendly" to users, as it's targeted mainly to developers. You might be luckier than me though :) 2. find a Windows XP somewhere, and try from there (I'm going to try this myself (with the JTAG port supplied in the MOD711 package) as soon as I can). 3. download the OpenOCD sources, and try to understand the errors. What's in "target_request.c:127" ? Best, Bogdan On Fri, Oct 31, 2008 at 5:02 PM, Caio Percia Mehlem <caioxmag at gmail.com>wrote: > We now tried from a root shell (with su -), here's what is says: > > root at feynman:/home/labmar/Desktop/STR7# openocd -f str7prg.cfg > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST) > Warning: arm7_9_common.c:734 arm7_9_assert_reset(): srst resets test logic, > too > *#(stops here for a while)* > Error: target_request.c:127 target_request(): unknown target request: 0f > Error: target_request.c:127 target_request(): unknown target request: 0f > Error: target_request.c:127 target_request(): unknown target request: 0f > Error: target_request.c:127 target_request(): unknown target request: 0f > Error: target_request.c:127 target_request(): unknown target request: 0f > Error: target_request.c:127 target_request(): unknown target request: 0f > Error: target_request.c:127 target_request(): unknown target request: 0f > Error: target_request.c:127 target_request(): unknown target request: 0f > Info: target.c:233 target_init_handler(): executing reset script > 'str7_flashprogram.script' > Info: configuration.c:50 configuration_output_handler(): dcc downloads > are enabled > Info: configuration.c:50 configuration_output_handler(): waiting for > target halted... > Info: configuration.c:50 configuration_output_handler(): timed out while > waiting for target halt > Error: target.c:1388 handle_wait_halt_command(): timed out while waiting > for target halt > Info: configuration.c:50 configuration_output_handler(): can't work with > this flash while target is running > Info: configuration.c:50 configuration_output_handler(): Command > erase_sector not found > Info: configuration.c:50 configuration_output_handler(): Command > write_bank not found > Warning: arm7_9_common.c:745 arm7_9_assert_reset(): srst resets test logic, > too > > > 2008/10/31 T?o Benjamin <teo.benjamin at gmail.com> > > Back at work. >> A bigger team now! >> >> >> On Wed, Oct 29, 2008 at 6:45 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >> >>> Hahahahahahahaha! >>> After the 100th time, I had this fear... But it's powered, don't worry. >>> hehehe >>> I'll go home soon and probably work at this tomorow. >>> Thanks for your help. It was really usefull. >>> >>> Teo >>> >>> >>> On Wed, Oct 29, 2008 at 7:41 PM, Bogdan Marinescu < >>> bogdan.marinescu at gmail.com> wrote: >>> >>>> I'm not loosing my time, I just don't know what to do anymore. If you >>>> have any kernel modules that are using the LPT port (such as printer >>>> drivers) try to unload them and then try with "openocd" again. "dmesg" might >>>> also help with some diagnostic messages in this situation. Try googling for >>>> something like "openocd lpt linux stuck" or "not working", you might find >>>> some useful threads. As a last resort, use a Windows system :) (in this case >>>> go back to parport_port 0x378 instead of parport_port 0, and also google for >>>> "giveio", you'll need it). >>>> I will go to sleep now, indeed :) Hope you'll be able to solve your >>>> problem soon. >>>> Ah, and one last thing ... the board is powered, right ? :) >>>> >>>> Best, >>>> Bogdan >>>> >>>> >>>> On Wed, Oct 29, 2008 at 11:36 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>>> >>>>> Now I did "parport_port 0", the Terminal does absolutely nothing. >>>>> I do sudo openocd -f str7prg.cfg and the normal message appears: >>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>> CEST) >>>>> >>>>> After that I keep waiting while nothing happens... >>>>> >>>>> The last error was my mistake. I'm sorry!!! >>>>> What is happening is this now... >>>>> >>>>> But you should be very tired. It's time to sleep in Romania. Do not >>>>> loose your sleep whith this! >>>>> Thanks a lot! >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 7:23 PM, Bogdan Marinescu < >>>>> bogdan.marinescu at gmail.com> wrote: >>>>> >>>>>> :| Puzzled. That error shouldn't appear at all if you run "openocd" >>>>>> from the directory in which "str7prg.cfg" exists. Try this: >>>>>> >>>>>> $ sudo chmod 666 /dev/parport0 >>>>>> >>>>>> Then simply: >>>>>> >>>>>> $ openocd -f str7prg.cfg >>>>>> >>>>>> (from the right directory). >>>>>> >>>>>> I'm running out of ideas ... >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 11:17 PM, T?o Benjamin < >>>>>> teo.benjamin at gmail.com> wrote: >>>>>> >>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>>>> CEST) >>>>>>> Error: configuration.c:121 parse_config_file(): couldn't open >>>>>>> config file >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 7:13 PM, Bogdan Marinescu < >>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>> >>>>>>>> Weird. Try this: >>>>>>>> >>>>>>>> parport_port 0 >>>>>>>> >>>>>>>> instead of this: >>>>>>>> >>>>>>>> parport_port 0x378 >>>>>>>> >>>>>>>> in str7prg.cfg, and then >>>>>>>> >>>>>>>> $ sudo openocd -f str7prg.cfg >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 11:10 PM, T?o Benjamin < >>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>> >>>>>>>>> I'm sorry, I wasn't any clear. >>>>>>>>> When I do this ($ sudo openocd -f str7prg.cfg) the same error >>>>>>>>> occours. No matter what I try now, it happens... hehe >>>>>>>>> But if I do only "sudo openocd", that other error message shows up, >>>>>>>>> but I don't know if that means something. >>>>>>>>> >>>>>>>>> I'm trying to figure out how to set the right permission to >>>>>>>>> parport0. >>>>>>>>> if I do "ls -l /dev/parport0" the terminal shows me: >>>>>>>>> crw-rw---- 1 lp scanner 99, 0 2008-10-14 15:39 /dev/parport0 >>>>>>>>> >>>>>>>>> I don't know right now what to do... >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2008 at 7:02 PM, Bogdan Marinescu < >>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> I mean "sudo openocd" with the same "openocd" parameters you used >>>>>>>>>> before. Something like this: >>>>>>>>>> >>>>>>>>>> $ sudo openocd -f str7prg.cfg >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin < >>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> I did sudo openocd and an error message appeared. >>>>>>>>>>> >>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>>>> 09:00 CEST) >>>>>>>>>>> Error: configuration.c:121 parse_config_file(): couldn't open >>>>>>>>>>> config file >>>>>>>>>>> >>>>>>>>>>> I'm not quite sure how to set the permission to parport0 >>>>>>>>>>> properly. >>>>>>>>>>> >>>>>>>>>>> Thanks for the help >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < >>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Then try setting the right permissions to /dev/parport0, or just >>>>>>>>>>>> sudo openocd ... I don't know, never tried Linux with this parport >>>>>>>>>>>> interface. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin < >>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> This is in Linux... >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> This comes from Windows or Linux? In Windows, you need to use >>>>>>>>>>>>>> giveio. In Linux you should probably set the right permission to >>>>>>>>>>>>>> /dev/parport0. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin < >>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger >>>>>>>>>>>>>>> (2007-09-05 09:00 CEST) >>>>>>>>>>>>>>> Error: parport.c:359 parport_init(): cannot open device. >>>>>>>>>>>>>>> check it exists and that user read and write rights are set >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I'll have a look on the link you sent... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Well, my tutorial also says this (feels kinda strange >>>>>>>>>>>>>>>> quoting myself :) ): >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> "The board comes with its own JTAG adadpter, but it uses a >>>>>>>>>>>>>>>> parallel interface, and since my computer doesn't have one, I used the >>>>>>>>>>>>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html>from Olimex" >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> So you'll need to change your interface description. I think >>>>>>>>>>>>>>>> you should use this: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> #interface >>>>>>>>>>>>>>>> interface parport >>>>>>>>>>>>>>>> parport_port 0x378 >>>>>>>>>>>>>>>> parport_cable wiggler >>>>>>>>>>>>>>>> jtag_speed 0 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> instead of this: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> # JTAG interface >>>>>>>>>>>>>>>> interface ft2232 >>>>>>>>>>>>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>>>>>>>>>>>> ft2232_layout olimex-jtag >>>>>>>>>>>>>>>> jtag_speed 20 >>>>>>>>>>>>>>>> jtag_nsrst_delay 200 >>>>>>>>>>>>>>>> jtag_ntrst_delay 200 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> in the "str7prg.cfg" file. >>>>>>>>>>>>>>>> Change "0x378" to the correct value if you're not using >>>>>>>>>>>>>>>> LPT1. >>>>>>>>>>>>>>>> Also, see this thread for more details/troubleshooting data: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Good luck! >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Bogdan >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> The same we sent you last month... ;) >>>>>>>>>>>>>>>>> We tried this in Linux and this message appears. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> We tried in Windows and the message was this one: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>>>>>>>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>>>>>>>>>>>> Info: options.c:50 configuration_output_handler(): >>>>>>>>>>>>>>>>> couldn't open script file >>>>>>>>>>>>>>>>> str7prg.cfg >>>>>>>>>>>>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface >>>>>>>>>>>>>>>>> has to be specified, >>>>>>>>>>>>>>>>> see "interface" command >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Resending to list, as usual ... :) >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>>>>>>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>>>>>>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>>>>>>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> What kind of JTAG adapter are you using? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Bogdan >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hello eLua people. >>>>>>>>>>>>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image >>>>>>>>>>>>>>>>>>> in the MOD711 from ScTec. >>>>>>>>>>>>>>>>>>> But we are having a problem here that we can't figure out >>>>>>>>>>>>>>>>>>> the solution. >>>>>>>>>>>>>>>>>>> When we finish all the steps of the tutorial in the site, >>>>>>>>>>>>>>>>>>> this error message appears: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger >>>>>>>>>>>>>>>>>>> (2007-09-05 09:00 CEST) >>>>>>>>>>>>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to >>>>>>>>>>>>>>>>>>> open ftdi device: device not found >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Any idea how to fix it? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>>> Teo >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Elua-dev mailing list >>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Elua-dev mailing list >>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Elua-dev mailing list >>>>>>>> Elua-dev at lists.berlios.de >>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Elua-dev mailing list >>>>>>> Elua-dev at lists.berlios.de >>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Elua-dev mailing list >>>>>> Elua-dev at lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Elua-dev mailing list >>>>> Elua-dev at lists.berlios.de >>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Elua-dev mailing list >>>> Elua-dev at lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>> >>>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081031/c638b23c/attachment-0001.html |
|
|
We tried some other programs too, but they only work on USB.
We will try this on Windows now (the other computer, in the same table, is Windows). I'll tell the news. Thanks On Fri, Oct 31, 2008 at 1:06 PM, Bogdan Marinescu < bogdan.marinescu at gmail.com> wrote: > I'm sorry, my experience with OpenOCD is very limited, and I have no idea > what these errors are. Some ideas: > > 1. ask on the OpenOCD mailing list. In my experience though, their mailing > list is far from being "friendly" to users, as it's targeted mainly to > developers. You might be luckier than me though :) > 2. find a Windows XP somewhere, and try from there (I'm going to try this > myself (with the JTAG port supplied in the MOD711 package) as soon as I > can). > 3. download the OpenOCD sources, and try to understand the errors. What's > in "target_request.c:127" ? > > Best, > Bogdan > > > On Fri, Oct 31, 2008 at 5:02 PM, Caio Percia Mehlem <caioxmag at gmail.com>wrote: > >> We now tried from a root shell (with su -), here's what is says: >> >> root at feynman:/home/labmar/Desktop/STR7# openocd -f str7prg.cfg >> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >> CEST) >> Warning: arm7_9_common.c:734 arm7_9_assert_reset(): srst resets test >> logic, too >> *#(stops here for a while)* >> Error: target_request.c:127 target_request(): unknown target request: 0f >> Error: target_request.c:127 target_request(): unknown target request: 0f >> Error: target_request.c:127 target_request(): unknown target request: 0f >> Error: target_request.c:127 target_request(): unknown target request: 0f >> Error: target_request.c:127 target_request(): unknown target request: 0f >> Error: target_request.c:127 target_request(): unknown target request: 0f >> Error: target_request.c:127 target_request(): unknown target request: 0f >> Error: target_request.c:127 target_request(): unknown target request: 0f >> Info: target.c:233 target_init_handler(): executing reset script >> 'str7_flashprogram.script' >> Info: configuration.c:50 configuration_output_handler(): dcc downloads >> are enabled >> Info: configuration.c:50 configuration_output_handler(): waiting for >> target halted... >> Info: configuration.c:50 configuration_output_handler(): timed out >> while waiting for target halt >> Error: target.c:1388 handle_wait_halt_command(): timed out while waiting >> for target halt >> Info: configuration.c:50 configuration_output_handler(): can't work >> with this flash while target is running >> Info: configuration.c:50 configuration_output_handler(): Command >> erase_sector not found >> Info: configuration.c:50 configuration_output_handler(): Command >> write_bank not found >> Warning: arm7_9_common.c:745 arm7_9_assert_reset(): srst resets test >> logic, too >> >> >> 2008/10/31 T?o Benjamin <teo.benjamin at gmail.com> >> >> Back at work. >>> A bigger team now! >>> >>> >>> On Wed, Oct 29, 2008 at 6:45 PM, T?o Benjamin <teo.benjamin at gmail.com>wrote: >>> >>>> Hahahahahahahaha! >>>> After the 100th time, I had this fear... But it's powered, don't worry. >>>> hehehe >>>> I'll go home soon and probably work at this tomorow. >>>> Thanks for your help. It was really usefull. >>>> >>>> Teo >>>> >>>> >>>> On Wed, Oct 29, 2008 at 7:41 PM, Bogdan Marinescu < >>>> bogdan.marinescu at gmail.com> wrote: >>>> >>>>> I'm not loosing my time, I just don't know what to do anymore. If you >>>>> have any kernel modules that are using the LPT port (such as printer >>>>> drivers) try to unload them and then try with "openocd" again. "dmesg" might >>>>> also help with some diagnostic messages in this situation. Try googling for >>>>> something like "openocd lpt linux stuck" or "not working", you might find >>>>> some useful threads. As a last resort, use a Windows system :) (in this case >>>>> go back to parport_port 0x378 instead of parport_port 0, and also google for >>>>> "giveio", you'll need it). >>>>> I will go to sleep now, indeed :) Hope you'll be able to solve your >>>>> problem soon. >>>>> Ah, and one last thing ... the board is powered, right ? :) >>>>> >>>>> Best, >>>>> Bogdan >>>>> >>>>> >>>>> On Wed, Oct 29, 2008 at 11:36 PM, T?o Benjamin <teo.benjamin at gmail.com >>>>> > wrote: >>>>> >>>>>> Now I did "parport_port 0", the Terminal does absolutely nothing. >>>>>> I do sudo openocd -f str7prg.cfg and the normal message appears: >>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 >>>>>> CEST) >>>>>> >>>>>> After that I keep waiting while nothing happens... >>>>>> >>>>>> The last error was my mistake. I'm sorry!!! >>>>>> What is happening is this now... >>>>>> >>>>>> But you should be very tired. It's time to sleep in Romania. Do not >>>>>> loose your sleep whith this! >>>>>> Thanks a lot! >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2008 at 7:23 PM, Bogdan Marinescu < >>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>> >>>>>>> :| Puzzled. That error shouldn't appear at all if you run "openocd" >>>>>>> from the directory in which "str7prg.cfg" exists. Try this: >>>>>>> >>>>>>> $ sudo chmod 666 /dev/parport0 >>>>>>> >>>>>>> Then simply: >>>>>>> >>>>>>> $ openocd -f str7prg.cfg >>>>>>> >>>>>>> (from the right directory). >>>>>>> >>>>>>> I'm running out of ideas ... >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 29, 2008 at 11:17 PM, T?o Benjamin < >>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>> >>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>> 09:00 CEST) >>>>>>>> Error: configuration.c:121 parse_config_file(): couldn't open >>>>>>>> config file >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 29, 2008 at 7:13 PM, Bogdan Marinescu < >>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>> >>>>>>>>> Weird. Try this: >>>>>>>>> >>>>>>>>> parport_port 0 >>>>>>>>> >>>>>>>>> instead of this: >>>>>>>>> >>>>>>>>> parport_port 0x378 >>>>>>>>> >>>>>>>>> in str7prg.cfg, and then >>>>>>>>> >>>>>>>>> $ sudo openocd -f str7prg.cfg >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2008 at 11:10 PM, T?o Benjamin < >>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> I'm sorry, I wasn't any clear. >>>>>>>>>> When I do this ($ sudo openocd -f str7prg.cfg) the same error >>>>>>>>>> occours. No matter what I try now, it happens... hehe >>>>>>>>>> But if I do only "sudo openocd", that other error message shows >>>>>>>>>> up, but I don't know if that means something. >>>>>>>>>> >>>>>>>>>> I'm trying to figure out how to set the right permission to >>>>>>>>>> parport0. >>>>>>>>>> if I do "ls -l /dev/parport0" the terminal shows me: >>>>>>>>>> crw-rw---- 1 lp scanner 99, 0 2008-10-14 15:39 /dev/parport0 >>>>>>>>>> >>>>>>>>>> I don't know right now what to do... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Oct 29, 2008 at 7:02 PM, Bogdan Marinescu < >>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> I mean "sudo openocd" with the same "openocd" parameters you used >>>>>>>>>>> before. Something like this: >>>>>>>>>>> >>>>>>>>>>> $ sudo openocd -f str7prg.cfg >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Oct 29, 2008 at 11:00 PM, T?o Benjamin < >>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> I did sudo openocd and an error message appeared. >>>>>>>>>>>> >>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 >>>>>>>>>>>> 09:00 CEST) >>>>>>>>>>>> Error: configuration.c:121 parse_config_file(): couldn't open >>>>>>>>>>>> config file >>>>>>>>>>>> >>>>>>>>>>>> I'm not quite sure how to set the permission to parport0 >>>>>>>>>>>> properly. >>>>>>>>>>>> >>>>>>>>>>>> Thanks for the help >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:56 PM, Bogdan Marinescu < >>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Then try setting the right permissions to /dev/parport0, or >>>>>>>>>>>>> just sudo openocd ... I don't know, never tried Linux with this parport >>>>>>>>>>>>> interface. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:54 PM, T?o Benjamin < >>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> This is in Linux... >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:53 PM, Bogdan Marinescu < >>>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> This comes from Windows or Linux? In Windows, you need to >>>>>>>>>>>>>>> use giveio. In Linux you should probably set the right permission to >>>>>>>>>>>>>>> /dev/parport0. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:50 PM, T?o Benjamin < >>>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger >>>>>>>>>>>>>>>> (2007-09-05 09:00 CEST) >>>>>>>>>>>>>>>> Error: parport.c:359 parport_init(): cannot open device. >>>>>>>>>>>>>>>> check it exists and that user read and write rights are set >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I'll have a look on the link you sent... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:41 PM, Bogdan Marinescu < >>>>>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Well, my tutorial also says this (feels kinda strange >>>>>>>>>>>>>>>>> quoting myself :) ): >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> "The board comes with its own JTAG adadpter, but it uses a >>>>>>>>>>>>>>>>> parallel interface, and since my computer doesn't have one, I used the >>>>>>>>>>>>>>>>> ARM-USB-TINY <http://www.olimex.com/dev/arm-usb-tiny.html>from Olimex" >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> So you'll need to change your interface description. I >>>>>>>>>>>>>>>>> think you should use this: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> #interface >>>>>>>>>>>>>>>>> interface parport >>>>>>>>>>>>>>>>> parport_port 0x378 >>>>>>>>>>>>>>>>> parport_cable wiggler >>>>>>>>>>>>>>>>> jtag_speed 0 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> instead of this: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> # JTAG interface >>>>>>>>>>>>>>>>> interface ft2232 >>>>>>>>>>>>>>>>> ft2232_device_desc "Olimex OpenOCD JTAG TINY A" >>>>>>>>>>>>>>>>> ft2232_layout olimex-jtag >>>>>>>>>>>>>>>>> jtag_speed 20 >>>>>>>>>>>>>>>>> jtag_nsrst_delay 200 >>>>>>>>>>>>>>>>> jtag_ntrst_delay 200 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> in the "str7prg.cfg" file. >>>>>>>>>>>>>>>>> Change "0x378" to the correct value if you're not using >>>>>>>>>>>>>>>>> LPT1. >>>>>>>>>>>>>>>>> Also, see this thread for more details/troubleshooting >>>>>>>>>>>>>>>>> data: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> http://en.mikrocontroller.net/topic/81646#new >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Good luck! >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Bogdan >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:35 PM, T?o Benjamin < >>>>>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> The same we sent you last month... ;) >>>>>>>>>>>>>>>>>> We tried this in Linux and this message appears. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> We tried in Windows and the message was this one: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Open On-Chip Debugger (2008-06-19 19:00) svn: 717 >>>>>>>>>>>>>>>>>> URL: http://svn.berlios.de/svnroot/repos/openocd/trunk >>>>>>>>>>>>>>>>>> Info: options.c:50 configuration_output_handler(): >>>>>>>>>>>>>>>>>> couldn't open script file >>>>>>>>>>>>>>>>>> str7prg.cfg >>>>>>>>>>>>>>>>>> Error: jtag.c:1511 jtag_interface_init(): JTAG interface >>>>>>>>>>>>>>>>>> has to be specified, >>>>>>>>>>>>>>>>>> see "interface" command >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 6:21 PM, Bogdan Marinescu < >>>>>>>>>>>>>>>>>> bogdan.marinescu at gmail.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Resending to list, as usual ... :) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>>>>>>>>> From: Bogdan Marinescu <bogdan.marinescu at gmail.com> >>>>>>>>>>>>>>>>>>> Date: Wed, Oct 29, 2008 at 10:21 PM >>>>>>>>>>>>>>>>>>> Subject: Re: [Elua-dev] MOD711 >>>>>>>>>>>>>>>>>>> To: T?o Benjamin <teo.benjamin at gmail.com> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> What kind of JTAG adapter are you using? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Bogdan >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Wed, Oct 29, 2008 at 10:16 PM, T?o Benjamin < >>>>>>>>>>>>>>>>>>> teo.benjamin at gmail.com> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Hello eLua people. >>>>>>>>>>>>>>>>>>>> We are trying to use OpenOCD to flash a .bin eLua image >>>>>>>>>>>>>>>>>>>> in the MOD711 from ScTec. >>>>>>>>>>>>>>>>>>>> But we are having a problem here that we can't figure >>>>>>>>>>>>>>>>>>>> out the solution. >>>>>>>>>>>>>>>>>>>> When we finish all the steps of the tutorial in the >>>>>>>>>>>>>>>>>>>> site, this error message appears: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Info: openocd.c:93 main(): Open On-Chip Debugger >>>>>>>>>>>>>>>>>>>> (2007-09-05 09:00 CEST) >>>>>>>>>>>>>>>>>>>> Error: ft2232.c:1439 ft2232_init_libftdi(): unable to >>>>>>>>>>>>>>>>>>>> open ftdi device: device not found >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Any idea how to fix it? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>>>> Teo >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Elua-dev mailing list >>>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Elua-dev mailing list >>>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Elua-dev mailing list >>>>>>>>> Elua-dev at lists.berlios.de >>>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Elua-dev mailing list >>>>>>>> Elua-dev at lists.berlios.de >>>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Elua-dev mailing list >>>>>>> Elua-dev at lists.berlios.de >>>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Elua-dev mailing list >>>>>> Elua-dev at lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Elua-dev mailing list >>>>> Elua-dev at lists.berlios.de >>>>> https://lists.berlios.de/mailman/listinfo/elua-dev >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Elua-dev mailing list >>> Elua-dev at lists.berlios.de >>> https://lists.berlios.de/mailman/listinfo/elua-dev >>> >>> >> >> _______________________________________________ >> Elua-dev mailing list >> Elua-dev at lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > > _______________________________________________ > Elua-dev mailing list > Elua-dev at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/elua-dev > > An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/elua-dev/attachments/20081031/ec251c92/attachment-0001.html |
«
Return to eLua Development
|
1 view|%1 views
| Free forum by Nabble | Edit this page |