Hello,
appended simple patch adds the definition for the STEVAL-PCC010V2 Board
withe the STM32F207. At least the detection works:
Info : JTAG tap: stm32f2xxx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part:
0xba00, ver: 0x4)
Info : JTAG tap: stm32f2xxx.bs tap/device found: 0x06411041 (mfg:
On Thu, Sep 1, 2011 at 11:32 AM, Uwe Bonnes wrote:
Hello,
appended simple patch adds the definition for the STEVAL-PCC010V2 Board
withe the STM32F207. At least the detection works:
+# This is an STM32 eval board with a single STM32F10x (128KB) chip.
+#
Hello,
appended simple patch adds the definition for the STEVAL-PCC010V2 Board
withe the STM32F207. At least the detection works:
Info : JTAG tap: stm32f2xxx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part:
0xba00, ver: 0x4)
Info : JTAG tap: stm32f2xxx.bs tap/device found: 0x06411041 (mfg:
On Thu, Sep 1, 2011 at 3:44 PM, Uwe Bonnes wrote:
appended simple patch adds the definition for the STEVAL-PCC010V2 Board
withe the STM32F207. At least the detection works:
Sorry to nitpick again, but the card model is called ...010 and...
tcl/board/steval_pcc0102v2.cfg | 8
1
Hello,
appended simple patch adds the definition for the STEVAL-PCC010V2 Board
withe the STM32F207. At least the detection works:
Info : JTAG tap: stm32f2xxx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part:
0xba00, ver: 0x4)
Info : JTAG tap: stm32f2xxx.bs tap/device found: 0x06411041 (mfg:
On Thu, Sep 1, 2011 at 4:33 PM, Uwe Bonnes wrote:
appended simple patch adds the definition for the STEVAL-PCC010V2 Board
withe the STM32F207. At least the detection works:
( this time with the comment corrected + SI unit etc)
It was the file name that I thought was wrong, not the comment.
Hello,
appended simple patch adds the definition for the STEVAL-PCC010V2 Board
withe the STM32F207. At least the detection works:
Info : JTAG tap: stm32f2xxx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part:
0xba00, ver: 0x4)
Info : JTAG tap: stm32f2xxx.bs tap/device found: 0x06411041 (mfg:
Hi,
due to the coming SWD support, I found that the arm_adi_v5 has
dependencies to the jtag subsystem. To preserve the performance I
changed the interface to the transport layer. Both, dap_queue_ap_write
and dap_queue_ap_read gets a pointer to a data array not a single value.
The adi_v5_jtag now
I can take a look at this as I'm finishing to solder a hardware that I
will finish the SWD implementation in upcoming days, but I would
rather not change interface/jtag/transport layer until SWD is done.
When its done and working then we can change internals, otherwise we
will have two different
