port: copy edit port readmes, archive ios port

port/apollo2-em9304/README.md

@@ -1,4 +1,4 @@
-# BTstack port for Ambiq Apollo2 with EM9304
+# BTstack Port for Ambiq Apollo2 with EM9304
 
 This port uses the Ambiq Apollo2 EVB and the Ambiq EM9304 (AM BLE) shield.
 HAL and BSP from Ambiq Suite 1.2.11 were used together with the regular ARM GCC toolchain.
@@ -45,7 +45,7 @@ In port/apollo2-em9304/btstack_config.h additional debug information can be enab
 
 Also, the full packet log can be enabled in src/btstack_port.c by uncommenting the hci_dump_init(..) line. The console output can then be converted into .pklg files for OS X PacketLogger or WireShark by running tool/create_packet_log.py
 
-# TODO
+## TODO
 - BTstack's TLV persisten storage via Flash memory is not implemented yet.
 - SPI Fullduplex: Newer Apollo 2 revisions supports SPI Full Duplex. The Ambiq Suite 1.2.11 does not cover Full Duplex with IRQ callback. It could be emulated by setting the Full Duplex mode and doing a regular write operation. When the write is complete, the received data can be read from the IOM FIFO.
 - During MCU sleep without an ongoing SPI operation, the SPI could be fully disabled, which would reduce enrgey consumption.

port/archive/README.md

@@ -1,17 +1,25 @@
 # 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 rewored/refreshed.
+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. Individual ports:
+  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](https://bluekitchen-gmbh.com/msp432p401r-cc2564c-port-uart-without-hardware-rtscts-flow-control/) should be used. Individual ports:
     - [EZ430-RF256x Bluetooth Evaluation Tool for MSP430](https://www.element14.com/community/docs/DOC-72027/l/ez430-rf256x-bluetooth-evaluation-too)
     - [MSP430F5438 Experimenter Board for MSP430](https://www.element14.com/community/docs/DOC-40373/l/msp430f5438-based-experimenter-board) with [Bluetooth CC2564 Module Evaluation Board](https://www.ti.com/tool/cc2564modnem)
     - [MSP-EXP430F5529LP LaunchPad](https://www.ti.com/ww/en/launchpad/launchpads-msp430-msp-exp430f5529lp.html#tabs) with [Bluetooth CC2564 Module Evaluation Board](https://www.ti.com/tool/cc2564modnem) and [EM Adapter BoosterPack](https://www.ti.com/tool/boost-ccemadapter) 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
+
+- Port for MicroChip PIC32 with Harmony Framework: the original port was for Harmony v1, while there's a Harmony V3 out since 2019:
     - [Microchip's PIC32 Bluetooth Audio Development Kit](https://www.microchip.com/Developmenttools/ProductDetails/DV320032)
+
+- iOS port:
+    - BTstack on iOS is not supported anymore.
+

port/msp432p401lp-cc256x/README.md

@@ -1,4 +1,4 @@
-# BTstack port for MSP432P401 Launchpad with CC256x
+# BTstack Port for MSP432P401 Launchpad with CC256x
 
 This port is for the the TI MSP432P401R Launchpad with TI's CC256x Bluetooth Controller using TI's DriverLib (without RTOS). 
 For easy development, Ozone project files are generated as well.

port/nrf5-cinnamon/README.md

@@ -1,4 +1,4 @@
-# BTstack port with Cinnamon for Nordic nRF5 Series 
+# BTstack Port with Cinnamon for Nordic nRF5 Series 
 
 *Cinnamon* is BlueKitchen's minimal, yet robust Controller/Link Layer implementation for use with BTstack.
 

port/nrf5-zephyr/README.md

@@ -1,4 +1,4 @@
-# Experimental port of BTstack to Zephyr running on Nordic nRF5 Series
+# BTstack Port for Zephyr RTOS running on Nordic nRF5 Series
 
 ## Overview
 

port/posix-h4-atwilc3000/README.md

@@ -1,5 +1,4 @@
-# POSIX H4 Port for Atmel ATWILC3000
-
+# BTstack Port for POSIX Systems with Atmel ATWILC3000 Controller
 This port allows to use the ATWILC3000 connected via UART with BTstack running on a POSIX host system, see test setup below (which lacks a proper RESET button).
 
 ## Compilation

port/posix-h4-da14581/README.md

@@ -1,4 +1,4 @@
-# POSIX H4 Port for Dialog Semiconductor DA14581
+# BTstack Port for POSIX Systems with Dialog Semiconductor DA14581 Controller
 
 This port allows to use the DA14581 connected via UART with BTstack running on a POSIX host system.
 

port/posix-h4-da14585/README.md

@@ -1,4 +1,4 @@
-# POSIX H4 Port for Dialog Semiconductor DA14585
+# BTstack Port for POSIX Systems with Dialog Semiconductor DA14585 Controller
 
 This port allows to use the DA14585 connected via UART with BTstack running on a POSIX host system.
 

port/posix-h4-zephyr/README.md

@@ -1,6 +1,6 @@
-# BTstack port for Zephyr Controller with HCI UART Firmware Connectected To POSIX System
+# BTstack Port for POSIX Systems with Zephyr-based Controller
 
-The main difference to the regular posix-h4 port is that that the Zephyr Contoller uses 1000000 as baud rate.
+The main difference to the regular posix-h4 port is that that the Zephyr Controller uses 1000000 as baud rate.
 In addition, the port defaults to use the fixed static address stored during production.
 
 ## Prepare Zephyr Controller

port/renesas-tb-s1ja-cc256x/README.md

@@ -1,4 +1,4 @@
-# BTstack port for Renesas Target Board TB-S1JA with CC256x
+# BTstack Port for Renesas Target Board TB-S1JA with CC256x
 
 This port uses the Renesas TB-S1JA with TI's CC256XEM ST Adapter Kit that allows to plug in a CC256xB or CC256xC Bluetooth module.
 Renesas e2 Studio (Eclise-based) was used with the SSP HAL and without an RTOS.

port/samv71-xplained-atwilc3000/README.md

@@ -1,4 +1,4 @@
-# BTstack port for SAMV71 Ultra Xplained with ATWILC3000 SHIELD
+# BTstack Port for SAMV71 Ultra Xplained with ATWILC3000 SHIELD
 
 This port uses the [SAMV71 Ultra Xplained Ultra](http://www.atmel.com/tools/atsamv71-xult.aspx) evaluation kit with an [ATWILC3000 SHIELD](http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=ATWILC3000-SHLD). The code is based on the Advanced Software Framework (ASF) (previously know as Atmel Software Framework). It uses the GCC Makefiles provided by the ASF. OpenOCD is used to upload the firmware to the device.