Nikolay,
you need to keep the .elf files for your builds to be able to
analyze a backtrace. Do not use addr2line, it shows wrong line
numbers. Use the script "a2l" I posted previously (I'll include it
again below). Just feed it the .elf file and the backtrace. Example:
a2l tmp/3.1.008-32-g2fa3ab8-elf/ovms3.elf 0x400dc8ec 0x4008f43d
0x4008e181 0x400818cc 0x40082163 0x40083c4d 0x400dc8e9
(I don't have the -28- version, so my output doesn't make sense)
@Mark: spurious task WDT crashes and heap corruption crashes still
occur, but it seems they have become less often with the internal
RAM rework.
How is performance and power usage affected when using StandardMetrics.xxxxx->SetValue
in the IncomingFrameCan1 method?
Most of the messages update value every 100ms, and except
maybe speed, battery current and voltage, most of the parameters
are not changing that often. And even for the speed, current and
voltage, it is probably enough to update StandardMetrics in the
1 second ticker... does this make sense or is the difference
non-existing.
Extending Mark's answer:
It's normally OK to directly set metrics from IncomingFrameCan1(),
but be aware metrics listeners will be executed synchronously in the
context that changes the metric.
Standard metrics listeners are now for example the automatic
notification generators in the vehicle base class. These may need
quite some stack and time.
If you spend too much time handling frames on a high volume bus,
your vehicle task may lose frames. It's possible to raise the queue
size (currently 20 frames) and the vehicle task stack size, but it's
better to keep the CAN processing simple.
TL;DR: if you need to handle many CAN frames, I recommend changing
metrics that trigger notifications or other complex actions from the
ticker. If you encounter crashes on some CAN frames that may be due
to the vehicle task stack being too small
(CONFIG_OVMS_VEHICLE_RXTASK_STACK=6144).
Regards,
Michael
Script a2l:
#!/bin/bash
elf=~/esp/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/build/ovms3.elf
for adr in $* ; do
if [[ "$adr" =~ "elf" ]] ; then
elf="$adr"
else
cmd+=" -ex 'l *$adr'"
fi
done
cmd+=" -ex 'q'"
echo "Using elf file: $elf"
eval xtensa-esp32-elf-gdb -batch $elf $cmd 2>/dev/null
#| grep "^0x.* is in "
Am 26.07.2018 um 09:59 schrieb Nikolay
Shishkov:
Quick update:
I managed to do a not so quick update on one of the ovms
v.3 boxes that sits in a Think and can confirm that the
porting seems to work.
I could see speed, parking time, ambient temperature.
I had very strange problems doing the OTA update. The
firmware start download and I can see the messages
progressing, but it would halt in between 700kB and 1600kB and
then stay there until I refresh the browser.
And when I refresh the browser I am asked of my password
which leads me to that there must have been a crash in the
meantime.
I was finally able to get the OTA update work by
disconnecting the box from the car and powering it via USB.
This is a single data point but it kind of points to a problem
with the code that communicates with the car.
I was not able to get a laptop connected to checkout the
console, but managed to get the following log - not sure how
to interpret it.
Last boot was 87 second(s) ago
Time at boot: 2018-07-25 18:07:43 GMT
This is reset #3 since last power cycle
Detected boot reason: Crash (12/12)
Crash counters: 3 total, 0 early
Last crash: Alloca exception on core 0
Registers:
PC : 0x400dc8ec PS : 0x00060234 A0 : 0x8008f440 A1 :
0x3ffc45b0
A2 : 0x00000020 A3 : 0x00000001 A4 : 0x00000000 A5 :
0x3ffb44b8
A6 : 0x3ffb47e4 A7 : 0x3ffb458c A8 : 0x3ffb44d4 A9 :
0x3ffc4590
A10 : 0x00000000 A11 : 0x7fffffff A12 : 0x8008e65b A13
: 0x3ffcc450
A14 : 0x00000003 A15 : 0x00060023 SAR : 0x00000000
EXCCAUSE: 0x00000005
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND :
0x00000000 LCOUNT : 0x00000000
Backtrace:
0x400dc8ec 0x4008f43d 0x4008e181 0x400818cc 0x40082163
0x40083c4d 0x400dc8e9
Version: 3.1.008-29-gaf41242/ota_1/edge (build idf
v3.1-dev-987-g55d915e Jul 6 2018 00:14:59)
Running partition: ota_1
Boot partition: ota_1
Firmware: 3.1.008-29-gaf41242/ota_1/edge (build idf
v3.1-dev-987-g55d915e Jul 6 2018 00:14:59)
How is performance and power usage affected when using StandardMetrics.xxxxx->SetValue
in the IncomingFrameCan1 method?
Most of the messages update value every 100ms, and except
maybe speed, battery current and voltage, most of the
parameters are not changing that often. And even for the
speed, current and voltage, it is probably enough to update
StandardMetrics in the 1 second ticker... does this make sense
or is the difference non-existing.
Thanks for all the hand holding and help,
Nikolay
--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26