I (think I) fixed the poke.c demo and the link to the configuration
file for openocd.


commit 0faa5ff61401d6ab129aabc95d7b4062cee1002f
Author: kwilson <kwil...@cs.pdx.edu>
Date:   Thu Jan 29 12:49:33 2009 -0800

    Changed link for ...Config/openocd_lpc2148.cfg to point at version
    for v1257 of openocd configuration file.

    Changed '\r' to '\n' in serial_getline function, poke.c now
    accepts input from terminal.

Sarah A Sharp wrote:
> Does the poke example work when the JTAG programmer is removed, and
> you use a USB to serial adapter to talk to the programmed LPC2148
> board?
> I can see from minicom that the RS232_0 serial port is outputting
> data.    Button presses seem to produce output also.  However, the
> board isn't echoing anything I type at it, so I'm concerned the board
> can't hear me.
> The screenshot shows a serial only connection, but I can't use a
> straight serial cable because my host PC doesn't have a serial port.
> Suggestions?
> Sarah
> On Wed, Jan 28, 2009 at 10:54 PM, Sarah A Sharp <saharabe...@gmail.com> wrote:
>> Heh, nevermind.  I figured it out.  Apparently the documentation
>> points to an old config file and the correct config file to use is
>> openocd_lpc2148_v1257.cfg
>> Fixing the documentation to match.
>> Sarah
>> On Wed, Jan 28, 2009 at 10:51 PM, Sarah A Sharp <saharabe...@gmail.com> 
>> wrote:
>>> Unfortunately I don't think I have a 9V wall wort.  I'll look around...
>>> I'm running into an issue before I can even program the board.  I get
>>> the error message 'invalid command name "daemon_startup_attach"' when
>>> I try to run the command
>>> sudo /home/sarah/git/lpc-kit/LPC/2148/OCD/bin/openocd -s
>>> ../../../../Config/2148 -f openocd_lpc2148.cfg
>>> I'm trying to download the poke example to the board.  Jamey seems to
>>> think the config file is wrong for this version of openocd.  I used
>>> the psas OCD download script, and the version seems to be the same one
>>> recommended by the documentation:
>>>  $ openocd -v
>>> Open On-Chip Debugger 1.0 (2009-01-28-22:13) svn:1257
>>> Suggestions?
>>> Sarah
>>> On Wed, Jan 28, 2009 at 10:44 PM, Dave Camarillo
>>> <dave.camari...@gmail.com> wrote:
>>>> Hi Sarah, that pretty much correct. One interesting side thing is that
>>>> sometimes the olimex jtag programmer is unable to provide enough power
>>>> to the 2148 board, and you run into flashing problems. You can avoid
>>>> this by using a 9VDC wall wart. My hypothesis is that this stems from
>>>> the lack of current sourcing abilities of some laptops (mainly my
>>>> laptop), so it may also be mitigated by using a powered hub.
>>>> Hope that's of some assistance...
>>>> -dave
>>>> On Thu, Jan 29, 2009 at 6:36 AM, Sarah A Sharp <saharabe...@gmail.com> 
>>>> wrote:
>>>>> Hi Kay,
>>>>> Do these directions look right for the cabling/jumper setup for the
>>>>> LPC2148 board and Olimex OCD JTAG programmer?  I couldn't remember if
>>>>> there needs to be an other USB cable from the LPC2148 to the host PC
>>>>> or not when I'm trying to program the board.
>>>>> 1. Make sure to set the Olimex JTAG programmer to 9V by jumpering on
>>>>> the right-most pins (the two farthest away from the JTAG cable).
>>>>> 2. Plug a USB cable from the JTAG programmer to your computer.
>>>>> 3. Power the LPC2148 dev board by plugging it into the JTAG programmer
>>>>> with the white cable.
>>>>> 4. Make sure the LPC2148 debug jumper is jumpered (the DBG_E pins are
>>>>> next to the JTAG port)
>>>>> 5. Set both dip-switches on the LPC2148 board to the 'off' position.
>>>>> Did I miss anything?  I'm putting these directions into the
>>>>> documentation for the project, since they seem to be scattered between
>>>>> the Keil documentation, the Olimex schematic, and the PSAS wiki.
>>>>> Sarah Sharp
>>>>> _______________________________________________
>>>>> psas-avionics mailing list
>>>>> psas-avionics@lists.psas.pdx.edu
>>>>> http://lists.psas.pdx.edu/mailman/listinfo/psas-avionics

psas-avionics mailing list

Reply via email to