Failed to build examples for wch port
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- zig
- Domain
- embedded-iot
Research direction
Start with port/wch/ch32v/src/chips/ch32v003.svd and inspect the access string reported as read/clear, then check how the regz SVD parser handles access values. Reproduce with zig build -Dexample=empty_ch32v003; done when the example builds without the reported parse failure.
Written by the indexing model from the issue text.
Description
Hi! Trying to build examples for wch port and got an error:
❯ zig version
0.17.0-dev.1936+5a625d5f3
❯ zig build -Dexample=empty_ch32v003
install
└─ install generated to empty_ch32v003.elf
└─ compile exe empty_ch32v003 debug riscv32-freestanding-eabi
└─ run exe regz (chips) w
warning(db): invalid access type: 'read/clear'
warning(svd): Failed to parse access string 'read/clear', it must be one of 'read-value', 'write-only', 'read-write', 'writeOnce', or 'read-writeOnce', defaulting to 'read-write'
failed command: ./.zig-cache/o/b359d994ac2ad06c9b5dba134b263811/regz --format svd --output_path ./.zig-cache/o/504071daff23245edfba08b64ae5b7e0/chips ./../../../port/wch/ch32v/src/chips/ch32v003.svd
Perhaps something wrong with port/wch/ch32v/src/chips/ch32v003.svd file
- Dominant language
- Zig
- Stars
- 2.3k
- Forks
- 198
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ZigEmbeddedGroup/microzig
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ZigEmbeddedGroup/microzig#1086 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 69/100
ZigEmbeddedGroup/microzig#1085 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ZigEmbeddedGroup/microzig#1061 ·
Maintainers usually reply within 1 day
-
regz: AVR peripherals generated at address 0 when the register-group name matches the module (ATDF)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
ZigEmbeddedGroup/microzig#1072 ·
Maintainers usually reply within 1 day
-
AVR (ATmega328P): UART/SPI HAL, drivers.zig, and nRF24L01+ driver (Emakefun RF-Nano V3.0)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
ZigEmbeddedGroup/microzig#1069 · 3 comments ·
Maintainers usually reply within 1 day
All issues in ZigEmbeddedGroup/microzig
Similar issues
-
[BUG] SOLE B94 (current model): Set Target Resistance Level rejected with 80 04 03 – bike expects 0.1 unitsPossibly taken @cagnulein claimed this today. Open
Difficulty 2/5 Half a day Newbie friendliness 78/100
cagnulein/qdomyos-zwift#5380 · 1 comment ·
Maintainers usually reply within 1 day
-
c++ good first issue no hardware needed tests
Difficulty 2/5 Under an hour Newbie friendliness 95/100
GageLawton/noise-cancellation#217 ·
Maintainers usually reply within 1 day
-
new device support
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Koenkk/zigbee2mqtt#33416 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
crosspoint-reader/crosspoint-reader#4008 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MatixYo/ESP32-Plane-Radar#110 ·
Maintainers usually reply within 1 day