New FreedomStudio


(Donnie Agema) #1

I just installed the new FreedomStudio on Windows7_64, including the latest Java release, and get the following error when trying to build Blinky:

23:31:05 **** Rebuild of configuration Debug for project Blinky ****
Info: Internal Builder is used for build
"C:\SF\FS\FreedomStudio\bin\riscv64-unknown-elf-gcc" -mabi=ilp32 -g -gdwarf-2 -march=rv32imac -DUSE_PLIC -DUSE_M_TIME “-IG:\SF\FS\FreedomStudio\eclipse\workspace\Blinky\bsp\env\freedom-e300-hifive1” “-IG:\SF\FS\FreedomStudio\eclipse\workspace\Blinky\bsp\drivers” “-IG:\SF\FS\FreedomStudio\eclipse\workspace\Blinky\bsp\include” “-IG:\SF\FS\FreedomStudio\eclipse\workspace\Blinky\bsp\env” -I/toolchain/lib/gcc/riscv32-unknown-elf/6.1.0/include -I/toolchain/lib/gcc/riscv32-unknown-elf/6.1.0/include-fixed -I/toolchain/riscv32-unknown-elf/include -O2 -ffunction-sections -fdata-sections -Wall -c -include sys/cdefs.h -fno-builtin-printf -o “src\interrupts.o” "…\src\interrupts.c"
Cannot run program “C:\SF\FS\FreedomStudio\bin\riscv64-unknown-elf-gcc” (in directory “G:\SF\FS\FreedomStudio\eclipse\workspace\Blinky\Debug”): CreateProcess failed, error=216

Error: Program “C:\SF\FS\FreedomStudio\bin\riscv64-unknown-elf-gcc” not found in PATH
PATH=[/C:/SF/FS/FreedomStudio/bin;/Users/drew/Tools/FS_Testing/FreedomStudio2//bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/drew/Tools/freedom-e-sdk-mac/toolchain/bin]

It seem to be saying that the executables provided in the package are not 64-bit. Am I wrong?


(Drew) #2

Hi Donnie,

Thanks for reporting this. The Windows version of the Freedom Studio isn’t fully supported at this time. Perhaps it should have been tagged as Alpha to differentiate it from Linux and Mac. Over the following weeks we plan to continue creating examples and documentation for Freedom Studio and hopefully work most of the kinks out in the Windows version as well.

For the time being, it is recommended to use either the Mac or Linux versions. You may still have to manually set paths for them, but they are considerably more stable than the Windows version.

Having said that, the Windows version of the toolchain binaries should be a bit more stable than Freedom Studio itself. They are included with Freedom Studio (in the SiFive folder) and also available as standalone on our website here.

I’m sorry for the inconvenience, please hold out for a few more weeks until we can get things resolved. In the meantime, we are here to answer your questions.

Drew


(Donnie Agema) #3

No problem. I was curious to see the new Freedom Studio and the Windows version was the easiest for me to just jump into. I will try out the Linux version toady.

Thanks for the help.:smiley:


(Donnie Agema) #4

I am now trying the Linux version on an Ubuntu VM. I can’t seem to find the “File->Import” path within the UI:

That at least did work in the Windows version.

Also, double-clicking the “Open Freedom Studio Documetnation” (sic) causes a Java crash.

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x00007fa48cfc52b7, pid=14031, tid=0x00007fa51952c700

JRE version: OpenJDK Runtime Environment (8.0_121-b13) (build 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13)

Java VM: OpenJDK 64-Bit Server VM (25.121-b13 mixed mode linux-amd64 compressed oops)

Problematic frame:

C [libgdk-x11-2.0.so.0+0x4e2b7] gdk_display_open+0x57

Failed to write core dump. Core dumps have been disabled. To enable core dumping, try “ulimit -c unlimited” before starting Java again

If you would like to submit a bug report, please visit:

http://bugreport.java.com/bugreport/crash.jsp

The crash happened outside the Java Virtual Machine in native code.

See problematic frame for where to report the bug.

--------------- T H R E A D ---------------

Current thread (0x00007fa51000a000): JavaThread “main” [_thread_in_native, id=14032, stack(0x00007fa51942c000,0x00007fa51952d000)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x0000000000000114

Registers:
RAX=0x0000000000000000, RBX=0x00007fa5123a6800, RCX=0x0000000000000000, RDX=0x0000000000000000
RSP=0x00007fa519529db0, RBP=0x00007fa519529dc0, RSI=0x00007fa48cfc50b0, RDI=0x00007fa5123a6800
R8 =0x00007fa51080cd40, R9 =0x0000000000000000, R10=0x0000000000000008, R11=0x000000000000000b
R12=0x00007fa48dafe280, R13=0x00007fa5101e7350, R14=0x00007fa512802300, R15=0x0000000000000001
RIP=0x00007fa48cfc52b7, EFLAGS=0x0000000000010246, CSGSFS=0x0000000000000033, ERR=0x0000000000000006
TRAPNO=0x000000000000000e


(Megan A. Wachs) #5

Donnie, thanks for being a beta tester!

I was able to reproduce the Java crash issue when clicking on the "Open Documentation " link, so we’ll look into that.

As far as the File->Import, in my version Ubuntu I have to hover the mouse over the very top of the screen (not the Freedom Studio window) in order to see the menu items. Then, File appears and I am able to do File->Import.


(Donnie Agema) #6

The hovering works for m too. Maximizing the Freedom Studio window makes it slightly more intuitive.:wink:


(Donnie Agema) #7

When I try to run debug, I get this error:

I wonder if is caused by the -version parameter. The openocd binary seems to accept -v but not -version:


(Drew) #8

Hi Donnie,

It looks like you set the GDB path to your OpenOCD binary. Try manually setting the paths using the Browse buttons and make sure that the top dialog points to OpenOCD, and the bottom points to GDB.

We are adding Freedom Studio versions of the Freedom-E-SDK examples now and should have the first batch ready to go early next week. For now you can see what we are doing on the freedom-studio branch of the Freedom-E-SDK repo.

The process will be:

  • Clone freedom-e-sdk (freedom studio branch). no need to recursive clone as we are inlcuding the toolchain with Freedom Studio.

  • Open Freedom Studio and pick a workspace location

  • Click File->Import->Existing Projects into Workspace

  • Select the root folder -> Freedom-E-SDK/FreedomStudio/Boad/

  • Select all projects and then Import

  • Build the wrap project first to create wrapped libraries, then you can build all projects

  • If the build fails, change toolchain path from the Quick Launcher to point to the FreedomStudio/bin directory. And also set the Freedom Directory from the Quick Launcher.

All of this will be documented, and hopefully much smoother soon. Until then feel free to use the forum to continue to ask questions. The more eyes filling bugs, the better the product will be :wink:


(Donnie Agema) #9

Yes, that is how I understood item 10 of the quick start guide. I am not a proficient Linux user - how do I find the path to the GDB executable? Show configuration gave me some hints, but the paths displayed were of no help:


(Megan A. Wachs) #10

donnie, looks like your GDB executable would be :

/home/donnie/Downloads/FreedomStudio/SiFive/riscv64-unknown-elf-gcc<…>/bin/riscv64-unknown-elf-gdb

If you use the ‘Browse…’ button you should get a GUI to help you find the file, starting from your Downloads/ folder.


Freedom Studio windows version problem
(Donnie Agema) #11

That works, Megan.

Thanks. :smile: