Hi Liviu, Could you help to clarify with SEGGER protocol documentation issue:
According to Segger's document RM08001-R7 Date: October 8, 2010, http://www.segger.com/admin/uploads/productDocs/RM08001_JLinkUSBProtocol.pdf section 5.5.3 EMU_CMD_SELECT_IF > SubCmd 1..31 to select interface (0..31) The table below states: 0 TIF_JTAG 1 TIF_SWD This obviously means that to select TIF_JTAG one should write SubCmd = 1. In fact, JTAG interface operates when SubCmd=0 It looks like a typo in documentation, because interfaces 0..31 could not be selected by 1..31 range command. 2012/5/24 Liviu Ionescu <[email protected]>: > > On May 24, 2012, at 19:50 , Liviu Ionescu wrote: > >> I will inform Segger about this new finding. > > here is the reply from Segger: > >> From: "SEGGER - Support J-Link (AG)" <[email protected]> >> Subject: Re: Possible J-Link firmware bug starting with V4.44? >> Date: May 24, 2012 20:04:29 GMT+03:00 >> To: Liviu Ionescu <[email protected]> >> Reply-To: [email protected] >> >> Hi Liviu, >> >> Alright, we were not aware of that OpenOCD does not select the interface >> before it starts communicating with the target. >> A debugger should always select the appropriate target interface before it >> starts communicating with the target, >> since otherwise it could also happen that a previous session with another >> debugger had selected SWD and the interface was not switched again by >> OpenOCD. >> >> >> Best regards >> Alex > > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
