From: Jens B. <jen...@gp...> - 2015-05-08 13:40:00
|
Hi all. I've built OpenOCD 0.9.0-rc1 on Mac (and as some of you know, I've placed an installer here: http://openocd.gpio.dk/ ) I had no problems building the sources. So far, I had no problems. I've tried the following targets: (All targets with JTAG-Lock-pick Tiny 2, except from the STM32F407 board) * LPC812 * LPC1114 * LPC1768 * LPC1788 * LPC4337 (see note) * STM32F407 with ST-Link v2 * STM32F427 * STM32F429 I had to supply WORKAREASIZE to some of my own .cfg files, but that's all. LPC4337 might fail sometimes; I might have time to investigate this later. (This could be due to a power supply, which is not strong enough, or missing capacitors). I did not succeed in flash-programming the LPC1342, but there have been problems with this chip earlier, so I'm not taking it too seriously. (I did manage to erase the program in it, while attempting to flash-program it, though). So I would say this is a success. It's no doubt the best OpenOCD on the Mac/PPC so far. Love Jens |
From: Paul F. <fer...@gm...> - 2015-05-08 16:26:05
|
Hey Jens, On Fri, May 08, 2015 at 03:39:49PM +0200, Jens Bauer wrote: > So I would say this is a success. It's no doubt the best OpenOCD on the Mac/PPC so far. Thanks, Jens, much appreciated! -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fer...@gm... |
From: Andreas F. <afa...@su...> - 2015-05-08 16:50:51
|
Am 08.05.2015 um 15:39 schrieb Jens Bauer: > Hi all. > > I've built OpenOCD 0.9.0-rc1 on Mac (and as some of you know, I've placed an installer here: http://openocd.gpio.dk/ ) > I had no problems building the sources. > > So far, I had no problems. I've tried the following targets: > > (All targets with JTAG-Lock-pick Tiny 2, except from the STM32F407 board) > > * LPC812 > * LPC1114 > * LPC1768 > * LPC1788 > * LPC4337 (see note) > * STM32F407 with ST-Link v2 > * STM32F427 > * STM32F429 FWIW I saw some initial errors on Linux/arm with the STM32F429I-DISCO using its ST-Link, but flashing worked nonetheless. (Logs to follow.) Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) |
From: Xiaofan C. <xia...@gm...> - 2015-05-15 03:47:39
|
On Sat, May 9, 2015 at 12:50 AM, Andreas Färber <afa...@su...> wrote: > Am 08.05.2015 um 15:39 schrieb Jens Bauer: >> I've built OpenOCD 0.9.0-rc1 on Mac (and as some of you know, >> I've placed an installer here: http://openocd.gpio.dk/ ) >> I had no problems building the sources. >> >> So far, I had no problems. > > FWIW I saw some initial errors on Linux/arm with the STM32F429I-DISCO > using its ST-Link, but flashing worked nonetheless. (Logs to follow.) > I have also tried OpenOCD 0.9.0-rc1 on Mac OS X 10.10 with Mac Mini 2011 (Intel) and no problems with either building or some simple tests with STM32/Amontec JtagKey2. -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2015-05-16 12:55:59
|
On Fri, May 15, 2015 at 11:47 AM, Xiaofan Chen <xia...@gm...> wrote: > I have also tried OpenOCD 0.9.0-rc1 on Mac OS X 10.10 > with Mac Mini 2011 (Intel) and no problems with either > building or some simple tests with STM32/Amontec JtagKey2. > I tried a few STM32 Discovery Board as well, F0 and F3 both are okay (ST-Link V2), VL does not seem to work (ST-Link V1). Even after using the work-around proposed by Paul (#reset_config srst_only; to comment out this line in the board config file), it does not seem to work under Mac OS X. I will try to see if it works under Windows or not. -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2015-05-16 13:18:17
|
On Sat, May 16, 2015 at 8:55 PM, Xiaofan Chen <xia...@gm...> wrote: > On Fri, May 15, 2015 at 11:47 AM, Xiaofan Chen <xia...@gm...> wrote: >> I have also tried OpenOCD 0.9.0-rc1 on Mac OS X 10.10 >> with Mac Mini 2011 (Intel) and no problems with either >> building or some simple tests with STM32/Amontec JtagKey2. >> > > I tried a few STM32 Discovery Board as well, F0 and F3 > both are okay (ST-Link V2), VL does not seem to work > (ST-Link V1). Even after using the work-around proposed > by Paul (#reset_config srst_only; to comment out this line > in the board config file), it does not seem to work under > Mac OS X. I will try to see if it works under Windows or not. I see there is a fix in gerrit and I will give it a try later. jtag/drivers/stlink: SRST issue with stlink-v1 http://openocd.zylin.com/#/c/2761/ -- Xiaofan |
From: Andreas F. <afa...@su...> - 2015-05-17 16:48:29
|
Am 08.05.2015 um 18:50 schrieb Andreas Färber: > Am 08.05.2015 um 15:39 schrieb Jens Bauer: >> Hi all. >> >> I've built OpenOCD 0.9.0-rc1 on Mac (and as some of you know, I've placed an installer here: http://openocd.gpio.dk/ ) >> I had no problems building the sources. >> >> So far, I had no problems. I've tried the following targets: >> >> (All targets with JTAG-Lock-pick Tiny 2, except from the STM32F407 board) >> >> * LPC812 >> * LPC1114 >> * LPC1768 >> * LPC1788 >> * LPC4337 (see note) >> * STM32F407 with ST-Link v2 >> * STM32F427 >> * STM32F429 > > FWIW I saw some initial errors on Linux/arm with the STM32F429I-DISCO > using its ST-Link, but flashing worked nonetheless. (Logs to follow.) andreas@droide:~> openocd -f board/stm32f429discovery.cfg Open On-Chip Debugger 0.9.0-rc1 (2015-04-27-11:50) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD adapter speed: 2000 kHz adapter_nsrst_delay: 100 none separate srst_only separate srst_nogate srst_open_drain connect_deassert_srst Info : Unable to match requested speed 2000 kHz, using 1800 kHz Info : Unable to match requested speed 2000 kHz, using 1800 kHz Info : clock speed 1800 kHz Info : STLINK v2 JTAG v17 API v2 SWIM v0 VID 0x0483 PID 0x3748 Info : using stlink api v2 Info : Target voltage: 2.860946 Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 100ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 300ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 700ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 1500ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 3100ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 6300ms Info : Previous state query failed, trying to reconnect Polling target stm32f4x.cpu failed, trying to reexamine Info : stm32f4x.cpu: hardware has 0 breakpoints, 4 watchpoints Error: mem2array: Read @ 0xe0042004, w=4, cnt=1, failed Runtime Error: /usr/share/openocd/scripts/mem_helper.tcl:6: in procedure 'mmw' in procedure 'mrw' called at file "/usr/share/openocd/scripts/mem_helper.tcl", line 16 at file "/usr/share/openocd/scripts/mem_helper.tcl", line 6 Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 100ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 300ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 700ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 1500ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 3100ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 6300ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 6300ms Info : Previous state query failed, trying to reconnect Error: jtag status contains invalid mode value - communication failure Polling target stm32f4x.cpu failed, trying to reexamine Examination failed, GDB will be halted. Polling again in 6300ms ^C Same errors on Linux/x86_64 with master. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) |