[OpenOCD-devel] CPLD + Cortex-M3

2012-09-09 Thread Akos Vandra
Hi! I have a board, where we (will) have a CPLD and a Cortex-M3 in a JTAG chain. Can OpenOCD handle such a configuration (where the CPU is not alone in the chain), and if so, how do I have to write the init script? Regards, Ákos Vandra -

Re: [OpenOCD-devel] OpenOCD 0.6.0 for FreeBSD is on its way :-)

2012-09-09 Thread Tomek CEDRO
On Sun, Sep 9, 2012 at 3:17 AM, Xiaofan Chen wrote: > The following patch what you want but it is not accepted. > http://openocd.zylin.com/#/c/491/ > > As Peter Stuge mentioned in the comments, you can > always manually specify CFLAGS and LDFLAGS to > make configure find libusb-1.0 so that the pat

Re: [OpenOCD-devel] OpenOCD 0.6.0 for FreeBSD is on its way :-)

2012-09-09 Thread Tomek CEDRO
On Sun, Sep 9, 2012 at 11:20 AM, Tomek CEDRO wrote: > The correct solution imo would be to use and provide > /path/libusb-1.0 in LDFLAGS/CFLAGS, wouldnt it? Or we should > create/provide pkgconfig files for FreeBSD master? :-) The .pc files being already there on the system did not help, the pro

Re: [OpenOCD-devel] OpenOCD 0.6.0 for FreeBSD is on its way :-)

2012-09-09 Thread Xiaofan Chen
On Sun, Sep 9, 2012 at 5:21 PM, Tomek CEDRO wrote: > On Sun, Sep 9, 2012 at 11:20 AM, Tomek CEDRO wrote: >> The correct solution imo would be to use and provide >> /path/libusb-1.0 in LDFLAGS/CFLAGS, wouldnt it? Or we should >> create/provide pkgconfig files for FreeBSD master? :-) > > The .pc f

Re: [OpenOCD-devel] CPLD + Cortex-M3

2012-09-09 Thread Andreas Fritiofson
On Sun, Sep 9, 2012 at 10:50 AM, Akos Vandra wrote: > I have a board, where we (will) have a CPLD and a Cortex-M3 in a JTAG chain. > > Can OpenOCD handle such a configuration (where the CPU is not alone in > the chain), and if so, how do I have to write the init script? Yes, that should be possib

Re: [OpenOCD-devel] OpenOCD 0.5.0 and SPIFI flash driver and algos

2012-09-09 Thread gianluca
Andreas Fritiofson wrote: >> >> I would like to know if I need to have the __EXACT__ version at the date of >> the patchset. In short I think I need the version __BEFORE__ the patchset >> date, then apply the fetch command. >> >> Or is it done automagically by git checkout FETCH_HEAD ??? >> > > It