On Thu, Apr 30, 2020 at 3:51 AM Antonio Borneo
wrote:
> Yes,riscv target does not define the function get_gdb_arch(), so
> cannot send the arch value to gdb.
> This should be easy to fix, but there are so many variants of riscv
> that I don't know how to correctly implement it.
>
> Tim,
> any
" , "j. m. norris"
, "openocd-devel"
Verzonden: Donderdag 30 april 2020 13:15:15
Onderwerp: Re: [OpenOCD-devel] Support for GigaDevice microcontrollers
On Thu, Apr 30, 2020 at 01:02:16PM +0200, kristof.mul...@telenet.be wrote:
> It looks like the firmware f
On Thu, Apr 30, 2020 at 01:02:16PM +0200, kristof.mul...@telenet.be wrote:
> It looks like the firmware flashed successfully.
You can use "compare-sections" after "load" to be sure.
> Unfortunately, the led on the board is not blinking. The firmware I
> got from Reuben Townsend should make an
Hi @Paul ,
Thank you very much for your suggestions. I've tried them with the following
results:
C:\beetle_projects\gd32vf103c_start>
"C:/embeetle/gnu_riscv_xpack_64b/bin/riscv-none-embed-gdb.exe"
warning: Couldn't determine a path for the index cache directory.
GNU gdb (xPack GNU RISC-V
On Thu, Apr 30, 2020 at 12:35 PM Paul Fertser wrote:
>
> Hi Kristof,
>
> On Thu, Apr 30, 2020 at 12:19:48PM +0200, kristof.mul...@telenet.be wrote:
> > (gdb) target remote localhost:
>
> I recommend extended-remote always, there's no reason at all to not
> use it. I type "tar ext :"
Hi Kristof,
On Thu, Apr 30, 2020 at 12:19:48PM +0200, kristof.mul...@telenet.be wrote:
> (gdb) target remote localhost:
I recommend extended-remote always, there's no reason at all to not
use it. I type "tar ext :" usually.
> Remote debugging using localhost:
> bfd
orted by this target.
As you can see, the "monitor" command simply doesn't work. It's the first time
this happens to me. I have absolutely no clue how to solve this.
Kind regards,
Kristof Mulier
Van: "Tomas Vanek"
Aan: "kristof mulier"
Cc: "openocd-devel&q
Hi Kristof,
On 29/04/2020 17:34, kristof.mul...@telenet.be wrote:
Hi @jmn
I just got the following reply from Reuben Townsend from GigaDevice:
/ Hi Kristof, the GD-LINK uses the CMSIS-DAP interface/
/ and for the GD32E230 MCU, you can use the stm32f0x.cfg/
/ configuration file.///
Hey Kristof,
On Wed, Apr 29, 2020 at 07:30:33PM +0200, kristof.mul...@telenet.be wrote:
> Do you recommend to use the "tool-openocd-gd32v" from platformio?
I would suggest to give it a try if you're not allergic to using
binary tools. And I have no idea about platformio specifics.
> Or should I
s,
Kristof
- Oorspronkelijk bericht -
Van: "Paul Fertser"
Aan: "kristof mulier"
Cc: "j. m. norris" , "openocd-devel"
Verzonden: Woensdag 29 april 2020 19:13:28
Onderwerp: Re: [OpenOCD-devel] Support for GigaDevice microcontrollers
On Wed, Apr 29, 2020 at 07:59:49PM
On Wed, Apr 29, 2020 at 07:59:49PM +0300, Paul Fertser wrote:
> On Wed, Apr 29, 2020 at 06:53:50PM +0200, kristof.mul...@telenet.be wrote:
> > Error: flash driver 'gd32vf103' not found
>
> I guess you want "tool-openocd-gd32v" from platformio. This driver is
> not in upstream OpenOCD.
I did some
Hello,
On Wed, Apr 29, 2020 at 06:53:50PM +0200, kristof.mul...@telenet.be wrote:
> Error: flash driver 'gd32vf103' not found
I guess you want "tool-openocd-gd32v" from platformio. This driver is
not in upstream OpenOCD.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html)
ristof mulier"
Cc: "openocd-devel"
Verzonden: Woensdag 29 april 2020 18:10:40
Onderwerp: Re: [OpenOCD-devel] Support for GigaDevice microcontrollers
Kristof,
The CMSIS-DAP related bits in that file should be fine. However, there are
other
things in the file that are s
Kristof,
The CMSIS-DAP related bits in that file should be fine. However, there are other
things in the file that are specific to the ARM, e.g, flash and PLL bits. So you
can't
use the file as-is. You'll have to do some modifications for the RISCV (if any).
As far as combining it, it's just a
57:25
Onderwerp: Re: [OpenOCD-devel] Support for GigaDevice microcontrollers
Kristof,
Can you send a link for the RiscV board documentation? I might be able to help
as I've work with other RiscV boards.
Regards
jmn
___
OpenOCD-devel mailing
Kristof,
Can you send a link for the RiscV board documentation? I might be able to help
as I've work with other RiscV boards.
Regards
jmn
___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
Hi,
We received a couple of boards from GigaDevice (one of them is RiscV-based):
GD32VF103C-START (MCU: GD32VF103C ) RiscV -based
GD32E231C-START (MCU: GD32E231C ) ARM -based
GD32E232K-START (MCU: GD32E232K ) ARM -based
GD32E230C-EVAL (MCU: GD32E230C8) ARM-based
OpenOCD doesn't seem to
17 matches
Mail list logo
