.. | ||
ez430-rf2560 | ||
msp430f5229lp-cc2564b | ||
msp-exp430f5438-cc2564b | ||
pic32-harmony | ||
posix-h5-bcm | ||
wiced-h5 | ||
README.md |
Archive of earlier ports
The ports in this folder are not recommended for new designs. This does not mean that the target hardware is not suitable for new designs, just that the ports would need to reworked/refreshed.
List of ports with reason for move to this archive:
-
MSP430 ports: The ports used the not-maintained version of the community MSP430 gcc port, which does not support more than 64 kB of FLASH RAM. A current port should use the official GCC version sponsored by TI. In addition, the MSP430 UART does not support hardware RTS/CTS. For a new port, our ringbuffer approach should be used. Individual ports:
- EZ430-RF256x Bluetooth Evaluation Tool for MSP430
- MSP430F5438 Experimenter Board for MSP430 with Bluetooth CC2564 Module Evaluation Board
- MSP-EXP430F5529LP LaunchPad with Bluetooth CC2564 Module Evaluation Board and EM Adapter BoosterPack with additional 32768Hz quartz oscillator
-
Ports for Broadcom/Cypress Controllers using HCI Transport H5: The PatchRAM cannot be uploaded via H5. This requires to upload the PatchRAM using H4 mode and then to start the stack using H5 transport. In addition, several bugs have been observed in H5 mode, e.g. LE Encrypt not wokring. Unless absolutely neccessary, it's better to use H4 mode.
- Unix-based system connected to Broadcom/Cypress Bluetooth module via H5 over serial port
- Broadcom platforms that support the WICED SDK via H5 UART, see wiced-h4
-
Port for MicroChip PIC32 with Harmony Framework: the original port was for Harmony v1, while there's a Harmony V3 out since 2019:
-
iOS port:
- BTstack on iOS is not supported anymore.