The BTT PI 1.2 is unstable with latest V3.0.0 image.
- Dominant language
- No language data
- Stars
- 496
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
I've tried to use the BTT PI 1.2 board with the latest available image CB1_Debian12_Klipper_kernel6.6_20241219.img.xz and discovered that at least my SBC behaves quite unstable with it.
Instability manifests itself in segmentation faults or archive utilities crashes e.g.:
- it is impossible to build firmware from /home/biqu/klipper folder - the compiler exits with an internal failure error or segmentation fault;
- apt can't processed indexes and complaints about gzip decompression errors;
- deb tools (dpkg-deb) fails with decompression error during packages unpacking
Situation improves a little bit if I reduce significantly CPU frequency using /etc/default/cpufrequtils but this doesn't resolve issue completely.
What is interesting - the **stress** utility doesn't triggers the issue (at least on short runs) but decompressing lzma archives or **lzbench** (with 'tornado' algorithm) easily reproduce the issue. So most likely it is RAM stability issue.
I've tried to use newer kernel from Armbian image (see below) but this doesn't help. But when I've tried to use the board with older **V2.3.4 image (CB1_Debian11_Klipper_kernel5.16_20240319.img.xz)** or with **Armbian image (Armbian_25.2.2_Bigtreetech-cb1_bookworm_current_6.6.75_minimal.img.xz)** images - everything **works fine**.
So I've thought that it could be an uBoot issue. I've tried to replace uBoot on microSD with V3.0.0 image by uBoot from Armbian using following commands:
```shell
dd if=Armbian_25.2.2_Bigtreetech-cb1_bookworm_current_6.6.75_minimal.img of=u-boot-btt.bin bs=1024 skip=8 count=1024
dd if=u-boot-btt.bin of=/dev/mmcblk0 bs=1024 seek=8 conv=fsyn
```
Such combination (i.e. uBoot from Armbian + V3.0.0) gives me completely stable work with V3.0.0 image.
I may only guess that it could be an issue related to the uBoot commit https://github.com/bigtreetech/u-boot/commit/bb850b2ced48100e05ae08f5c04b874e26c69bec but I've not checked this directly.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the failures with CB1_Debian12_Klipper_kernel6.6_20241219.img.xz using the Klipper firmware build, apt/dpkg decompression, and lzbench tests. Compare it with V2.3.4 and Armbian_25.2.2_Bigtreetech-cb1_bookworm_current_6.6.75_minimal.img.xz, then inspect the referenced u-boot commit bb850b2 and test the Armbian u-boot replacement commands. Done means V3.0.0 is stable without requiring reduced CPU frequency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100