Ok, I'm inside (Mr Elon, please do not send an assassin
- The whole problem is not a lack of memory. It is caused by refresh function for traffic info, with passes processing to the main routine. It seems that somebody interpreted value of delay of a refresh to be in seconds (120, = 2 minutes), but it is in milliseconds. It eats 30% of spare MCU1 time. It tries to re-render it 6-7 times per second, with no new information (refresh period of traffic info via communication channel is set correctly).
My assumption - two differently skilled programmers did that.
Please, Tesla, correct this. Just add three zeros (120 -> 120000), recompile and send to us. And all will be ok.
Thomas
PS: Loading Tegra3 with this one passive cooler over 60% of load causes throttling. Who was a developer? Even ventilation holes, developed by engineers are covered from the bottom by shelf under the screen. No air circulation then.