Issue with ChipWhisperer 5.7.0 – CW308_SAM4S and CWLITEXMEGA Compilation Error

1

Hello everyone,

I’m new to ChipWhisperer and currently trying to set up version 5.7.0 with a Husky and the CW308_SAM4S target. I’m running into an issue where the compiler is not found when using a Lab in Jupyter Notebook, even though I can successfully build the firmware in the ChipWhisperer bash.

What works:

In the ChipWhisperer bash, I can compile and generate firmware using:

bash

CopierModifier

cd ~/portable/chipwhisperer/hardware/victims/firmware/simpleserial-aes
make PLATFORM='CW308_SAM4S'

The build completes successfully, and I get output like this:

yaml

CopierModifier

Welcome to another exciting ChipWhisperer target build!!
arm-none-eabi-gcc (GNU Arm Embedded Toolchain 10-2020-q4-major) 10.2.1 20201103 (release)
Compiling:
    simpleserial-aes.c ...Done!
    ../hal/sam4s/uart.c ...Done!
    ../crypto/tiny-AES128-C/aes.c ...Done!
LINKING:
    simpleserial-aes-CW308_SAM4S.elf ...Done!
Size after:
   text    data     bss     dec     hex filename
   3824     276    4588    8688    21f0 simpleserial-aes-CW308_SAM4S.elf

The problem:

However, when I try to run a Lab in Jupyter Notebook, I get the following error:

less

CopierModifier

sh: 1: arm-none-eabi-gcc: not found
make[1]: *** [.././Makefile.inc:398: gccversion] Error 127
sh: 1: arm-none-eabi-gcc: not found
make[1]: *** [.././Makefile.inc:495: objdir-CW308_SAM4S/basic-passwdcheck.o] Error 127

It looks like arm-none-eabi-gcc is not found when running from Jupyter Notebook, even though it works fine in the ChipWhisperer bash.

Additionally, I encountered the same issue when trying the Starter Kit 1 with the CWLITEXMEGA target, where avr-gcc is not found.

What I’ve tried:

  • Reinstalled the compilers** (arm-none-eabi-gcc and avr-gcc).
  • Checked my system paths:** I added the necessary paths and enabled long paths in Windows as recommended.
  • Disabled WSL (Windows Subsystem for Linux)** to ensure there were no conflicts.

Since I’m new to ChipWhisperer, I might be missing something obvious. Has anyone encountered this issue before? Any guidance would be greatly appreciated!

Thank you in advance for your help. :blush:

2

Hi,

Can you try the following:

  1. Try changing %%bash to %%sh
  2. If that doesn’t work, try going back to %%bash and running echo $PATH and posting the results.

Alex

3

Hi Alex,

Thanks a lot for your help! Switching to %%sh worked perfectly. I really appreciate your quick response and support. :blush:

Best,
Pierrick