Migration to 6.0.1
Posted: Sun Jun 14, 2026 10:54 pm
After some headaches i managed to shift my application to 6.0.1.
BUT ACTUALLY i had to fight two ugly facts:
configTASK_NOTIFICATION_ARRAY_ENTRIES defaults to 1 EVEN THOUGH drivers (like uart) require this to be at least 2 .....
The new CAN implementation uses twai_onchip_node_config_t which has no default initialization.
Hence new members
node_config.io_cfg.quanta_clk_out
node_config.io_cfg.bus_off_indicator
are initialized to 0 which causes GPIO0 to be driven unintentionally.
Took me some time to find out why my modbus communication died whenever CAN driver was initialized
Another problem ocurred with old STM32 modules causing brownouts with WIFI which they did NOT with 5.5.4 ! Even placing a huge capacitor did not help. On newer ESP32 modules and fortunately with my Custom PCB this was not an issue.
- So please revert the default configTASK_NOTIFICATION_ARRAY_ENTRIES back to 2. If one has to save 4 Bytes a task he can lower to 1
- Provide an initialization MACRO or a default constructor for twai_onchip_node_config_t !
Greets, Tom
BUT ACTUALLY i had to fight two ugly facts:
configTASK_NOTIFICATION_ARRAY_ENTRIES defaults to 1 EVEN THOUGH drivers (like uart) require this to be at least 2 .....
The new CAN implementation uses twai_onchip_node_config_t which has no default initialization.
Hence new members
node_config.io_cfg.quanta_clk_out
node_config.io_cfg.bus_off_indicator
are initialized to 0 which causes GPIO0 to be driven unintentionally.
Took me some time to find out why my modbus communication died whenever CAN driver was initialized
Another problem ocurred with old STM32 modules causing brownouts with WIFI which they did NOT with 5.5.4 ! Even placing a huge capacitor did not help. On newer ESP32 modules and fortunately with my Custom PCB this was not an issue.
- So please revert the default configTASK_NOTIFICATION_ARRAY_ENTRIES back to 2. If one has to save 4 Bytes a task he can lower to 1
- Provide an initialization MACRO or a default constructor for twai_onchip_node_config_t !
Greets, Tom