On Mon, Mar 1, 2010 at 1:33 PM, David Brownell wrote:
> That said ... I think I'd be interested in something like
> one of those, but powered by some USB-equipped Cortex-M3.
> (Or maybe even some kind of AVR). Compared to the current
> FT232 + PIC24 combo, the chip costs would be lower, and the
The best reference page for the Bus Pirate is probably the manual:
http://dangerousprototypes.com/bus-pirate-manual/
Microchip's 16bit compilers are gcc-based, but you're correct that
vanilla gcc won't compile for the PIC. I went with the 24FJ chip because
it has a peripheral pin select cross-b
On Sunday 28 February 2010, Arne Pagel wrote:
> > Hmm, I didn't observe that at all. I wonder if that's specific
> > to the "recover" procedure, or whether other power cycle sequences
> > would do the same thing?
> This has nothing to do with the recover procedure,
> this always happens if I power
I've fixed some problems in add_tms_seq and added
support to bitbang & zy1000.
Not tested yet, ready for comments:
http://repo.or.cz/w/openocd/oharboe.git/shortlog/refs/heads/addtms
--
Øyvind Harboe
Visit us at Embedded World, March 2nd-4th. IS2T's stand, HALL 10 - 118
http://www.zylin.com/ev
On Sunday 28 February 2010, David Brownell wrote:
> arm_semihosting.c:71: error: ‘spsr’ may be used uninitialized in this function
> arm_semihosting.c:71: error: ‘lr’ may be used uninitialized in this function
Quickie build fix appended -- code not tested. Note the REVISIT comment.
- Dave
--
Hmm, I didn't observe that at all. I wonder if that's specific
to the "recover" procedure, or whether other power cycle sequences
would do the same thing?
This has nothing to do with the recover procedure,
this always happens if I power cycle the target hardware.
I compiled with --enable-ft2232
On Sunday 28 February 2010, David Brownell wrote:
> On Sunday 28 February 2010, Antonio Borneo wrote:
> > Same compile issue with old Fedora 6, gcc version 4.1.1 20061011 (Red
> > Hat 4.1.1-30)
And just now with an Ubuntu that has
gcc (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu4)
and also a newer
On Sunday 28 February 2010, Antonio Borneo wrote:
> Same compile issue with old Fedora 6, gcc version 4.1.1 20061011 (Red
> Hat 4.1.1-30)
>
> Dave,
> could you please report gcc version in your cygwin?
"gcc -v" says: gcc (GCC) 4.3.4 20090804 (release) 1
... and that should be the latest version
On Saturday 27 February 2010, Michal Demin wrote:
> +++ b/tcl/interface/buspirate.cfg
> @@ -0,0 +1,16 @@
> +#
> +# Buspirate with OpenOCD support
> +#
> +# http://dangerousprototypes.com/category/bus-pirate/
> +#
> +
Ignoring the code, for the moment ... that blog is the only
reference you give t
On Sunday 28 February 2010, Gene Smith wrote:
> It was at least 6 months ago that I tried getting Olimex serial to work
> in linux. I may give it another look soon. Does it just require the
> libftdi package?
No. Serial ports are pure kernel driver territory;
specifically drivers/usb/serial/ftd
David Brownell wrote, On 02/28/2010 11:17 PM:
On Sunday 28 February 2010, Gene Smith wrote:
I was never able to get the serial port on the Olimex to work with
linux (but never really needed it). Maybe user error?
Check "dmesg" output to see which port it was configured to be.
Likely /dev/ttyU
Same compile issue with old Fedora 6, gcc version 4.1.1 20061011 (Red
Hat 4.1.1-30)
Dave,
could you please report gcc version in your cygwin?
Best Regards,
Antonio Borneo
On Mon, Mar 1, 2010 at 12:13 PM, David Brownell wrote:
> A test build (cygwin, as it happened) after your latest commits giv
On Sunday 28 February 2010, Gene Smith wrote:
> I was never able to get the serial port on the Olimex to work with
> linux (but never really needed it). Maybe user error?
Check "dmesg" output to see which port it was configured to be.
Likely /dev/ttyUSB0 would suffice ... unless you have other
U
A test build (cygwin, as it happened) after your latest commits gives me:
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../src -I../../src -g -O2 -Wall
-Wstrict-prototypes -Wformat-security -Wextra -Wno-unused-parameter
-Wbad-function-cast -Wcast-align -Wredundant-decls -Werror -MT
arm_semih
Xiaofan Chen wrote, On 02/28/2010 10:51 PM:
On Mon, Mar 1, 2010 at 11:33 AM, Gene Smith wrote:
On linux, I can plug the Olimex into any usb port and it works.
Yeah, that is one thing Linux works better. ;-)
But there are other places Windows works better.
Like I was never able to get th
Gene Smith wrote, On 02/28/2010 10:33 PM:
Do you have to require a windows install of OpenOCD to always run on the
same USB port when using Olimex jtag? Or do you just have to re-install
drivers for each possible usb port you might be using?
Re-installing driver on every possible USB port see
On Mon, Mar 1, 2010 at 11:33 AM, Gene Smith wrote:
> Do you have to require a windows install of OpenOCD to always run on the
> same USB port when using Olimex jtag? Or do you just have to re-install
> drivers for each possible usb port you might be using?
>
> This is using Freddie's libusb0.sys
Xiaofan Chen wrote, On 02/28/2010 09:37 PM:
On Mon, Mar 1, 2010 at 9:42 AM, Gene Smith wrote:
It worked for me on two different XP-Home systems. Just disabled it and and,
for good measure, rebooted a couple times. Came back up with no "New H/W"
nags.
Then that is good. But what happens if y
On Thursday 25 February 2010, David Brownell wrote:
> On Thursday 25 February 2010, Mariano Alvira wrote:
> >
> > > By the way ... I kind of suspect this will cause build breakage
> > > on systems configured to use FTDI's library, since INTERFACE_A
> > > and suchlike are not defined.
> >
> > I do
On Mon, Mar 1, 2010 at 9:42 AM, Gene Smith wrote:
> It worked for me on two different XP-Home systems. Just disabled it and and,
> for good measure, rebooted a couple times. Came back up with no "New H/W"
> nags.
>
Then that is good. But what happens if you insert it to a different USB port?
An
Xiaofan Chen wrote, On 02/28/2010 06:08 PM:
On Mon, Mar 1, 2010 at 5:24 AM, Gene Smith wrote:
On the Olimex CD (and on their site) there are two inf files:
ftdibus.inf
ftdiport.inf
I used ftdiport. After installing it at the yellow ? device, the yellow ?
remained but it put new Olimex OCD De
On Mon, Mar 1, 2010 at 7:08 AM, Xiaofan Chen wrote:
BTW, if you do not need to use the serail port, I think Olimex already
provide the inf file for libusb-win32. The INF file is for both interface
so you will lose the serial port.
http://www.olimex.com/dev/arm-usb-ocd.html
http://www.olimex.com/d
On Mon, Mar 1, 2010 at 5:24 AM, Gene Smith wrote:
> On the Olimex CD (and on their site) there are two inf files:
>
> ftdibus.inf
> ftdiport.inf
>
> I used ftdiport. After installing it at the yellow ? device, the yellow ?
> remained but it put new Olimex OCD Device under "Universal Serial Bus
>
On Sunday 28 February 2010, Arne Pagel wrote:
> David Brownell schrieb:
> > OK, I just merged this. It should work with any JTAG (or
> > JTAG/SWD) Adapter which implements the jtag_add_tms_seq()
> > infrastructure ... for the moment, that's only FT2232 ...
> > so all the Stellaris eval boards are
David Brownell schrieb:
OK, I just merged this. It should work with any JTAG (or
JTAG/SWD) Adapter which implements the jtag_add_tms_seq()
infrastructure ... for the moment, that's only FT2232 ...
so all the Stellaris eval boards are covered, and others
can start implementing that too.
Great J
Xiaofan Chen wrote, On 02/28/2010 03:33 AM:
On Sun, Feb 28, 2010 at 4:05 PM, Gene Smith wrote:
LibUSB-Win32 Devices
Olimex ARM-USB-OCD (Channel A)
? Other Devices
? Olimex OpenOcd JTAG
Universal Serial Bus Controller
USB Composite
USB Composite
The first one lo
On Sun, Feb 28, 2010 at 10:42:30AM -0800, David Brownell wrote:
> On Sunday 28 February 2010, Mariano Alvira wrote:
> > On Sat, Feb 27, 2010 at 10:54:29PM -0800, David Brownell wrote:
> > > Merged the first two.
>
> ... and now the third one ...
Nice thanks!
>
>
> > Also, did you not merge the
I don't have a phytec board to test on handy(if someone wants
to send us one it would be greatly appreciated!).
Attached is a patch that tries to cleanup target/board scripts a bit,
but I really rely on the list to test, polish comments & feed back
a suitable version to be merged.
--
Øyvind Harb
On Sunday 28 February 2010, Mariano Alvira wrote:
> On Sat, Feb 27, 2010 at 10:54:29PM -0800, David Brownell wrote:
> > Merged the first two.
... and now the third one ...
> Also, did you not merge the redbee-usb patch because the product isn't
> available yet or is there another reason?
Unavai
On Sat, Feb 27, 2010 at 10:54:29PM -0800, David Brownell wrote:
> Merged the first two.
Also, did you not merge the redbee-usb patch because the product isn't
available yet or is there another reason?
-Mar.
___
Openocd-development mailing list
Openocd-d
On Sat, Feb 27, 2010 at 10:54:29PM -0800, David Brownell wrote:
> Merged the first two.
Great, thanks for your help.
-Mar.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-develo
On Sunday 28 February 2010, Xiaofan Chen wrote:
> > Under Ubuntu 9.10 64bit, it is still broken.
For some reason my Ubuntu x86-64 boxes are still 8.10 ... they're fine,
albeit due for an upgrade.
___
Openocd-development mailing list
Openocd-development@
On Sun, Feb 28, 2010 at 4:05 PM, Gene Smith wrote:
> LibUSB-Win32 Devices
> Olimex ARM-USB-OCD (Channel A)
> ? Other Devices
> ? Olimex OpenOcd JTAG
> Universal Serial Bus Controller
> USB Composite
> USB Composite
>
> The first one looks like the correct and functiona
I've been using a svn snapshot version (from last summer) of openocd on
linux with Olimex-arm-usb-ocd device and another guy is using same
version that I built for windows with jlink. Unfortunately, the jlink
failed and now he is using our spare Olimex-arm-usb-ocd in its place. He
also upgraded
On Sun, Feb 28, 2010 at 3:19 PM, Xiaofan Chen wrote:
Somehow the latest git is broken.
>> Hmm, latest git works under Arch Linux. Need to check back
>> Ubuntu 9.10 64bit later.
>
> Under Ubuntu 9.10 64bit, it is still broken.
But it does work with Ubuntu 9.10 32bit. Strange.
mc...@ubuntu:~
35 matches
Mail list logo
