Hi Marc,
>Is this debug information generated by the driver? >It's printed to the serial console, isn't it? >Is this debug printing enabled by default? If so, disable it. Yes, this is debug printing enabled by default, on the serial console. Maybe it is generated by the driver (printf calls from the BSP), because I don't know how to disable it. I will ask Freescale about this debug printing thing as soon as possible. >Do you have a watchdog in the system, that can cause the reboot? Yes there is a watchdog timer module, (589 root 1704 S /usr/sbin/wd_keepalive ) but I can't tell for now the cause of the reset when the system reboots, I will make some test. I can join boot message if you want to look a it. >Does it always reboot in the middle of DATA[4]? every time I looked it was either in the middle of DATA[4] or DATA[3]. Thanks, Francois 2011/9/8 Marc Kleine-Budde <[email protected]> > Hello Francois, > > please don't forget the mailinglist on CC! > > On 09/08/2011 04:27 PM, Francois Bouchard wrote: > >> On 09/07/2011 10:29 PM, Francois Bouchard wrote: > >>>>> what does "the program reset by itself after a while" mean? > >>>> I mean yes the whole system seems to reboots apparently because of the > >> test > >>>> program. > >> > >>> It really seems to be a driver problem. Do you have any error messages > >>> prior to the reboot? Does the system hang or become unresponsive prior > >>> to rebooting? > >> > > Yes see below terminal message: > > Is this debug information generated by the driver? > It's printed to the serial console, isn't it? > Is this debug printing enabled by default? If so, disable it. > > Printing to the serial line is quite expensive, it takes to much time to > print the when receiving at 1000 kbit/s. > > > > > Transmission code active 0xc080000 > > reg->caniflg = 0x3 > > ** MB[1] : CODE=0x6 LEN=8 > > ** RX > > OVERRUN > > DATA[0] = 0x4c > > DATA[1] = 0x2e > > DATA[2] = 0x1 > > DATA[3] = 0x22 > > DATA[4] = 0x0 > > DATA[5] = 0x0 > > DATA[6] = 0x72 > > DATA[7] = 0x14 > > ID = 0x0 > > > > Transmission code active 0xc080000 > > reg->caniflg = 0x3 > > ** MB[1] : CODE=0x6 LEN=8 > > ** RX > > OVERRUN > > DATA[0] = 0x4c > > DATA[1] = 0x2e > > DATA[2] = 0x1 > > DATA[3] = 0x42 > > DATA[4] > > * incomplete received data printing... > > * THEN reboot HERE... > > Do you have a watchdog in the system, that can cause the reboot? > Does it always reboot in the middle of DATA[4]? > > > I know there is a buffer overrun on MB[1] (CODE = 0x6) which mean that > a > > frame > > was overwritten into a full buffer. > > The overflow is probably due to high load caused by the debug output. > > [...] > > > There is an update here: > > Looks like an update for some Eclipse plugins... > > cheers, Marc > > -- > Pengutronix e.K. | Marc Kleine-Budde | > Industrial Linux Solutions | Phone: +49-231-2826-924 | > Vertretung West/Dortmund | Fax: +49-5121-206917-5555 | > Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de | > >
_______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
