I've looked at the regmap dump and added the offset in the RX and TX
FIFOs.
tl;dr:
Everything, but the last 2 messages, look consistent The last 2 RX
messages have not been received by the hardware. On the other hand the
hardware has received the correct messages, but they were not received
by the test application.
On 23.12.2022 08:18:17, Stefan Althöfer wrote:
> Loop 4429 2022-12-23T03:07:45 last+4s total:4h299m
> + ./sctestself -b -n 4 -l 999 -t 2 -v cmperr,logmsg -F refilldata,leastdots,allowintloopb,stoponerror -d 8 can1
> CAN selftest can1 .......idx 2 tx:2A5#00 02 6A 8F 6C 81 C3 B0
> rx:2A5#00 00 85 9A EF 54 34 5D
> idx 3 tx:2A5#00 03 4F 8F 85 59 8E DA
> rx:2A5#00 00 85 9A EF 54 34 5D
> .c (700) fail
> 0: RX (004/003) 2A5#00 00 85 9A EF 54 34 5D ???
Not RX'ed by hardware
> 0: RX (004/002) 2A5#00 00 85 9A EF 54 34 5D ???
Not RX'ed by hardware
> 0: TX (003/002) 2A5#00 03 4F 8F 85 59 8E DA TX 0x03 -> RX 0x03 !!!
Not RX'ed by application
In the hardware the message is in the TX FIFO at offset 0x03 and in RX
0x03.
> 0: RX (003/001) 2A5#00 01 7C 30 5C 7A 2D 1C RX 0x01
> 0: TX (002/001) 2A5#00 02 6A 8F 6C 81 C3 B0 TX 0x02 -> RX 0x02 !!!
Not RX'ed by application
In the hardware the message is in the TX FIFO at offset 0x02 and in RX
0x02.
> 0: RX (002/000) 2A5#00 00 AC AF 70 9B 32 03 RX 0x00
> 0: TX (001/000) 2A5#00 01 7C 30 5C 7A 2D 1C TX 0x01 -> RX 0x01
In the hardware the message is in the TX FIFO at offset 0x01 and in RX
0x01.
> 0: TX (000/000) 2A5#00 00 AC AF 70 9B 32 03 TX 0x00 -> RX 0x00
In the hardware the message is in the TX FIFO at offset 0x00 and in RX
0x00.
> 0: RX (004/003) 2A5#00 03 65 32 F8 E7 E6 F5 RX 0x0f
> 0: RX (004/002) 2A5#00 02 CC D5 09 FE 55 99 RX 0x0e
> 0: TX (003/002) 2A5#00 03 65 32 F8 E7 E6 F5
> 0: RX (003/001) 2A5#00 01 62 4F 17 34 44 CE RX 0x0d
> 0: TX (002/001) 2A5#00 02 CC D5 09 FE 55 99
> 0: RX (002/000) 2A5#00 00 FE 58 FE FD C0 EF RX 0x0c
> 0: TX (001/000) 2A5#00 01 62 4F 17 34 44 CE
> 0: TX (000/000) 2A5#00 00 FE 58 FE FD C0 EF
> 0: RX (004/003) 2A5#00 03 C9 7B EF 83 93 E0 RX 0x0b
> 0: RX (004/002) 2A5#00 02 DD 5E 82 B4 FD C4 RX 0x0a
> 0: TX (003/002) 2A5#00 03 C9 7B EF 83 93 E0
> 0: RX (003/001) 2A5#00 01 90 3B 32 80 90 67 RX 0x09
> 0: TX (002/001) 2A5#00 02 DD 5E 82 B4 FD C4
> 0: RX (002/000) 2A5#00 00 8F 28 D2 F5 B6 98 RX 0x08
> 0: TX (001/000) 2A5#00 01 90 3B 32 80 90 67
> 0: TX (000/000) 2A5#00 00 8F 28 D2 F5 B6 98
> 0: RX (004/003) 2A5#00 03 C5 1E FE 68 F1 65 RX 0x07
> 0: RX (004/002) 2A5#00 02 7E 2B BA 18 F1 7B RX 0x06
> 0: TX (003/002) 2A5#00 03 C5 1E FE 68 F1 65
> 0: RX (003/001) 2A5#00 01 CE 1B D7 9E 42 15 RX 0x05
> 0: TX (002/001) 2A5#00 02 7E 2B BA 18 F1 7B
> 0: RX (002/000) 2A5#00 00 85 9A EF 54 34 5D RX 0x04
> 0: TX (001/000) 2A5#00 01 CE 1B D7 9E 42 15
> 0: TX (000/000) 2A5#00 00 85 9A EF 54 34 5D
Can you run this in parallel to the test. Abort with Ctrl+c after the
test fails and send me the log file. The last 256 lines should be
enough.
| candump any,0:0,#FFFFFFFF -l
The candump writes to current dir by default. To avoid side effects
change to a tmpfs, if you have enough RAM :).
Also send the regmap dump and of course the error message of the test
tool.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
