[MyAmigo]

OK

Thanks for your help.

[MyAmigo]

Thank you for the suggestion.

I had installed J-Link V6.48b previously so I updated to the latest beta release (V6.61d) for this trial. I assume that this is the J-Link stub you referred to… https://www.segger.com/downloads/jlink/JLink_Windows_beta.exe

My settings with this installed are shown here: https://photos.app.goo.gl/dtGjtymNYn8a2ARM7

When I run the connection test I get a failure…

https://photos.app.goo.gl/dX3c8aQbbqeqhWHx5

The failure messages are…

Connecting to target...
ERROR: The connected J-Link does not support selecting another hart/core than 0 for RISC-V
Specific core setup failed.
ERROR: Could not connect to target.

I tried targetting the RISCV, RV32 & RV64 devices and different clock settings… Same result in each case.

I can switch back to the OpenOCD debugger and K210 target and things are as they should be…

https://photos.app.goo.gl/szNtbeawdKrPx5Zx8

Do you have any further suggestions?

Thank you

 

[MyAmigo]

I was already setup for OpenOCD debugging using tools from Kendyte’s site.

I wish I had tried that first. Hardware registers are unsupported 🙁

cmdlet MCU_debug.ps1 at command pipeline position 1
Supply values for the following parameters:
app: apu
GNU gdb (GDB) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=i686-w64-mingw32 --target=riscv64-unknown-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from apu...done.
Remote debugging using 127.0.0.1:3333
warning: Target-supplied registers are not supported by the current architecture
0x0000000000000400 in ?? ()
(gdb)

 

 

[MyAmigo]

Just a little more info to go with this to help resolve the problem.

I dumped memory in the region of interest andVisualGDM shows ????? for the entire address space from 0x52000000 – 0x52FFFFFF.

• 0x52000000: https://photos.app.goo.gl/mZkqCchNR8AtaQ59A
• 0x50300000: https://photos.app.goo.gl/oCTc9BdndQ9jzkjP8

This is also seems to be true for the range 0x50400000 – 0x50500000

This should help to narrow down the cause.

• This reply was modified 4 years, 9 months ago by MyAmigo.

[MyAmigo]

I think you nailed it.

I tested several register locations at the same time. They returned the expected values and the test variables retained that value when reasigned to themselves. A bug in the K210 port of OpenOCD is the likely reason.

Thank you!

 

 

 

[MyAmigo]

Thanks for the crazy-fast input!

x/1x 0x50250200

yields…

x/1x 0x50250200
&”x/1x 0x50250200\n”
0x50250200: 0xffffffff
OK

… and that’s the same that I see with the “Hardware Register ” view. Other nearby addresses return the same result.

When I run the monitor command I get all zeroes at that address…

0x50250200: 00000000

• This reply was modified 4 years, 9 months ago by MyAmigo.

[Author]

Posts