Repository navigation
Releases: TouchNetix/AXPB009
Release list
v03.02
What's Changed
- Add irq line state command by @HenryCTS in #16
- Add reproducible Docker and CMake firmware build by @HenryCTS in #17
Full Changelog: v03.00...v03.02
Contributors
Assets 6
v03.00
What's Changed
- Added stm32f0xx-hal-driver as submodule and updated to the latest version by @Jimmy-Cameron in #11
- Modified the out endpoints bInterval from 5 to 1. by @HenryCTS in #12
- Uprev to v03.00. by @Jimmy-Cameron in #13
New Contributors
Full Changelog: v02.05...v03.00
ATTENTION
This release DOES NOT include a build for the STM32F042F6 part. The recent code changes increased the code size and the
STM32F042F6 does not have enough flash (32kB). This will be addressed in a future release.
Contributors
Assets 6
v2.05
AXPB009 v02.05
What's Changed
- USB host detection improvements by @Jimmy-Cameron in #10
Full Changelog: v02.04...v02.05
Contributors
Assets 8
v02.04
AXPB009 v02.04
• Fixed a bug that prevented devices programmed from blank from functioning
v02.03
AXPB009 v02.03
• Fixed an issue where after a hard-reset (with self-tests) the SCL line would be stuck low
• Bridge now waits for aXiom to complete any self-tests before trying to obtain the I2C address
• Only checks I2C addresses 0x66 and 0x67, rather than sweeping the full range. Looks for response from aXiom for 12.5 seconds. If no response, bridge will skip trying to read the usage table and appear in "Bridge Only" mode.
• When resetting, the bridge will now wait 3 seconds after disconnecting from the USB bus before performing a reset.
IMPORTANT
IF PROGRAMMING A BLANK CHIP WITH THIS FIRMWARE, THE DEVICE WILL NOT OPERATE. FOR NEW PRODUCTION RUNS WHERE THE DEVICE IS BEING PROGRAMMED IN FACTORY, USE V2.04.
THIS ISSUE DOES NOT AFFECT PREVIOUSLY PROGRAMMED DEVICES (E.G. UPGRADING FROM V2.02 TO V2.03).
v02.02
AXPB009 v02.02
• Removed ability for bridge to write a semaphore before/after a multi-page read
• Added ~100us delay to the end of every SPI transfer to prevent an issue where reading aXiom too quickly resulted in a comms error
