
16next firmware
Hype23/100Firmware for next-generation 16n devices.
for16n project 16n Faderbank·by@16n-faderbank
Unclaimed. Is this yours? Sign in with GitHub as @16n-faderbank to claim it.
16next_3_1_1.uf2· 77 KB
MIT· 16n-faderbank/16next_firmware·downloads come from the creator’s GitHub releases
v3.1.116next v3.1.1Latest1 file
Changelog
- I2C enumeration now done via write, not read (fixes compatibility with Expert Sleepers Disting NT). (thanks, @expertsleepers).
The way I2C scanning was performed - originally written for TXi/TXo back in the day - wasn't compatible with devices that never write over I2C. This should still be compatible with existing devices, and also now enable support with the Disting NT.
v3.1.016next v3.1.01 file
Changelog
- Support sending high-resolution (14-bit) data for each TRS/USB channel
- Fettle sensitivity of channels via ResponsiveAnalogRead to avoid 'stickiness' at edges.
16next-based devices can now send 14-bit CC data for each USB and TRS channel, configured via the editor. PLEASE READ the upgrade guide:
Important note on upgrading from < 3.1.0 to 3.1.0+
If you are upgrading from a device that has already had a pre-3.1.0 firmware installed on it, you will need to head to the editor immediately and edit your configuration; some USB or TRS channels might have set themselves to "high resolution" mode, and you will likely want to disable this.
This arises because the config is derived from previously unused areas of memory, which may lead to confusion.
If you are installing 3.1.0 onto a fresh RP2040, the default settings should avoid this; it's only an issue when upgrading firmware.
In general, you should always head to the editor to check your configuration after a firmware upgrade.
v3.0.316next v3.0.31 file
Changelog
- I2C data is now 14-bit range (0-16383) rather than 12-bit (0-4095).
16n transmitted 14-bit values over I2C because it was sending the raw value from a 14-bit ADC (which, to be fair, was not the best idea).
16nx was previously transmitting 12-bit values over I2C, which, whilst reasonable, would make it incompatible with (eg) Teletype scripts expecting 14-bit numbers.
I2C output data is now bitshifted by 2 (
<<2) to make it 14-bit, ensuring backwards compatibility.v3.0.216next v3.0.21 file
Changelog
- new VID/PID codes courtesy of pid.codes.
Functionally identical to 3.0.1, not a mandatory upgrade, but we'll build on this going forward.
v3.0.116next v3.0.11 file
Changelog
- add increased time for crystal oscillator startup, fixing issue where boards wouldn't necessarily start correctly.
Even if you didn't have this issue, this is a recommended upgrade for all boards.
v3.0.016next v3.0.01 file
First preview release of 16next firmware.
This appears as
3.0.0in the editor and everywhere, simply because it's the next MAJOR release after the 16n firmware itself, which was at 2.x.x.