On Thu, Feb 18, 2010 at 5:23 AM, CeDeROM wrote:
>> Error: J-Link command 0xdf failed (-6)
>> Error: usb_bulk_write failed (requested=6, result=-6)
>> Error: jlink_tap_execute, wrong result -107 (expected 1)
>> Command handler execution failed
>> Warn : jtag initialization failed; try 'jtag init' a
On Fri, Feb 19, 2010 at 2:55 PM, Xiaofan Chen wrote:
>> This seems to work fine. But then again you delete the parallel port
>> support which is actually wrong. The codes for FreeBSD ppi API
>> is already in place. I did not notice this one before.
>>
>
> By default -Werror this will fail.
>
> By
On Fri, Feb 19, 2010 at 2:42 PM, Xiaofan Chen wrote:
> On Tue, Feb 16, 2010 at 4:55 AM, CeDeROM wrote:
>> Btw. I have just submitted an 0.4.0-RC2 "openocd-devel" port for
>> FreeBSD Port System - currently it awaits assignment and approval, but
>> in a few days it should become available for test
On Tue, Feb 16, 2010 at 4:55 AM, CeDeROM wrote:
> Btw. I have just submitted an 0.4.0-RC2 "openocd-devel" port for
> FreeBSD Port System - currently it awaits assignment and approval, but
> in a few days it should become available for testing straight from the
> port tree - until then attached pac
On Fri, Feb 19, 2010 at 2:10 AM, CeDeROM wrote:
> Hello Xiao!
I am Xiaofan. ;-)
> On Wed, Feb 17, 2010 at 11:53 PM, Xiaofan Chen wrote:
>> Hmm, I thought you were not using the digest. It is a bad
>> idea to use the digest format when you become a regular
>> of the list.
>
> Yeah but even with
Hello Xiao!
On Wed, Feb 17, 2010 at 11:53 PM, Xiaofan Chen wrote:
> Hmm, I thought you were not using the digest. It is a bad
> idea to use the digest format when you become a regular
> of the list.
Yeah but even with digest I receive so many emails everyday that it
takes over hours to sort/read
On Thu, Feb 18, 2010 at 5:23 AM, CeDeROM wrote:
> Ah, there were reports from Australia even for 0.2.0 that this JLink
> does not work on FreeBSD, but the patch is provided - please take a
> look at patch for current openocd port
> (/usr/ports/devel/openocd/files) and try to (somehow) apply this
Hello Xiaofan!
On Wed, Feb 17, 2010 at 10:42 AM, Xiaofan Chen wrote:
> Message: 3
> Date: Wed, 17 Feb 2010 16:41:00 +0800
> From: Xiaofan Chen
> Subject: Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was:
> FreeBSD status of 0.4.0-RC1)
> To: Openocd-Dev
>
On Wed, Feb 17, 2010 at 8:33 PM, Xiaofan Chen wrote:
> On Wed, Feb 17, 2010 at 4:41 PM, Xiaofan Chen wrote:
>
>> The first run with EK-LM3S1968 seems to work. But J-Link does not seem to
>> work.
>
> J-Link V3 (black, IAR OEM) does not seem to work at all under FreeBSD.
> J-Link V7 (black, ADI O
On Wed, Feb 17, 2010 at 4:41 PM, Xiaofan Chen wrote:
> The first run with EK-LM3S1968 seems to work. But J-Link does not seem to
> work.
J-Link V3 (black, IAR OEM) does not seem to work at all under FreeBSD.
[mc...@myfreebsd
/usr/home/mcuee/Desktop/build/openocd/luminary/lm3s1968]$ openocd -f
On Wed, Feb 17, 2010 at 4:35 PM, Xiaofan Chen wrote:
> On Mon, Feb 15, 2010 at 8:43 AM, Xiaofan Chen wrote:
>> I just want to use plain git if possible without using the port system.
>
> Yes it is possible now. I do not need to use the port system after all.
>
The first run with EK-LM3S1968 seem
On Mon, Feb 15, 2010 at 8:43 AM, Xiaofan Chen wrote:
> I just want to use plain git if possible without using the port system.
Yes it is possible now. I do not need to use the port system after all.
[mc...@myfreebsd ~/Desktop/build/openocd/build]$
CFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local
For those interested - status of the port can be verified online at:
http://www.freebsd.org/cgi/query-pr.cgi?pr=143967
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists
Hello David!
On Mon, Feb 15, 2010 at 8:08 PM, David Brownell wrote:
> On Monday 15 February 2010, CeDeROM wrote:
>> Hello! I have some problems with running STM32Primer1 and the
>> 0.4.0-rc2 on FreeBSD :-(
>>
>> %openocd -f interface/rlink.cfg -f board/stm32f10x_128k_eval.cfg
>>
>
>
> For starter
On Monday 15 February 2010, CeDeROM wrote:
> Hello! I have some problems with running STM32Primer1 and the
> 0.4.0-rc2 on FreeBSD :-(
>
> %openocd -f interface/rlink.cfg -f board/stm32f10x_128k_eval.cfg
>
For starters, "board/stm32f10x_128k_eval.cfg" isn't a Primer1 config.
But also ... don't
Hello! I have some problems with running STM32Primer1 and the
0.4.0-rc2 on FreeBSD :-(
%openocd -f interface/rlink.cfg -f board/stm32f10x_128k_eval.cfg
Open On-Chip Debugger 0.4.0-rc2 (2010-02-15-20:22)
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
1000 kHz
jtag_nsr
On Mon, Feb 15, 2010 at 9:36 AM, CeDeROM wrote:
> Ah yes, OpenOCD's configure script can also assume using
> "/usr/local/lib" and "/usr/local/include" to search for libraries and
> header files - it would be nice, however if it don't the Port will
> make it automatically :-)
Actually I consider t
On Mon, Feb 15, 2010 at 1:21 AM, Xiaofan Chen wrote:
> On Mon, Feb 15, 2010 at 9:13 AM, Xiaofan Chen wrote:
>>> and there are some addtional libraries/includes passed to the compiler
>>> in the Makefile:
> (...)
>> I think the above patches should be integrated into the main
>> OpenOCD source tre
On Mon, Feb 15, 2010 at 12:53 AM, Xiaofan Chen wrote:
> On Mon, Feb 15, 2010 at 8:35 AM, CeDeROM wrote:
>
>> If you want to test the latest 0.4.0-rc2 source code, please download
>> this unapproved port package and uncompress it into /usr/ports/devel:
>> http://files.tomek.cedro.info/stuff/openoc
On Mon, Feb 15, 2010 at 9:13 AM, Xiaofan Chen wrote:
>> and there are some addtional libraries/includes passed to the compiler
>> in the Makefile:
>> CFLAGS+= -I${LOCALBASE}/include -L${LOCALBASE}/lib
>>
>> Wow, Ive just realised that using FreeBSD is somehow like programming
>> in assembly
On Mon, Feb 15, 2010 at 9:01 AM, CeDeROM wrote:
> That is probably because port got requested dependencies:
> ===> openocd-0.4.0.r2 depends on executable: gmake - found
> ===> openocd-0.4.0.r2 depends on shared library: ftdi - found
>
> and there are some addtional libraries/includes passed t
On Mon, Feb 15, 2010 at 12:43 AM, Xiaofan Chen wrote:
> On Mon, Feb 15, 2010 at 8:35 AM, CeDeROM wrote:
>> Xiao, the port is a some kind of a program plug into a FreeBSD system
>> - for a program to work on a FreeBSD it must have its own Port, also
>> any change in the program code may be done on
On Mon, Feb 15, 2010 at 8:35 AM, CeDeROM wrote:
> If you want to test the latest 0.4.0-rc2 source code, please download
> this unapproved port package and uncompress it into /usr/ports/devel:
> http://files.tomek.cedro.info/stuff/openocd-040-rc2.tar.gz
>
> If you want to get the sources from a GI
On Mon, Feb 15, 2010 at 8:35 AM, CeDeROM wrote:
> Xiao, the port is a some kind of a program plug into a FreeBSD system
> - for a program to work on a FreeBSD it must have its own Port, also
> any change in the program code may be done only within its Port - what
> you get from a binary is a resul
On Sun, Feb 14, 2010 at 3:26 PM, Xiaofan Chen wrote:
> Do you need to run 8-CURRENT in order to get this latest port?
> It seems 8.0-RELEASE ships with an old version of libftdi
> and it does not work with OpenOCD. I also could not got
> the latest git to build under FreeBSD.
Xiao, the port is a
On Sun, Feb 14, 2010 at 4:37 PM, Xiaofan Chen wrote:
> Yeah I think openocd-devel port is the way to go. I do not really
> like the port system very much due to the fact that many
> mirrors are dead. The binaries are also not often updated.
> Many ports are actually quite outdated.
Almost all por
26 matches
Mail list logo
