11 Jan
2018
11 Jan
'18
2:20 p.m.
WiFi running on core #0 would explain the impact of wifi operations on the receipt of CAN frames. But, with the car interfaces running on core #1, core #0 might actually have more bandwidth under normal circumstances, as I'm assuming the modem is pretty light loading due to the limited data rate. {shrug} Need more real-world experience for optimizing this kind of stuff. Are we going to have a semi-formalized "beta" testing period for the first sets of production units per car? What will the feedback channel be? Greg Mark Webb-Johnson wrote:
Every other task is created on core #1. Supposedly our App runs on core #1, and wifi/bluetooth run on core #0. Why is can::can CAN_rxtask running on core #0?