OSC DEV V006 Rev B Is Ready
The OSC DEV V006 Rev B is a revised hardware design intended to fix critical issues present in the previous Rev A version, including power, UART, and differential current sensing problems. It also introduces new features such as dual-mode encoder input, an external NTC connector, and improved pin mapping for better functionality. While the design is complete, it has not yet been fabricated or tested, so validation remains pending.
- ▪Rev B fixes critical issues from Rev A, including a VDD/VCC swap that previously required physical modification to power on.
- ▪The differential current sensing circuit was incorrectly implemented in Rev A, rendering it non-functional; Rev B corrects this by proper OPA pin mapping.
- ▪A jumper has been added to allow selection between LinkE and TTL UART modes, enabling UART functionality without firmware.
- ▪Rev B adds new features like an external NTC connector, PWM servo header, and dual-mode encoder input for enhanced development capabilities.
- ▪The design is complete but has not yet been fabricated or validated, so users are advised to wait for a bringup report before building it.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 110125) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Aaron Qian Posted on May 2 • Originally published at aaronqian.com OSC DEV V006 Rev B Is Ready #hardware #embedded #electronics #riscv Rev A took board surgery to power on. Then I hit an RX line that refused to go LOW. Then I noticed a third defect I never wrote up: the differential current sensing on the OPA wasn't actually differential. Rev B is the respin that fixes all three, plus a handful of features I was going to need anyway.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV Community.
Discussion
0 commentsMore from DEV Community
