Hello,
I'm running into exactly the same issue as YoanEyeLights after updating to the 6.5 kernel.
Could you pelase send me the patch as well (or make it publicly available, since it will most likely affect more people after the update to the 6.5 kernel was recently released)?
Thanks in advance ...
Search found 4 matches
- Mon 15. Jan 2024, 09:55
- Forum: Linux
- Topic: problem building peak linux driver
- Replies: 7
- Views: 9573
- Tue 13. Mar 2018, 11:38
- Forum: PCAN-Basic
- Topic: CAN_initialize failing after 'Stop Debugging' in VS 2015
- Replies: 7
- Views: 14170
Re: CAN_initialize failing after 'Stop Debugging' in VS 2015
After a little bit more research i can confirm that it does work with the 64 Bit version of the PCAN-Basic library.
However, if i use the 32 Bit version of the library, it does not.
I'll try to switch my application to 64 Bits.
However, if i use the 32 Bit version of the library, it does not.
I'll try to switch my application to 64 Bits.
- Mon 12. Mar 2018, 15:07
- Forum: PCAN-Basic
- Topic: CAN_initialize failing after 'Stop Debugging' in VS 2015
- Replies: 7
- Views: 14170
Re: CAN_initialize failing after 'Stop Debugging' in VS 2015
Thanks for the quick reply! I am using Windows 10. Even after a few minutes the abandoned connection seems not to be cleared.
- Mon 12. Mar 2018, 14:13
- Forum: PCAN-Basic
- Topic: CAN_initialize failing after 'Stop Debugging' in VS 2015
- Replies: 7
- Views: 14170
CAN_initialize failing after 'Stop Debugging' in VS 2015
Hello,
i use a PCAN USB Dongle with driver version 4.1.3. Initializing a channel works fine until the application is closed during debugging with the 'Stop Debugging' button in Visual Studio. Afterwards, CAN_Initialize always returns PCAN_ERROR_INITIALIZE. The only workaround i found so far is ...
i use a PCAN USB Dongle with driver version 4.1.3. Initializing a channel works fine until the application is closed during debugging with the 'Stop Debugging' button in Visual Studio. Afterwards, CAN_Initialize always returns PCAN_ERROR_INITIALIZE. The only workaround i found so far is ...