@Yu-Mingjin : thank you so much for taking the time to report on this. Using your suggestions, I successfully compiled both examples.

@Yudan Thank you. Just for now: could you at least confirm my issue? Best Thierry

I tried with the other example app (RAWDATA). Still no luck. Can someone else please try to compile the current state of the project for the "OpenRTK330L" board.
The error log for the my attempt with the RAWDATA app is here
https://gist.github.com/thierry3000/ce581dced0c80ae08d0068da1c3a0364

I am unable to build the latest firmware from source provided at https://github.com/Aceinna/platform-aceinna_imu. I cloned the respository, changed the directory into examples/OpenRTK330LI/RTK_INS, modified the platform.ini ([env:OpenRTK330LI] and board = OpenRTK330L) followed by executing pio run.

I described the exact output here. Did someone successfully build the firmware from source? If yes, could you please point out my mistake.

It turned out that I read the initial image with a size box of 0x200000 instead of 0x100000. Fortunately, I restored the original image after some byte modifications. This solved my issue.

I suffered a failure during an upload with Visual Studio Code. Since nothing worked as before after the failure, I finally decided for a "Full chip erase" with STM32 ST-LINK Utility.

After erasing, I successfully flashed the bootloader with "OpenRTK330L_Bootloader_v1.1.1.bin" as documented in the tutorials. Unfortunately I am now stuck here! As also suggested by the tutorials, I created an emergency backup of the shipped image. Obviously I must have done something wrong since my emergency backup is not flashing with the comment "File size bigger than the flash memory size".

First questing:
is there a way to flash one of the default firmware (e.g. OpenRTK330L_GNSS_RTK_INS_v23.01.bin) to the EVK? If yes, how to accomplish that?

Currently I face the green LED on the EVK flashing and I cannot communicate with the USB bus. I tried on Ubuntu 18.04 and Windows 10 with the python-openimu tool. Booth worked before the chip erase. Now the "--console-log" output repeats as shown below instead of connecting.

Second question:
How to connect with USB.

ans-devices.exe --console-log --cli
2021-01-28 10:11:48,882 - INFO: try to use last connected port COM24 460800
2021-01-28 10:11:53,031 - INFO: start to connect serial port
2021-01-28 10:11:53,031 - INFO: try to use connected port COM24 in history
2021-01-28 10:11:53,031 - INFO: try to use connected port COM25 in history
2021-01-28 10:11:53,031 - INFO: try to use connected port COM26 in history
2021-01-28 10:11:53,031 - INFO: try to use connected port COM27 in history
2021-01-28 10:11:53,031 - INFO: try COM25:460800
2021-01-28 10:11:53,131 - INFO: try COM26:460800
2021-01-28 10:11:53,147 - INFO: try COM27:460800
2021-01-28 10:11:57,994 - INFO: try COM24:460800
2021-01-28 10:11:59,251 - INFO: try COM27:115200
2021-01-28 10:11:59,267 - INFO: try COM26:115200
2021-01-28 10:12:01,200 - INFO: try COM25:115200
2021-01-28 10:12:03,850 - INFO: try COM24:115200
2021-01-28 10:12:04,923 - INFO: try COM27:57600
2021-01-28 10:12:05,039 - INFO: try COM26:57600
2021-01-28 10:12:06,692 - INFO: try COM25:57600
2021-01-28 10:12:09,540 - INFO: try COM24:57600
2021-01-28 10:12:10,506 - INFO: try COM27:230400
2021-01-28 10:12:10,590 - INFO: try COM26:230400
2021-01-28 10:12:12,536 - INFO: try COM25:230400
2021-01-28 10:12:38,194 - INFO: try COM27:38400
2021-01-28 10:12:38,364 - INFO: try COM26:38400
2021-01-28 10:12:38,864 - INFO: try COM24:230400
2021-01-28 10:12:39,215 - INFO: try COM25:38400

Any help would be highly appreciated.