Re: [Openocd-development] cygwin: git head jimsh compilation failed

On 05/04/2011, at 4:08 PM, Steve Bennett wrote: > On 05/04/2011, at 3:53 PM, Mathias K. wrote: > >> I was able to link openocd against libjim. There is only a problem to link >> jimsh against libjim. > > Strange. > Perhaps you can send me libjim.a and I'll take a look. For the benefit of the l

Re: [Openocd-development] mdh - 16bit memory

> another question: i haven't been able to find a way to make load_image > and verify_image work with my target, any clues? > to implement "resume" for example, i added .resume=my_resume_function > to my target. is there something similar for load_image? i got this part, had to add .write_buffer a

Re: [Openocd-development] ULINK driver: firmware license questions

It seems that ULINK doesn't support SWD, because TMS pin is output only. But if use another pin for SWDIO input, ULINK can support TMS. Simply connect TMS pin to another input pin eg. J-TRAP. 2011/4/8 Peter Stuge > simon qian wrote: > > Is Schematics of ULINK available? > > http://www.mikrocontr

[Openocd-development] mdh - 16bit memory

hi! i do not understand how this code (from target.c) works. i'm working with a dsp568013. each memory address holds 16 bits. when i run "mdh someaddress count" with count over 16, openocd's output does not match what i would expect. the first 16 words are displayed in a line with address "someaddr

Re: [Openocd-development] ULINK driver: firmware license questions

simon qian wrote: > Is Schematics of ULINK available? http://www.mikrocontroller.net/attachment/51828/ULink.pdf > I can check if it's suitable for Versaloon's USB_TO_XXX protocol. That's a brilliant idea! //Peter ___ Openocd-development mailing list

Re: [Openocd-development] ULINK driver: firmware license questions

Is Schematics of ULINK available? Does it support SWD? I can check if it's suitable for Versaloon's USB_TO_XXX protocol. 2011/4/8 Michael Schwingen > Laurent Gauch wrote: > >> So, ULINK hardware is only used as board platform :-) >> So, you have your own protocol. >> >> I hope you have your own

Re: [Openocd-development] Actual configure file corrupted

Try: make distclean sh bootstrap ./configure --enable-maintainer-mode make if that doesn't work, upgrade various autoconf packages, etc. -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.h

Re: [Openocd-development] ULINK driver: firmware license questions

Laurent Gauch wrote: So, ULINK hardware is only used as board platform :-) So, you have your own protocol. I hope you have your own USB VID/PID too. Why should he? The hardware comes with a valid VID/PID combination - since he only loads a different firmware into the RAM of the ULINK, I do not

Re: [Openocd-development] Actual configure file corrupted

On Thu, Apr 7, 2011 at 5:51 PM, Laurent Gauch wrote: > We cannot patch this file, since the 'configure' is generated at compilation > :-)! Well, it's generated from autotools (during bootstrap), so patch can be sent to these... BR, Drasko ___ Openocd-d

Re: [Openocd-development] Actual configure file corrupted

On Thu, Apr 7, 2011 at 5:19 PM, Peter Stuge https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote: >/ Laurent Gauch wrote: />>/ Last GIT has configure file corrupted. />>/ ; at line 14208 - 14245 - 14315 - 14348 - 14698 - 14726 />>/ />>/ do you need patch ? />/ />/ If you send a pa

Re: [Openocd-development] Actual configure file corrupted

Drasko DRASKOVIC wrote: > > If you send a patch yourself you increase the chances that the > > change is included sooner. > > I did not look, but I had an impression from e-mail that Laurent > thought that the file needs revert (being correct in previous > revisions). > > If correct version is al

Re: [Openocd-development] Actual configure file corrupted

On Thu, Apr 7, 2011 at 5:19 PM, Peter Stuge wrote: > Laurent Gauch wrote: >> Last GIT has configure file corrupted. >> ; at line 14208 - 14245 - 14315 - 14348 - 14698 - 14726 >> >> do you need patch ? > > If you send a patch you are contributing more efficiently. You never > have to ask if a chang

Re: [Openocd-development] Actual configure file corrupted

Laurent Gauch wrote: > Last GIT has configure file corrupted. > ; at line 14208 - 14245 - 14315 - 14348 - 14698 - 14726 > > do you need patch ? If you send a patch you are contributing more efficiently. You never have to ask if a change should be sent as a patch, just send the patch directly. :)

Re: [Openocd-development] ULINK driver: firmware license questions

>/ The EZ-USB gives access to USB but not to the ULINK interface. Right ? / The ULINK consists of the EZ-USB microcontroller, an SRAM, an EEPROM and level shifters. There's even a schematic floating around the net: http://www.mikrocontroller.net/attachment/51828/ULink.pdf Keil is just using the

[Openocd-development] Actual configure file corrupted

Last GIT has configure file corrupted. ; at line 14208 - 14245 - 14315 - 14348 - 14698 - 14726 do you need patch ? Regards, Laurent http://www.amontec.com http://www.amontec.com/jtagkey.shtml Amontec JTAGkey-2 : low-cost High-Speed USB JTAG cable interface

Re: [Openocd-development] field.in_value = NULL - general question

On Thu, Apr 7, 2011 at 1:48 PM, Laurent Gauch wrote: >> Whoops, sorry... >> Without reading in SPrAcc bit (fields[0].in_value = NULL) I can obtain >> up to : 182.220215s (1.938 KiB/s). >> >> However, when I read it in (fields[0].in_value = &spracc_in) I get : >> downloaded 361540 bytes in 12.48972

Re: [Openocd-development] field.in_value = NULL - general question

Drasko DRASKOVIC wrote: On Thu, Apr 7, 2011 at 1:09 PM, Laurent Gauch wrote: / https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote: />>/ Hi all, />>/ I have one general question regarding OpenOCD scans. />>/ />>/ What happens when we set some field.in_value = NULL

Re: [Openocd-development] field.in_value = NULL - general question

On Thu, Apr 7, 2011 at 1:09 PM, Laurent Gauch wrote: >> >> >/ > > > wrote: >> />>/ Hi all, >> />>/ I have one general question regarding OpenOCD scans. >> />>/ >> />>/ What happens when we set some field.in_value = NULL, and in reality

Re: [Openocd-development] field.in_value = NULL - general question

>/ https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote: />>/ Hi all, />>/ I have one general question regarding OpenOCD scans. />>/ />>/ What happens when we set some field.in_value = NULL, and in reality />>/ there are some bits that re shifted out on the scan chain ? Are they

Re: [Openocd-development] field.in_value = NULL - general question

On Thu, Apr 7, 2011 at 11:21 AM, Øyvind Harboe wrote: > On Thu, Apr 7, 2011 at 11:14 AM, Drasko DRASKOVIC > wrote: >> Hi all, >> I have one general question regarding OpenOCD scans. >> >> What happens when we set some field.in_value = NULL, and in reality >> there are some bits that re shifted ou

Re: [Openocd-development] field.in_value = NULL - general question

On Thu, Apr 7, 2011 at 11:14 AM, Drasko DRASKOVIC wrote: > Hi all, > I have one general question regarding OpenOCD scans. > > What happens when we set some field.in_value = NULL, and in reality > there are some bits that re shifted out on the scan chain ? Are they > just ignored ? Does that pose t

[Openocd-development] field.in_value = NULL - general question

Hi all, I have one general question regarding OpenOCD scans. What happens when we set some field.in_value = NULL, and in reality there are some bits that re shifted out on the scan chain ? Are they just ignored ? Does that pose the problem ? To give a concrete example, in the mips_ejtag.c we have