can0 config is old format -- can't install

[andyalford]

run again from command line, delete can0 and add it back to update config

-> I keep getting this message for can0 and can1, and at the same time, I do not seem to reliably get my can config to work.
-> For example, I add can10 and then restart and get can0 listed.

I think I have some old files stuck in my Pi system, can you advise what I should do?

Thanks

[kwindrem]

It sounds like you might have a CANbus hat board plugged in. These will automatically configure as can0 and can1 if the dt overlay is in place in /u-boot/overlays and called from /u-boot/config.txt.

VeCanSetup will never create a can0 or can1 device because there is a conflict with what Venus OS configures automatically. CANbus hats will be configured as can8 and can9 and USB CANbus interfaces will be configured starting with can10.

Don't confuse names you might give the device with the actual device number. The name can be anything you want it to be but I've seen some use "can0" so this can get very confusing.

If you want to completely remove all the stored configurations, install the package from the setup script then delete /data/setupOptions/VeCanSetup directory and all its contents. It is important to uninstall first to make sure the active files the script installs are removed.

[andyalford]

Thanks for the quick reply. I don’t have a CANbus hat board, but my installation has seen a few changes and gone through a few upgrades where I have used can0 / can1 a few times, so a cleanup seems to be a good idea. I think a typo in your last para, but this is my plan… * uninstall the package from the setup script * then delete /data/setupOptions/VeCanSetup directory and all its contents * A reboot, etc * Then fresh install and use an unambiguous name like ‘GobelPower01’ I’ll write to confirm anything I learn, in case anyone else can benefit. Thanks again for an excellent piece of work!! From: kwindrem ***@***.***> Sent: Sunday, November 26, 2023 6:02 AM To: kwindrem/VeCanSetup ***@***.***> Cc: andyalford ***@***.***>; Author ***@***.***> Subject: Re: [kwindrem/VeCanSetup] can0 config is old format -- can't install (Issue #32) It sounds like you might have a CANbus hat board plugged in. These will automatically configure as can0 and can1 if the dt overlay is in place in /u-boot/overlays and called from /u-boot/config.txt. VeCanSetup will never create a can0 or can1 device because there is a conflict with what Venus OS configures automatically. CANbus hats will be configured as can8 and can9 and USB CANbus interfaces will be configured starting with can10. Don't confuse names you might give the device with the actual device number. The name can be anything you want it to be but I've seen some use "can0" so this can get very confusing. If you want to completely remove all the stored configurations, install the package from the setup script then delete /data/setupOptions/VeCanSetup directory and all its contents. It is important to uninstall first to make sure the active files the script installs are removed. — Reply to this email directly, view it on GitHub <#32 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFKISVMUJB4AR3B46CFJBUTYGJTERAVCNFSM6AAAAAA72LMC5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGQZDQOBSGI> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AFKISVLXKC5MWKUSRUT4DPLYGJTERA5CNFSM6AAAAAA72LMC5OWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTM3ULZM.gif> Message ID: ***@***.*** ***@***.***> >