Re: [OpenOCD-devel] MIPS BUG ?

[Xiaochen Z. <zho...@h3...>]

On 2012年02月16日 05:13, Spencer Oliver wrote:
> 2012/2/15<jan...@ce...>:
>> On 15 Feb 2012 at 20:31, Spencer Oliver wrote:
>>
>>> On 15 February 2012 19:33,<jan...@ce...>  wrote:
>>>> I tried to halt the CPU with halt command.
>>>> It failed  but the debug shows
>>>>
>>>> #########
>>>> Debug: 40 13610 command.c:151 script_debug(): command - ocd_command ocd_command
>>>> type ocd_halt
>>>> Debug: 41 13625 command.c:151 script_debug(): command - halt ocd_halt
>>>> Debug: 43 13625 target.c:2354 handle_halt_command(): -
>>>> Debug: 44 13625 mips_m4k.c:185 mips_m4k_halt(): target->state: running
>>>> Debug: 45 13641 mips_ejtag.c:250 mips_ejtag_enter_debug(): ejtag_ctrl: 0x0020c10
>>>> 8
>>>> Debug: 46 13641 target.c:2333 target_wait_state(): waiting for target halted...
>>>> Info : 49 14656 target.c:468 target_poll(): Halt timed out, wake up GDB.
>>>> Debug: 50 14656 target.c:1198 target_call_event_callbacks(): target event 2 (gdb
>>>> -halt)
>>>> Error: 58 18656 target.c:2344 target_wait_state(): timed out while waiting for t
>>>> arget halted
>>>> Debug: 59 18656 command.c:638 run_command(): Command failed with error code -4
>>>> User : 60 18656 command.c:679 command_run_line(): in procedure 'halt'
>>>> ##########
>>>> As you can see ejtag_ctrl: 0x0020c108.
>>>> That is the 3rd bit is 1 and it means Debug Mode.
>>> I can only see ejtag_ctrl: 0x0020c10 - which is telling us yout target
>>> is running
>>
>> The 8 is on the new line,below 0x0020c10
>>
>> Here is another log, Another bug??.
>> Here is the log
>>
>> Info : clock speed 6000 kHz
>> Info : JTAG tap: bcm7401.cpu tap/device found: 0x2740117f (mfg: 0x0bf, part: 0x7
>> 401, ver: 0x2)
>> Info : accepting 'telnet' connection from 4444
>> User : 39 19172 command.c:557 command_print(): debug_level: 3
>> Debug: 40 24625 command.c:151 script_debug(): command - ocd_command ocd_command
>> type ocd_halt
>> Debug: 41 24625 command.c:151 script_debug(): command - halt ocd_halt
>> Debug: 43 24640 target.c:2354 handle_halt_command(): -
>> Debug: 44 24640 mips_m4k.c:185 mips_m4k_halt(): target->state: running
>> Debug: 45 24640 mips_ejtag.c:250 mips_ejtag_enter_debug(): ejtag_ctrl: 0x0020c10
>> 0
>> Error: 46 24656 mips_ejtag.c:253 mips_ejtag_enter_debug(): Failed to enter Debug
>>   Mode!
>> Debug: 47 24656 target.c:2333 target_wait_state(): waiting for target halted...
>> Info : 50 25672 target.c:468 target_poll(): Halt timed out, wake up GDB.
>> Debug: 51 25672 target.c:1198 target_call_event_callbacks(): target event 2 (gdb
>> -halt)
>> Error: 59 29672 target.c:2344 target_wait_state(): timed out while waiting for t
>> arget halted
>> Debug: 60 29672 command.c:638 run_command(): Command failed with error code -4
>> User : 61 29672 command.c:679 command_run_line(): in procedure 'halt'
>> Debug: 62 40093 command.c:151 script_debug(): command - ocd_command ocd_command
>> type ocd_halt 100
>> Debug: 63 40109 command.c:151 script_debug(): command - halt ocd_halt 100
>> Debug: 65 40109 target.c:2354 handle_halt_command(): -
>> Debug: 66 40109 mips_m4k.c:185 mips_m4k_halt(): target->state: running
>> Debug: 67 40125 mips_ejtag.c:250 mips_ejtag_enter_debug(): ejtag_ctrl: 0x0020d10
>> 0
>> Error: 68 40125 mips_ejtag.c:253 mips_ejtag_enter_debug(): Failed to enter Debug
>>   Mode!
>> Debug: 69 40125 target.c:2333 target_wait_state(): waiting for target halted...
>> Info : 72 41140 target.c:468 target_poll(): Halt timed out, wake up GDB.
>> Debug: 73 41140 target.c:1198 target_call_event_callbacks(): target event 2 (gdb
>> -halt)
>> Debug: 93 51078 mips32_pracc.c:143 wait_for_pracc_rw(): DEBUGMODULE: No memory a
>> ccess in progress!
>> Debug: 94 51078 mips_m4k.c:858 mips_m4k_read_memory(): address: 0xff300000, size
>> : 0x00000004, count: 0x00000001
>> Debug: 95 51093 target.c:1741 target_read_u32(): address: 0xff300000, value: 0x0
>> 000001e
>> Debug: 96 51093 mips32.c:569 mips32_configure_break_unit(): DCR 0x1e numinst 0 n
>> umdata 0
>> Debug: 99 52109 mips32_pracc.c:143 wait_for_pracc_rw(): DEBUGMODULE: No memory a
>> ccess in progress!
>> Debug: 100 52109 mips_m4k.c:112 mips_m4k_debug_entry(): entered debug state at P
>> C 0x0, target->state: halted
>> Debug: 101 52109 target.c:1198 target_call_event_callbacks(): target event 2 (gd
>> b-halt)
>> Debug: 102 52125 target.c:1198 target_call_event_callbacks(): target event 3 (ha
>> lted)
>> User : 103 52125 target.c:1475 target_arch_state(): target state: halted
>> User : 104 52125 mips32.c:258 mips32_arch_state(): target halted in MIPS32 mode
>> due to debug-request, pc: 0x00000000
>> Debug: 105 81718 command.c:151 script_debug(): command - ocd_command
>> ocd_command
>>   type ocd_mww 0x100
>> Debug: 106 81718 command.c:151 script_debug(): command - mww ocd_mww 0x100
>> Debug: 108 81734 command.c:151 script_debug(): command - ocd_command
>> ocd_command
>>   type ocd_usage mww
>> Debug: 109 81734 command.c:151 script_debug(): command - usage ocd_usage mww
>> User : 111 81734 command.c:847 command_help_show_indent():   User : 112 81734 co
>> mmand.c:885 command_help_show(): bcm7401.cpu mwwUser : 113 81750 command.c:892
>> c
>> ommand_help_show():  User : 114 81750 command.c:864 command_help_show_wrap(): ad
>> dress data [count]
>> User : 115 81750 command.c:885 command_help_show(): mwwUser : 116 81750
>> command.
>> c:892 command_help_show():  User : 117 81750 command.c:864 command_help_show_wra
>> p(): ['phys'] address value [count]
>> User : 118 81750 command.c:679 command_run_line(): in procedure 'mww'
>> Debug: 119 143156 command.c:151 script_debug(): command - ocd_command
>> ocd_comman
>> d type ocd_mdw 0x100
>> Debug: 120 143156 command.c:151 script_debug(): command - mdw ocd_mdw 0x100
>> Debug: 122 143156 mips_m4k.c:858 mips_m4k_read_memory(): address: 0x00000100, si
>> ze: 0x00000004, count: 0x00000001
>> Warn : 123 143156 mips_m4k.c:862 mips_m4k_read_memory(): target not halted
>> Debug: 124 143172 command.c:638 run_command(): Command failed with error code -3
>> 04
>> User : 125 143172 command.c:679 command_run_line(): in procedure 'mdw'
>>
>>
>> This log is a response to my command from this telnet session
>>
>> Open On-Chip Debugger
>>> debug_level 3
>> debug_level: 3
>>> halt
>> Failed to enter Debug Mode!
>> Halt timed out, wake up GDB.
>> timed out while waiting for target halted
>> in procedure 'halt'
>>> halt 100
>> Failed to enter Debug Mode!
>> Halt timed out, wake up GDB.
>> target state: halted
>> target halted in MIPS32 mode due to debug-request, pc: 0x0000000
>>> mww 0x100
>>   bcm7401.cpu mww address data [count]
>> mww ['phys'] address value [count]
>> in procedure 'mww'
>>> mdw 0x100
>> target not halted
>> in procedure 'mdw'
>> It says it was halted( for the second time) but when I tried to read a value
>> see
>> mdw 0x100
>> it says
>> target not halted
>> Does it mean that my mistyping
>> mww 0x100
>> caused that problem?
>> or is it a bug?
>> Thanks for the reply
>>
> cc list.
>
> Strange i am running out of ideas.
> Can you reduce the jtag clock to something like 500kHz - we need to
> eliminate all possible issues.
>
> Cheers
> Spen
>
> ------------------------------------------------------------------------------
> Virtualization&  Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> OpenOCD-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openocd-devel

Most of Broadcom CPUs can not supported by openocd. That's why our
company buy commercial JTAG-debug. And even commercial debug can not
fully support Broadcom CPUs, for example BDI-2000.

I guess Broadcom maybe add some features to EJTAG, and this made EJTAG
not standard. But no one know this because Broadcom never make their
datasheets open.

Regards,

Xiaochen Zhou

-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!