JorgeGzm opened a new pull request, #19445:
URL: https://github.com/apache/nuttx/pull/19445

   ## Summary
   
   New RISC-V chip port for the GigaDevice **GD32VW55x** (Nuclei N307, Wi-Fi 6 
+ BLE 5.3) and the GD32VW553K-START board. The radio comes from the prebuilt 
vendor libraries behind a thin sys_* facade; the SDK is cloned and pinned at 
build time (same pattern as esp-hal-3rdparty). Everything that touches hardware 
registers is a native NuttX driver.
   
   HAL drivers: serial, DMA, GPIO/EXTI, SPI, I2C, ADC, PWM, input capture, 
FWDGT and WWDGT watchdogs, PROGMEM (internal flash via the mask ROM API), TRNG, 
CRC, RTC, plus board LEDs and software reset. Wi-Fi (wlan0, station and softAP) 
is a netdev_lowerhalf driver on the NuttX network stack. BLE 5.3 is present but 
EXPERIMENTAL and off by default.
   
   Full details are in the new documentation under 
Documentation/platforms/risc-v/gd32vw55x/.
   
   <img width="652" height="771" alt="gd32vw553k-start" 
src="https://github.com/user-attachments/assets/db136683-f4ac-4270-a267-f92f383112df";
 />
   
   
   ## Impact
   
   New arch/chip and board; no existing code is changed. The Wi-Fi/BLE 
configurations need the vendor SDK (fetched at build time); nsh and periph 
build without it.
   
   ## Testing
   
   Built on Linux with riscv-none-elf-gcc 14.2.0; all five configurations 
build, nxstyle is clean, docs build without warnings.
   
   Validated on hardware (**GD32VW553K-START**:
   
   - nsh / periph / littlefs — boots, drivers register, TRNG and LEDs work, 
LittleFS survives a reboot.
   - Wi-Fi station: scan, WPA2 four-way handshake, DHCP, ping gateway and 
8.8.8.8 (3/3).
   - Wi-Fi softAP: nuttxwifi up (WPA2, ch 11), visible from a laptop.
   - BLE: advertises as NuttX; a central connects and enumerates GATT.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to