On 16 January 2013 11:52, Tomek CEDRO <[email protected]> wrote: > On Wed, Jan 16, 2013 at 12:03 PM, Spencer Oliver <[email protected]> wrote: >> As Freddie pointed out a poll is required, so this suggests the >> handle_target is not working as it should. > > Please point the exact location of the code/handler and I will take a > look at it. This means Target is implemented in a dirty way - it > somehow ommits MEM-AP read/writes that are used to access ARM > peripherals... >
target.c:2171 > >> The hla adapters (currently stlink and ti_icdi behave at a much higher >> layer, eg resume/stop. >> From the OpenOCD point of view they are more like targets. > > Hmm, we need to think of some good organization for that, so the > proposed 7 layers organization is valid and still we can use existing > existing code. > > Answering some questions should sort things out - please reply in > "internals reorganization" thread: > 1. How do you select your target working with HLA? > 2. How do you configure target and HLA? > 3. What are the differences between HLA design and existing > Interface-Target design? > 4. How to make both compatible? > 5. How to fit both into 7 layer organization? > ok > >>>> One tweak i have made is that all my adapters tested use the inverse >>>> "RnW" logic, so i think we need to add support for this. >>> >>> I think I have forseen that - please try "nRnW" signal name, it should >>> work together with "RnW" signal - this is the pair for driving the >>> output buffers on a direction change :-) >> >> I have looked in the src and cannot see anything that implements this >> - can you double check ? > > Okay, ill take a look, if the code is not there I will write it, but I > remember I done this before :-) > thanks >> The swd support still needs a lot of work/cleanup before it can be >> merged into master. > > I need your help guys, I have been working on this solution for months > with no supoprt, you have the solution and the documentation, its time > for you to work a bit so I can get into other things, I am here, if > you need anything just write :-) > > The commits are minimal set of changes, only one of them can break > tihngs all others should be non-invasive, for me the work is done, if > you need to adapt it more into OpenOCD style please do so, I would > prefer however that you add new commits rather than editing existing > ones as this will surely break things and erase development history > and this is not the way I like to work, some work is done, things > start to work, lets move forward :-) > I am going through your changes now, i have already mentioned some of the issues on gerrit. At minimum we need a rebase, but i am also after a second opinion on some of the changes, mainly effecting the transport and additional jtag_interface for swd (ft2232_swd). Cheers Spen ------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
