Software/SystemK
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix for #12: Transition from "Configuring" to "Ready" due to "Configured" event not possible (#13)

Browse source 
This pull request fixes #12.

The root cause was [`BLE_HandleCommonEvents()`](https://git.ktag.clubk.club/Software/SystemK/src/tag/SystemK_v01.01/BLE/BLE_Utils.c#L57) was causing BLE events to be marked as "not new" by [`BLE_IsPacketNew()`](https://git.ktag.clubk.club/Software/SystemK/src/tag/SystemK_v01.01/BLE/BLE_Packet_Tracker.c#L53), even though these packets were left unhandled by the common event handler.

The solution is to separate the querying of whether a packet is new from the marking it as already seen, since we don't want to mark a packet as seen until it has been properly _handled_.  I added the function `BLE_RememberPacket()` for the latter purpose.

I also cleaned up some of the logging code, now that logging is configurable (on ESP32 platform, anyway).

Co-authored-by: Joe Kearney <joe@clubk.club>
Reviewed-on: #13
This commit is contained in:
Joe Kearney 2026-02-28 02:51:00 +00:00
parent 45df6f952a
commit daa1a2a1ec
6 changed files with 28 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
States/State_Configuring.c
View file

@ -376,6 +376,8 @@ void HandleBLEConfigurationPacket(const BLE_ParametersPacket_T *const packet)
{
if (BLE_IsPacketNew(packet->BD_ADDR, BLE_PACKET_TYPE_PARAMETERS, packet->event_number))
{
BLE_RememberPacket(packet->BD_ADDR, BLE_PACKET_TYPE_PARAMETERS, packet->event_number);
if (packet->subtype == BLE_REQUEST_PARAMETER_CHANGE)
{
SystemKResult_T result = SYSTEMK_RESULT_SUCCESS;