| ### Key Points | |
| - **Modules Likely Functional but with Potential Issues**: The provided register readout shows a mix of values that partially align with CC1101 defaults, indicating SPI communication is occurring and the modules are responding. This rules out complete non-functionality or major wiring errors, but readings like PARTNUM=0xFF or VERSION=0xFF/0x0F suggest possible software misreads, counterfeit chips, or SPI protocol mismatches common in low-cost modules. | |
| - **Common Problems with Cheap CC1101 Modules**: Research suggests many inexpensive Chinese CC1101 units may be counterfeits, remarked chips (e.g., similar to CC110L), or have manufacturing variances that affect SPI reliability, reception, or register accuracy. However, they often work for basic tasks if configured carefully. | |
| - **SPI Reading Error Possible**: The 0x0F value may represent the chip's status byte (indicating states like IDLE with FIFO details) rather than the actual register value, pointing to a code mistake where the dummy byte isn' |
| import json | |
| file_path = "/usr/share/vscodium-bin/resources/app/product.json" | |
| with open(file_path, "r") as f: | |
| config = json.load(f) | |
| config["extensionsGallery"]["serviceUrl"] = "https://marketplace.visualstudio.com/_apis/public/gallery" | |
| config["extensionsGallery"]["cacheUrl"] = "https://vscode.blob.core.windows.net/gallery/index" | |
| config["extensionsGallery"]["itemUrl"] = "https://marketplace.visualstudio.com/items" |
If your running a x64 bit Ubuntu or other Linux and find USB transfers hang at the end apply this fix:
echo $((16*1024*1024)) > /proc/sys/vm/dirty_background_bytes
echo $((48*1024*1024)) > /proc/sys/vm/dirty_bytes
I suggest you edit your /etc/rc.local file to make this change persistant across reboots.
sudo nano /etc/rc.local