Using Ubuntu 18.04.4 LTS 64Bit OS.
I built the riscv toolchain from https://github.com/riscv/riscv-gnu-toolchain master branch using --enable-multilib --with-arch=rv64imac --with-abi=lp64 configure option.
I built the freedom with default Arty for 35T FPGA board and the mcs file was generated and programmed on Arty 35T board using vivado 2019.2 successfully.
When i reset (or reconnect the USB), i am able to see the LD4, LD5, LD6 light up.
When i press the BTN3, the LD6 is off
When i press the RESET button, the LD4 is off.
Hope the programming is done correctly.
However i am unable to see any sifive logo on the miniterm of /dev/ttyUSB1 even after pressing RESET or reconnecting the USB.
Nothing is displaying on the miniterm.
In freedom-e-sdk, when after compiling using “make PROGRAM=sifive-welcome TARGET=freedom-e310-arty software”, i tried to upload using “make PROGRAM=sifive-welcome TARGET=freedom-e310-arty upload” command. I am getting the following error
(since i am using the arty 35T onboard USB-JTAG FTDI interface itself[i don’t have the Olimex JTAG adapter], i changed “set connection tunnel” in bsp/freedom-e310-arty/openocd.cfg)
/opt/tools/riscv_multilib/bin/riscv64-unknown-elf-size /home/sathish/sifive/freedom-e-sdk/software/sifive-welcome/debug/sifive-welcome.elf
text data bss dec hex filename
23974 1924 3256 29154 71e2 /home/sathish/sifive/freedom-e-sdk/software/sifive-welcome/debug/sifive-welcome.elf
scripts/upload --elf /home/sathish/sifive/freedom-e-sdk/software/sifive-welcome/debug/sifive-welcome.elf --openocd /home/sathish/software/riscv-openocd/bin/openocd --gdb /opt/tools/riscv_multilib/bin/riscv64-unknown-elf-gdb --openocd-config bsp/freedom-e310-arty/openocd.cfg
Open On-Chip Debugger 0.10.0+dev-00863-g4579dd935-dirty (2020-07-05-22:40)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Using JTAG tunnel
Info : auto-selecting first available session transport “jtag”. To override use 'transport select '.
Info : Nested Tap based Bscan Tunnel Selected
Info : ftdi: if you experience problems at higher adapter clocks, try the command “ftdi_tdo_sample_edge falling”
Info : clock speed 10000 kHz
Info : JTAG tap: riscv.cpu tap/device found: 0x0362d093 (mfg: 0x049 (Xilinx), part: 0x362d, ver: 0x0)
Error: Unsupported DTM version 9. (dtmcontrol=0x9)
Info : Listening on port 3333 for gdb connections
Error: Target not examined yet
localhost:3333: Connection timed out.
“monitor” command not supported by this target.
“monitor” command not supported by this target.
You can’t do that when your target is `exec’
“monitor” command not supported by this target.
“monitor” command not supported by this target.
$
Please any suggestion ?