I think the way to create virtual project did matter.
Below is my working setup

I hit the same issue in Win10 and the root cause is I have 2 GNU ARM Toolchain installed in Win10. The way I fixed it is to change TC_PATH/QORC_TC_PATH in config.mk like below #Override with your own tool direcoty #export TC_PATH=C:\Program Files (x86)\GNU Tools ARM Embedded\7 2017-q4-major\bin expo...

Okay. I just found that I can use Windows to program the image and also use JLINK to recover the board.

I am using WIN10 running vmware. In Windows, i can see VMware USB device has been recognized by Windows. But cannot detect by Ubuntu in VM. I also tried ubuntu20.04 in virtualbox. USB extention pack has been installed and it can recognized Merced board as well. Still cannot make it work for QuickFea...

Yes. System is reboot and before plug in the board, use apio drivers --serial-enable to enable. The log shows phil@ubuntu:~$ sudo apio drivers --serial-enable [sudo] password for phil: Configure Serial drivers for FPGA Already enabled And check the ttyACM again still no good. ls /dev/ttyA* ls: canno...

I still have problem to make it work on VM workstation 15 player for Ubuntu20.04.

For apio install, I have to use
pip3 install -U apio
instead of
sudo apt install apio

After the apio driver is enabled, still cannot see device in /dev/ttyACM0.

BTW, the VM can detect Merced board.

Any update on this?

There is no qorcsdk/qf_apps/qf_helloworldsw/GCC_projects
instead
qorc-sdk/qf_apps/qf_helloworldsw/GCC_Project

In Working.with.Zephyr.pdf, it mentioned a boot loader document to flash image. Where can I find that? Executing: It generates the output binary in elf and bin formats in samples/hello_world/build/zephyr. Follow the instructions in boot loader document to flash the M4 image bin file and execute. Opt...

You are right. There is error I ignore earlier while doing pip3 install –-user -r ~/zephyrproject/zephyr/scripts/requirements.txt ERROR: Invalid requirement: '–-user' Then I realized I am using "copy and paste" from the document which cause "--user" became "–-user" Doc ...