Silicon Labs devkit_xg24_brd2601b won't build

[MHVUT]

Silicon Labs - Issues rebuilding the .bin file for the dev_kit_xg25_brd2601b. Followed the Adafruit guide and the SiLabs READ.md. Trying to build with Ubuntu Linux 22.04.2 (x86_64 emulation) on a Mac with the Parallels VM version 19.2.1. This is the entire build output from the ‘make BOARD=devkit_xg24_brd2601b’ cli command.

The guides have been followed exactly with a new clean VM.

The Adafruit guide has the 'make BOARD=circuitplayground_express' at the end of their documentation which works fine, no issues. The build problem looks to be specific to the SiLabs port. The 'make fetch-port-submodules' has been done for the SiLabs port.

parallels@ubuntu-linux-22-04-02-desktop:~/circuitpython/ports/silabs$ make BOARD=devkit_xg24_brd2601b
- Verbosity options: any combination of "steps commands rules", as `make V=...` or env var BUILD_VERBOSE
- Verbosity options: any combination of "steps commands rules", as `make V=...` or env var BUILD_VERBOSE
SLC generates project
sdk was set to /home/parallels/circuitpython/ports/silabs/gecko_sdk
The extension /home/parallels/circuitpython/ports/silabs/cp_efr32_extension/cp_efr32.slce is already trusted at the requested level. Nothing to do.
The sdk /home/parallels/circuitpython/ports/silabs/gecko_sdk/ is already trusted at the requested level. Nothing to do.
Found valid toolchain component toolchain_gcc for gcc
Generation location: /home/parallels/circuitpython/ports/silabs/build-devkit_xg24_brd2601b
Generation: Starting AC generation for ucProject in project circuitpython_efr32: Fri Feb 09 19:54:24 UTC 2024
Project is already viable -- no choices need be made.
Problems generating template files from component: bluetooth_stack - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: bluetooth_stack - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: board_control - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: cmsis_core - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: component_catalog - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: device_init_clocks - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: event_handler - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: event_handler - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: i2cspm_core - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: i2cspm_core - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: mbedtls_config - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: mbedtls_config - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: psa_crypto_config - Potential jar issue: python script did not properly register a template generator
Problems generating template files from component: toolchain_gcc - Potential jar issue: python script did not properly register a template generator
Generation issue: com.silabs.ss.framework.uc.core.api.exception.MultiException: Multi-Exceptions available:
  Multi-Exceptions available:
  Problems generating template files from component: bluetooth_stack - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: bluetooth_stack - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: board_control - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: cmsis_core - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: component_catalog - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: device_init_clocks - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: event_handler - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: event_handler - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: i2cspm_core - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: i2cspm_core - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: mbedtls_config - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: mbedtls_config - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: psa_crypto_config - Potential jar issue: python script did not properly register a template generator
  Problems generating template files from component: toolchain_gcc - Potential jar issue: python script did not properly register a template generator
Generation to /home/parallels/circuitpython/ports/silabs/build-devkit_xg24_brd2601b for circuitpython_efr32 did not succeed.
Slc-cli:
JVM terminated. Exit code=255
/home/parallels/.sdkman/candidates/java/current/bin/java
-Dosgi.requiredJavaVersion=11
-Dosgi.console=none
-Xms40m
-Declipse.p2.unsignedPolicy=allow
-Djava.net.preferIPv4Stack=true
-Declipse.exitdata=
-Duc.workingdirectory=/home/parallels/circuitpython/ports/silabs
-Dslc_consolecolour=false
-Dslc_consolewidth=185
-jar /home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/bin/slc-cli//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar
-os linux
-ws gtk
-arch x86_64
-launcher /home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/bin/slc-cli/slc-cli
-name Slc-cli
--launcher.library /home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/bin/slc-cli//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.2.400.v20211117-0650/eclipse_11600.so
-startup /home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/bin/slc-cli//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar
--launcher.appendVmargs
-exitdata 10002 generate
-name=circuitpython_efr32 circuitpython_efr32.slcp
--sdk gecko_sdk
--with brd2601b
-tlcn gcc
-d=build-devkit_xg24_brd2601b
-vm /home/parallels/.sdkman/candidates/java/current/bin/java
-vmargs
-Dosgi.requiredJavaVersion=11
-Dosgi.console=none
-Xms40m
-Declipse.p2.unsignedPolicy=allow
-Djava.net.preferIPv4Stack=true
-Declipse.exitdata=
-Duc.workingdirectory=/home/parallels/circuitpython/ports/silabs
-Dslc_consolecolour=false
-Dslc_consolewidth=185
-jar /home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/bin/slc-cli//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar 
make[1]: *** [Makefile:177: slc-generate] Error 255
make: *** [Makefile:142: build-devkit_xg24_brd2601b/circuitpython_efr32.Makefile] Error 2

[dhalbert]

@silabs-ChatNguyen I don't know what the issue might be in the build above. We asked @MHVUT to post here so we could ping you. My own build environment is working, but a clean build in a new environment should too. Do you know what the issue might be?

Are there Silabs forums that might also be a place to ask this question, or is this the best route? Thanks.

[MHVUT]

Hi @silabs-ChatNguyen Would it be possible to get a response for this issue and help work out a solution? Thanks so much.

[dhalbert]

@MHVUT I'm wondering, which version of Java are you using? I have

$ java --version
openjdk 11.0.21 2023-10-17
OpenJDK Runtime Environment (build 11.0.21+9-post-Ubuntu-0ubuntu122.04)
OpenJDK 64-Bit Server VM (build 11.0.21+9-post-Ubuntu-0ubuntu122.04, mixed mode, sharing)

[silabs-ChatNguyen]

@MHVUT I'm wondering, which version of Java are you using? I have

$ java --version
openjdk 11.0.21 2023-10-17
OpenJDK Runtime Environment (build 11.0.21+9-post-Ubuntu-0ubuntu122.04)
OpenJDK 64-Bit Server VM (build 11.0.21+9-post-Ubuntu-0ubuntu122.04, mixed mode, sharing)

Sorry for the late reply. I was just wrapping up the Lunar New Year holiday.
I think this issue due to wrong java version. Code generation tool are using java 11.

[MHVUT]

Thanks guys for the support. The SiLabs UG520 app note states in section 2.1 for requirements…  I actually had installed this version based on the UG520 app note of requiring version 17 or higher... openjdk 21.0.2 2024-01-16 LTS OpenJDK Runtime Environment Temurin-21.0.2+13 (build 21.0.2+13-LTS) OpenJDK 64-Bit Server VM Temurin-21.0.2+13 (build 21.0.2+13-LTS, mixed mode, sharing) Per the comments I used sdkman to install and set the following version as the default…  Now confirmed as the version in use… openjdk 11.0.21 2023-10-17 LTS OpenJDK Runtime Environment Corretto-11.0.21.9.1 (build 11.0.21+9-LTS) OpenJDK 64-Bit Server VM Corretto-11.0.21.9.1 (build 11.0.21+9-LTS, mixed mode) But I still get the same problem. So my question is exactly which version of Java should be installed? Thanks, JT

…

On Feb 20, 2024, at 7:46 AM, Nguyen Van Chat ***@***.***> wrote: @MHVUT <https://github.com/MHVUT> I'm wondering, which version of Java are you using? I have $ java --version openjdk 11.0.21 2023-10-17 OpenJDK Runtime Environment (build 11.0.21+9-post-Ubuntu-0ubuntu122.04) OpenJDK 64-Bit Server VM (build 11.0.21+9-post-Ubuntu-0ubuntu122.04, mixed mode, sharing) Sorry for the late reply. I was just wrapping up the Lunar New Year holiday. I think this issue due to wrong java version. Code generation tool are using java 11. — Reply to this email directly, view it on GitHub <#8897 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFV6A6BFXJOXRRMG3YGRZNDYUTANVAVCNFSM6AAAAABDCADXE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJUGUYDEMZWGY>. You are receiving this because you were mentioned.

[silabs-ChatNguyen]

I am using default-jdk of ubuntu 22.04
openjdk version "11.0.21" 2023-10-17
OpenJDK Runtime Environment (build 11.0.21+9-post-Ubuntu-0ubuntu122.04)
OpenJDK 64-Bit Server VM (build 11.0.21+9-post-Ubuntu-0ubuntu122.04, mixed mode, sharing)

Could you help to run below cmd in your side:
cd /port/silabs/
make BOARD=devkit_xg24_brd2601b clean
make BOARD=devkit_xg24_brd2601b slc-generate

[MHVUT]

See output log for ‘clean’ and ’slc-generate’ commands as requested. I have posted the full output log here in case it provides more information that may be useful to understand the problem. ***@***.***:~/circuitpython/ports/silabs$ make BOARD=devkit_xg24_brd2601b clean - Verbosity options: any combination of "steps commands rules", as `make V=...` or env var BUILD_VERBOSE rm -rf build-devkit_xg24_brd2601b ***@***.***:~/circuitpython/ports/silabs$ make BOARD=devkit_xg24_brd2601b slc-generate - Verbosity options: any combination of "steps commands rules", as `make V=...` or env var BUILD_VERBOSE SLC generates project sdk was set to /home/parallels/circuitpython/ports/silabs/gecko_sdk The extension /home/parallels/circuitpython/ports/silabs/cp_efr32_extension/cp_efr32.slce is already trusted at the requested level. Nothing to do. The sdk /home/parallels/circuitpython/ports/silabs/gecko_sdk/ is already trusted at the requested level. Nothing to do. Found valid toolchain component toolchain_gcc for gcc Generation location: /home/parallels/circuitpython/ports/silabs/build-devkit_xg24_brd2601b Generation: Starting AC generation for ucProject in project circuitpython_efr32: Tue Feb 20 09:07:14 PST 2024 Project is already viable -- no choices need be made. Problems generating template files from component: bluetooth_stack - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: bluetooth_stack - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: board_control - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: cmsis_core - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: component_catalog - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: device_init_clocks - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: event_handler - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: event_handler - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: i2cspm_core - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: i2cspm_core - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: mbedtls_config - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: mbedtls_config - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: psa_crypto_config - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: toolchain_gcc - Potential jar issue: python script did not properly register a template generator Generation issue: com.silabs.ss.framework.uc.core.api.exception.MultiException: Multi-Exceptions available: Multi-Exceptions available: Problems generating template files from component: bluetooth_stack - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: bluetooth_stack - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: board_control - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: cmsis_core - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: component_catalog - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: device_init_clocks - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: event_handler - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: event_handler - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: i2cspm_core - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: i2cspm_core - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: mbedtls_config - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: mbedtls_config - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: psa_crypto_config - Potential jar issue: python script did not properly register a template generator Problems generating template files from component: toolchain_gcc - Potential jar issue: python script did not properly register a template generator Generation to /home/parallels/circuitpython/ports/silabs/build-devkit_xg24_brd2601b for circuitpython_efr32 did not succeed. Slc-cli: JVM terminated. Exit code=255 /home/parallels/.sdkman/candidates/java/current/bin/java -Dosgi.requiredJavaVersion=11 -Dosgi.console=none -Xms40m -Declipse.p2.unsignedPolicy=allow -Djava.net.preferIPv4Stack=true -Declipse.exitdata= -Duc.workingdirectory=/home/parallels/circuitpython/ports/silabs -Dslc_consolecolour=false -Dslc_consolewidth=172 -jar /home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/bin/slc-cli//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar -os linux -ws gtk -arch x86_64 -launcher /home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/bin/slc-cli/slc-cli -name Slc-cli --launcher.library /home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/bin/slc-cli//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.2.400.v20211117-0650/eclipse_11600.so -startup /home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/bin/slc-cli//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar --launcher.appendVmargs -exitdata 10021 generate -name=circuitpython_efr32 circuitpython_efr32.slcp --sdk gecko_sdk --with brd2601b -tlcn gcc -d=build-devkit_xg24_brd2601b -vm /home/parallels/.sdkman/candidates/java/current/bin/java -vmargs -Dosgi.requiredJavaVersion=11 -Dosgi.console=none -Xms40m -Declipse.p2.unsignedPolicy=allow -Djava.net.preferIPv4Stack=true -Declipse.exitdata= -Duc.workingdirectory=/home/parallels/circuitpython/ports/silabs -Dslc_consolecolour=false -Dslc_consolewidth=172 -jar /home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/bin/slc-cli//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar make: *** [Makefile:177: slc-generate] Error 255

…

On Feb 20, 2024, at 8:54 AM, Nguyen Van Chat ***@***.***> wrote: I am using default-jdk of ubuntu 22.04 openjdk version "11.0.21" 2023-10-17 OpenJDK Runtime Environment (build 11.0.21+9-post-Ubuntu-0ubuntu122.04) OpenJDK 64-Bit Server VM (build 11.0.21+9-post-Ubuntu-0ubuntu122.04, mixed mode, sharing) Could you help to run below cmd in your side: cd /port/silabs/ make BOARD=devkit_xg24_brd2601b clean make BOARD=devkit_xg24_brd2601b slc-generate — Reply to this email directly, view it on GitHub <#8897 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFV6A6GHLULH3BGYL7ILWULYUTIKXAVCNFSM6AAAAABDCADXE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJUGYZTQNBZGY>. You are receiving this because you were mentioned.

[silabs-ChatNguyen]

I am not sure about your build environment.
Can you setup and build with docker ubuntu:22.04?
I will try build a docker environment and provide to you.

[MHVUT]

OK I think I have docker build setup. I am way out of my comfort zone here 8-)). I am new to Linux just because that appears to be the only way to build Circuit Python. So not really sure what I am going at this stage. Please send the docker environment and I’ll try to use it. Thanks,

…

On Feb 21, 2024, at 7:01 AM, Nguyen Van Chat ***@***.***> wrote: I am not sure about your build environment. Can you setup and build with docker ubuntu:22.04? I will try build a docker environment and provide to you. — Reply to this email directly, view it on GitHub <#8897 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFV6A6BUHYERZ7LZWJVPOJTYUYD25AVCNFSM6AAAAABDCADXE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWHA2TANBZHA>. You are receiving this because you were mentioned.

[MHVUT]

So I decided to try something completely different rather than trying to fix the current Ubuntu 22.04.2 (x86_64 emulation) with Parallels on my Mac. I started a completely new VM but this time using Ubuntu 22.04.2 ARM64 to see if that makes any difference. I followed the Adafruit notes as defined here… https://learn.adafruit.com/building-circuitpython/linux Building CircuitPython learn.adafruit.com and here… https://docs.circuitpython.org/en/latest/ports/silabs/README.html#prerequisites Here is the status… ***@***.***:~/circuitpython/ports/silabs$ java --version openjdk 11.0.21 2023-10-17 OpenJDK Runtime Environment (build 11.0.21+9-post-Ubuntu-0ubuntu122.04) OpenJDK 64-Bit Server VM (build 11.0.21+9-post-Ubuntu-0ubuntu122.04, mixed mode) ***@***.***:~/circuitpython/ports/silabs$ python3 --version Python 3.10.12 ***@***.***:~/circuitpython/ports/silabs$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/home/parallels/bin/gcc-arm-none-eabi-10.3-2021.10/bin:/home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux ***@***.***:~/circuitpython/ports/silabs$ ***@***.***:~/circuitpython/ports/silabs$ make BOARD=devkit_xg24_brd2601b clean - Verbosity options: any combination of "steps commands rules", as `make V=...` or env var BUILD_VERBOSE rm -rf build-devkit_xg24_brd2601b ***@***.***:~/circuitpython/ports/silabs$ make BOARD=devkit_xg24_brd2601b slc-generate - Verbosity options: any combination of "steps commands rules", as `make V=...` or env var BUILD_VERBOSE SLC generates project Traceback (most recent call last): File "/home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/slc", line 23, in <module> sys.exit(_entryPoint(sys.argv[1:])) File "/home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/lib/slc_run.py", line 1300, in _entryPoint ret = _simpleSlc( File "/home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/lib/slc_run.py", line 1158, in _simpleSlc return _launchCliNoDaemon(args, launch_uc, java_location, debug, do_timing) File "/home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/lib/slc_run.py", line 962, in _launchCliNoDaemon cli_process = subprocess.Popen( File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) OSError: [Errno 8] Exec format error: '/home/parallels/circuitpython/ports/silabs/tools/slc_cli_linux/lib/../bin/slc-cli/slc-cli' make: *** [Makefile:173: slc-generate] Error 1 So different problems than before but it still does not work. This is with a completely clean Ubuntu install. At least the java environment appears to match your setups now. I have been trying to get this to work for nearly a month now. There appears to be issues and/or confusion on exactly how the SiLabs CP build setup should work. I have done this so many times now. To go back to why I am trying to do this. I have a custom board with the same EFR32MG24 part that is on the xG24 Dev Kit. I want to make sure I can successfully rebuild CP for the Dev Kit before going down the path of making changes for my specific HW. Maybe you could follow the instructions yourself with a clean Ubuntu VM and see what’s different to get it to work, clearly there has to be something that is missing or unclear. Thanks again for support. JT

…

On Feb 21, 2024, at 8:07 AM, Wayne Weeks ***@***.***> wrote: OK I think I have docker build setup. I am way out of my comfort zone here 8-)). I am new to Linux just because that appears to be the only way to build Circuit Python. So not really sure what I am going at this stage. Please send the docker environment and I’ll try to use it. Thanks, > On Feb 21, 2024, at 7:01 AM, Nguyen Van Chat ***@***.***> wrote: > > > I am not sure about your build environment. > Can you setup and build with docker ubuntu:22.04? > I will try build a docker environment and provide to you. > > — > Reply to this email directly, view it on GitHub <#8897 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFV6A6BUHYERZ7LZWJVPOJTYUYD25AVCNFSM6AAAAABDCADXE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWHA2TANBZHA>. > You are receiving this because you were mentioned. >

[silabs-ChatNguyen]

build_cp.zip

You can try with docker environment with below guide:

Extract

dev-machine:~$  unzip build_cp.zip
dev-machine:~$  cd build_cp

Build docker image

dev-machine:~/build_cp$  docker build -t docker_cp .

Run docker image & build

dev-machine:~/build_cp$  docker run -it -v $PWD:/build docker_cp

root@docker:/#  cd ./build/
root@docker:/build/#  git clone https://github.com/adafruit/circuitpython.git
root@docker:/build/#  cd ./circuitpython
root@docker:/build/circuitpython#  git checkout 8.2.10
root@docker:/build/circuitpython#  cd ./ports/silabs
root@docker:/build/circuitpython/ports/silabs#  make fetch-port-submodules
root@docker:/build/circuitpython/ports/silabs#  make BOARD=devkit_xg24_brd2601b V=2 clean
root@docker:/build/circuitpython/ports/silabs#  make BOARD=devkit_xg24_brd2601b V=2

```

[MHVUT]

Thanks for the docker file and instructions. Looks to be exactly the same problem that I posted about yesterday when trying a clean new Ubuntu VM. ***@***.***:/build/circuitpython/ports/silabs# make BOARD=devkit_xg24_brd2601b V=2 clean rm -rf build-devkit_xg24_brd2601b ***@***.***:/build/circuitpython/ports/silabs# make BOARD=devkit_xg24_brd2601b V=2 SLC generates project Traceback (most recent call last): File "/build/circuitpython/ports/silabs/tools/slc_cli_linux/slc", line 23, in <module> sys.exit(_entryPoint(sys.argv[1:])) File "/build/circuitpython/ports/silabs/tools/slc_cli_linux/lib/slc_run.py", line 1300, in _entryPoint ret = _simpleSlc( File "/build/circuitpython/ports/silabs/tools/slc_cli_linux/lib/slc_run.py", line 1158, in _simpleSlc return _launchCliNoDaemon(args, launch_uc, java_location, debug, do_timing) File "/build/circuitpython/ports/silabs/tools/slc_cli_linux/lib/slc_run.py", line 962, in _launchCliNoDaemon cli_process = subprocess.Popen( File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) OSError: [Errno 8] Exec format error: '/build/circuitpython/ports/silabs/tools/slc_cli_linux/lib/../bin/slc-cli/slc-cli' make[1]: *** [Makefile:174: slc-generate] Error 1 make: *** [Makefile:149: build-devkit_xg24_brd2601b/circuitpython_efr32.Makefile] Error 2 ***@***.***:/build/circuitpython/ports/silabs#

…

On Feb 22, 2024, at 10:08 AM, Nguyen Van Chat ***@***.***> wrote: You can try with docker environment with below guide: Extract dev-machine:~$ unzip build_cp.zip dev-machine:~$ cd build_cp Build docker image dev-machine:~/build_cp$ docker build -t docker_cp . Run docker image & build dev-machine:~/build_cp$ docker run -it -v $PWD:/build docker_cp ***@***.***:/# cd ./build/ ***@***.***:/build/# git clone https://github.com/adafruit/circuitpython.git ***@***.***:/build/# cd ./circuitpython ***@***.***:/build/circuitpython# git checkout 8.2.10 ***@***.***:/build/circuitpython# cd ./ports/silabs ***@***.***:/build/circuitpython/ports/silabs# make fetch-port-submodules ***@***.***:/build/circuitpython/ports/silabs# make BOARD=devkit_xg24_brd2601b V=2 clean ***@***.***:/build/circuitpython/ports/silabs# make BOARD=devkit_xg24_brd2601b V=2 ``` [build_cp.zip](https://github.com/adafruit/circuitpython/files/14377761/build_cp.zip) — Reply to this email directly, view it on GitHub <#8897 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFV6A6FIQZJUA4FPHJRIOUTYU6CQJAVCNFSM6AAAAABDCADXE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZHE4TGNZZGE>. You are receiving this because you were mentioned.

[MHVUT]

Hi Guys, Just want to give an update on progress rebuilding the CircuitPython .bin file for the SiLabs EFR32MG24 Dev Kit. I finally got it to work. Here’s how… I have an old Intel i5 based Mac on which I re-installed the mac OS, specifically Big Sur 11.7.10, so it was completely clean. Then I installed the Parallels VM tools, then used the Parallels tools to install Ubuntu 22.04. Following that I installed the Docker build tools, and then followed the instructions for building and running the docker VM. And it worked. So I can finally rebuild the CP .bin file for the SiLabs boards. I made no changes to any of the code or setup instructions when using the older Intel i5 based Mac with macOS Big Sur. Up to that point I was trying to use an M2 Pro based Mac mini with macOS Sonoma, specifically 14.3.1. So there does appear to be some differences between either an Apple silicon or Intel silicon based Mac, and/or using Big Sur versus Sonoma macOS with Parallels that impacts the CP development tool chain for SiLabs parts. I was able to take the new .bin file and program it on one of my EFR32MG24 Dev Kit boards, successfully connect with Thonny and run the simple ‘Hello World’ .py file. I know it’s the file I built because it has today’s date in the Adafruit CP boot message. Now I am trying to bring up CP on my custom board. I have the Mini Simplicity Connector on the custom board, and I have the WSTK. I am able to use SS5 to build and download .s37 files to the custom board. I have been using the bootloader and the bare metal ‘blinky’ which all works as expected. I can flash the RGB LED on my custom board. However, when I use Simplicity Commander to program CP on to the custom board, how do I then connect Thonny to get to the REPL? Thonny sees the J-Link interface for the WSTK, but Thonny says the ‘Device is busy or does not respond’. Is there additional config required on the WSTK, or elsewhere, to get Thonny to connect to the custom board using the Mini Simplicity interface? I believe the Mini Simplicity interface is working given that I can use SS5 to program the custom board. It is just the CP/REPL that doesn’t appear to be working. Thanks so much Nguyen for the support, I wouldn’t have been able to get the build working w/o your docker build file. JT

…

On Feb 22, 2024, at 1:30 PM, Wayne Weeks ***@***.***> wrote: Thanks for the docker file and instructions. Looks to be exactly the same problem that I posted about yesterday when trying a clean new Ubuntu VM. ***@***.***:/build/circuitpython/ports/silabs# make BOARD=devkit_xg24_brd2601b V=2 clean rm -rf build-devkit_xg24_brd2601b ***@***.***:/build/circuitpython/ports/silabs# make BOARD=devkit_xg24_brd2601b V=2 SLC generates project Traceback (most recent call last): File "/build/circuitpython/ports/silabs/tools/slc_cli_linux/slc", line 23, in <module> sys.exit(_entryPoint(sys.argv[1:])) File "/build/circuitpython/ports/silabs/tools/slc_cli_linux/lib/slc_run.py", line 1300, in _entryPoint ret = _simpleSlc( File "/build/circuitpython/ports/silabs/tools/slc_cli_linux/lib/slc_run.py", line 1158, in _simpleSlc return _launchCliNoDaemon(args, launch_uc, java_location, debug, do_timing) File "/build/circuitpython/ports/silabs/tools/slc_cli_linux/lib/slc_run.py", line 962, in _launchCliNoDaemon cli_process = subprocess.Popen( File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) OSError: [Errno 8] Exec format error: '/build/circuitpython/ports/silabs/tools/slc_cli_linux/lib/../bin/slc-cli/slc-cli' make[1]: *** [Makefile:174: slc-generate] Error 1 make: *** [Makefile:149: build-devkit_xg24_brd2601b/circuitpython_efr32.Makefile] Error 2 ***@***.***:/build/circuitpython/ports/silabs# > On Feb 22, 2024, at 10:08 AM, Nguyen Van Chat ***@***.***> wrote: > > > You can try with docker environment with below guide: > > Extract > > dev-machine:~$ unzip build_cp.zip > dev-machine:~$ cd build_cp > Build docker image > > dev-machine:~/build_cp$ docker build -t docker_cp . > Run docker image & build > > dev-machine:~/build_cp$ docker run -it -v $PWD:/build docker_cp > > ***@***.***:/# cd ./build/ > ***@***.***:/build/# git clone https://github.com/adafruit/circuitpython.git > ***@***.***:/build/# cd ./circuitpython > ***@***.***:/build/circuitpython# git checkout 8.2.10 > ***@***.***:/build/circuitpython# cd ./ports/silabs > ***@***.***:/build/circuitpython/ports/silabs# make fetch-port-submodules > ***@***.***:/build/circuitpython/ports/silabs# make BOARD=devkit_xg24_brd2601b V=2 clean > ***@***.***:/build/circuitpython/ports/silabs# make BOARD=devkit_xg24_brd2601b V=2 > > ``` > [build_cp.zip](https://github.com/adafruit/circuitpython/files/14377761/build_cp.zip) > — > Reply to this email directly, view it on GitHub <#8897 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFV6A6FIQZJUA4FPHJRIOUTYU6CQJAVCNFSM6AAAAABDCADXE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZHE4TGNZZGE>. > You are receiving this because you were mentioned. >

[silabs-ChatNguyen]

Maybe the bring-up code on your custom board does not work, so Thonny can't connect to your custom board.
The board communicate with Thonny via EUSART0. You can try build & flash firmware to print something to VCOM first.
In addition, you should use Ozone-Segger tool to debug your bring-up code.