On Tue, Jul 9, 2013 at 8:07 AM, Laszlo Papp <[email protected]> wrote:
> OK, this is now solved by using "soft_reset_halt" as the only workaround
> without srst connected. I will look into a different type of reset
> implemented later, for this omap board.

I'd seen this solved before by increasing the timeouts in the
interface code.  In the case I remember, it was for ft2232.  But you
may find a similar fix works for you.

Oh, I just found the original thread and patch in the mailing list:

http://lists.berlios.de/pipermail/openocd-development/2009-October/011599.html

https://lists.berlios.de/pipermail/openocd-development/attachments/20091025/32e8a10d/attachment.patch

This is just a best guess, btw.
>
>
> On Tue, Jul 9, 2013 at 11:21 AM, Laszlo Papp <[email protected]> wrote:
>>
>> Is the following output expected?
>>
>> >>>>>>
>> sudo openocd -f interface/xds100v2.cfg -f target/omapl138.cfg -c
>> "reset_config trst_and_srst; init; reset halt"
>> Open On-Chip Debugger 0.7.0 (2013-05-05-22:01)
>> Licensed under GNU GPL v2
>> For bug reports, read
>>         http://openocd.sourceforge.net/doc/doxygen/bugs.html
>> Info : only one transport option; autoselect 'jtag'
>> RCLK - adaptive
>> fast memory access is enabled
>> dcc downloads are enabled
>> force hard breakpoints
>> use of EmbeddedICE dbgrq instead of breakpoint for target halt enabled
>> trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
>> connect_deassert_srst
>> Info : max TCK change to: 30000 kHz
>> Info : RCLK (adaptive clock speed)
>> Info : JTAG tap: omapl138.jrc tap/device found: 0x1b7d102f (mfg: 0x017,
>> part: 0xb7d1, ver: 0x1)
>> Info : JTAG tap: omapl138.etb enabled
>> Info : JTAG tap: omapl138.arm enabled
>> Info : Embedded ICE version 6
>> Info : omapl138.arm: hardware has 2 breakpoint/watchpoint units
>> Info : ETM v1.3
>> RCLK - adaptive
>> Info : JTAG tap: omapl138.jrc tap/device found: 0x1b7d102f (mfg: 0x017,
>> part: 0xb7d1, ver: 0x1)
>> Info : JTAG tap: omapl138.etb enabled
>> Info : JTAG tap: omapl138.arm enabled
>> target state: halted
>> target halted in ARM state due to debug-request, current mode: User
>> cpsr: 0x20000010 pc: 0x427ea2f0
>> MMU: enabled, D-Cache: enabled, I-Cache: enabled
>> <<<<<<
>>
>> The problem is that when I am trying to flash u-boot, I am getting the
>> aforementioned address translation failure...
>>
>> >>>>>>
>> User : 651 252 arm926ejs.c:534 arm926ejs_arch_state(): MMU: enabled,
>> D-Cache: enabled, I-Cache: enabled
>> Debug: 652 252 command.c:145 script_debug(): command - ocd_command
>> ocd_command type ocd_sleep 10
>> Debug: 653 252 command.c:145 script_debug(): command - sleep ocd_sleep 10
>> Debug: 655 265 command.c:145 script_debug(): command - ocd_command
>> ocd_command type ocd_flash write_image erase unlock u-boot-build/u-boot.bin
>> 0x60000000
>> Debug: 656 265 command.c:145 script_debug(): command - ocd_flash ocd_flash
>> write_image erase unlock u-boot-build/u-boot.bin 0x60000000
>> User : 658 266 command.c:549 command_print(): auto erase enabled
>> User : 659 266 command.c:549 command_print(): auto unlock enabled
>> Debug: 660 266 configuration.c:86 find_file(): found
>> u-boot-build/u-boot.bin
>> Debug: 661 266 configuration.c:86 find_file(): found
>> u-boot-build/u-boot.bin
>> Debug: 662 284 arm7_9_common.c:2107 arm7_9_read_memory(): address:
>> 0xc7049800, size: 0x00000004, count: 0x00000001
>> Debug: 663 290 armv4_5_mmu.c:47 armv4_5_mmu_translate_va(): 1st lvl desc:
>> 00000000
>> Error: 664 290 armv4_5_mmu.c:50 armv4_5_mmu_translate_va(): Address
>> translation failure
>> Error: 665 290 core.c:239 get_flash_bank_by_addr(): auto_probe failed
>> Debug: 666 290 command.c:631 run_command(): Command failed with error code
>> -309
>> <<<<<<
>>
>> Got a clue?
>>
>> Many thanks in advance,
>> Laszlo
>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> OpenOCD-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openocd-devel
>

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to