FreeRTOS-Kernel/FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator
Kody Stribrny 54d4eeaa26
Add Vectored Interrupt Support To SiFive RISC-V Demo (#871)
Update SiFive IAR demo to support vectored interrupts. This is a near copy of https://github.com/FreeRTOS/FreeRTOS/pull/797.

Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com>
Co-authored-by: Gaurav Aggarwal <aggarg@amazon.com>
2022-11-09 10:34:04 -08:00
..
Common Add Vectored Interrupt Support To SiFive RISC-V Demo (#871) 2022-11-09 10:34:04 -08:00
MQTT_Basic_TLS winsim-mqtt-demos: Update VS project files 2022-08-17 15:43:21 -07:00
MQTT_Keep_Alive winsim-mqtt-demos: Update VS project files 2022-08-17 15:43:21 -07:00
MQTT_Multitask winsim-mqtt: Fix ALPN strings in coreMQTT demos 2022-08-26 09:58:39 -07:00
MQTT_Mutual_Auth Percepio Trace Recorder v4.6.0 (#789) 2022-11-03 13:58:38 -07:00
MQTT_Mutual_Auth_wolfSSL Add Vectored Interrupt Support To SiFive RISC-V Demo (#871) 2022-11-09 10:34:04 -08:00
MQTT_Plain_Text winsim-mqtt-demos: Update VS project files 2022-08-17 15:43:21 -07:00
MQTT_Serializer Add Vectored Interrupt Support To SiFive RISC-V Demo (#871) 2022-11-09 10:34:04 -08:00
readme.txt Multiple tidy up and corrections preparing for release (#390) 2020-11-09 14:50:33 -08:00
readme_also_coreMQTT_multithreading_agent.url Add links to the MQTT agent in the non-agent mqtt demos (#470) 2020-12-11 21:12:44 -08:00
readme_coreMQTT.url Update urls in code to those on the server (#396) 2020-11-10 10:53:14 -08:00

The subdirectories of this directory contain multiple examples that demonstrate
coreMQTT using in both single and multi-threaded scenarios, as well as with
both plain text and authenticated and encrypted network interfaces.

The multi threaded example creates an MQTT agent (or daemon task).  It is thread
safe because only the agent task is allowed to access the coreMQTT API - hence
the API is only accessed from one FreeRTOS task.  Other tasks and interrupts
needing to interact with the MQTT agent do so through a thread safe queue.
We are generalising this technique for future coreMQTT releases, which will have
a re-usable agent component.

! Plain text examples are for ease of evaluation only - product devices should
! always use authenticated and encrypted communication.  Never send private or
! sensitive data on an unencrypted connection.