Hi! That helped, thanks! The IDCODE is not necessarily the same as the CPUTAPID right? It's still not working 100%, the output now is pasted below. I guess this was what you were referring to last time that WAIT conditions are not yet handled correctly?
Regards, Ákos Info : KT-LINK SWD-Mode initialization complete... Info : max TCK change to: 30000 kHz Info : clock speed 10 kHz Info : adapter_init ok Info : New SWD context initialized at 0x0x1779650 SWD_I: Executing swd_dap_activate(swdctx=@0x1779650, operation=SWD_OPERATION_EXECUTE) SWD_I: Executing swd_dap_reset(swdctx=@0x1779650, operation=SWD_OPERATION_EXECUTE) SWD_I: Executing swd_dp_read_idcode(swdctx=@0x1779650, operation=SWD_OPERATION_EXECUTE) SWD_I: swd_dp_read_idcode(swdctx=@0x1779650, operation=SWD_OPERATION_EXECUTE, **idcode=0x2BA01477/00101011101000000001010001110111). Info : SWD transport initialization complete. Found IDCODE=0x2BA01477. Info : Selecting SWD transport command set. SWD_I: swd_dp_read(swdctx=@0x1779650, operation=SWD_OPERATION_EXECUTE, addr=0x4, **data=0xF0000003/11110000000000000000000000000011). SWD_I: swd_dp_read(swdctx=@0x1779650, operation=SWD_OPERATION_EXECUTE, addr=0x4, **data=0xF0000001/11110000000000000000000000000001). SWD_I: swd_dp_read(swdctx=@0x1779650, operation=SWD_OPERATION_EXECUTE, addr=0x4, **data=0xF0000000/11110000000000000000000000000000). SWD_I: swd_dp_read(swdctx=@0x1779650, operation=SWD_OPERATION_EXECUTE, addr=0x4, **data=0xF0000000/11110000000000000000000000000000). SWD_I: swd_dp_read(swdctx=@0x1779650, operation=SWD_OPERATION_EXECUTE, addr=0x4, **data=0xF0000001/11110000000000000000000000000001). SWD_W: swd_drv_transmit(swdctx=@0x0x1779650, cmd=@0x0x177a7f0): SWD_ACK_WAIT detectd! SWD_E: swd_drv_transmit(swdctx=@0x0x1779650, cmd=@0x0x177a7f0): Bad ACK, clearing cmdq tail to preserve synchronization... Error: swd_ap_read() error: [SWD_ERROR_ACK_WAIT] got ACK_WAIT response On 8 November 2011 16:47, Tomek CEDRO <[email protected]> wrote: > On Tue, Nov 8, 2011 at 2:15 PM, Akos Vandra <[email protected]> wrote: >> I am trying to get openocd+libswd to work, however I keep getting: >> Error: 57 7 target.c:406 get_current_target(): BUG: current_target out of >> bounds > > Yup, this is the current OpenOCD design limitation - you need to > define a target to work on. Take a look at > http://stm32primer2swd.sf.net there is an example configuration that > should hel you out :-) > > >> oocd_swd_transport_init() is calling the get_current_target() which >> calls get_target_by_num(0) function, but the all_targets list is >> empty. > > transport init needs to interrigate scan chain. unfortunatelly this is > an init operation and it enables some features that setup the > interafce signals etc that should be available before init. this > requires redesign of openocd and this is first task after swd is > working with flash and debug :-) > > Best regards :-) > Tomek > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Openocd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
