Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sorry, I am a rookie. Who triggered this vendor packet? #188

Closed
tonghiden opened this issue Feb 19, 2025 · 12 comments
Closed

sorry, I am a rookie. Who triggered this vendor packet? #188

tonghiden opened this issue Feb 19, 2025 · 12 comments
Labels

Comments

@tonghiden
Copy link

tonghiden commented Feb 19, 2025

Who triggered this vendor packet? Why does this trigger as soon as I open the software?

Image

Image

@marckleinebudde marckleinebudde changed the title sorry,iam a rookie,Who triggered this vendor packet? sorry,iam a rookie. Who triggered this vendor packet? Feb 19, 2025
@marckleinebudde marckleinebudde changed the title sorry,iam a rookie. Who triggered this vendor packet? sorry, I am a rookie. Who triggered this vendor packet? Feb 19, 2025
@marckleinebudde
Copy link
Collaborator

Which Software are you opening?

@tonghiden
Copy link
Author

Yes, I opened the Cangaroo software because I ported the descriptors to another chip platform (gd32), but my ported code did not receive the vendor package. Why

Image

@marckleinebudde
Copy link
Collaborator

What software did you actually port to the gd32?

@tonghiden
Copy link
Author

candleLight1.0

@marckleinebudde
Copy link
Collaborator

You mean https://github.com/candle-usb/candleLight_fw/tree/v1.0 ? This is 9 years... :/

You may want to diff the frames with the original firmware and your gd32 port and see if there's something different before this.

If not, then there's probably something wrong with your device setup.

@tonghiden
Copy link
Author

Hahaha, forgot, didn't you? Yes, it's been too long.But if you can remember, please help me see if there is any mark missing, because I didn't receive the vendor package when I opened the cangroo.exe on my own device, https://github.com/candle-usb/candleLight_fw/tree/v1.0 Yes, so, I wonder if some tags are missing so that the software can't recognise me, so they don't send me the vendor package, you know why?Also, I've got Windows to load up.,ths

Image

@tonghiden
Copy link
Author

tonghiden commented Feb 20, 2025

Image

Image
In addition, it is possible that a certain software has only been used in my country. I also tried it under Ubuntu and found that it couldn't form can0, and then I typed dmesg and found that it described [49401.290509] gs_usb 2-2.1:1.0: Couldn't send data format (err=-110)

@fenugrec
Copy link
Collaborator

Do I understand correctly that you're using the 1.0 tree, which is ancient and very different from current codebase; ported it to a different platform, are not even showing your code, and expect us to provide support ?

@tonghiden
Copy link
Author

tonghiden commented Feb 20, 2025

Image

Image
Sorry, maybe my description is wrong, I will re-describe. I bought a device with a chip STM32F07X in the shop, and then I compiled the source code of Candlelight1.0 and burned it to the device I purchased. I then used a Windows software called Cangroo; all the functions are normal, the message sending and receiving are perfect, and "can0" can also be loaded on Ubuntu. This proves that the code is compatible with the device (picture 1). Then I started to move Candlelight1.0 to another device (gd32/ch32), and when I thought the porting was complete, I found that Windows recognised the device and could enumerate it (Picture 2), but the software didn't recognise my ported device, and it couldn't load "can0" on Ubuntu. So, I used the packet capture method and found that the vendor was missing. The main issue is that on the Ubuntu side, there was no enumeration of any CAN devices, and then I entered dmesg. Hint: [50184.221105] gs_usb 2-2.1:1.0: Couldn't send data format (err=-110). So, can you help me find out what's wrong?

@marckleinebudde
Copy link
Collaborator

Your firmware fails with a timeout https://github.com/torvalds/linux/blob/master/include/uapi/asm-generic/errno.h#L93 when the Linux driver sends the host config https://github.com/torvalds/linux/blob/v6.13/drivers/net/can/usb/gs_usb.c#L1433

There's a problem with your firmware. As you're using a branch that's over 9 years old and you don't show us your code, I don't see any possibilities to help any further.

@tonghiden
Copy link
Author

Oh, thank you. This has been very helpful to me. I'm sorry, I forgot to upload the code because I think the entire project is a bit large and inconvenient, and some parts are encrypted by software. I will try my best to troubleshoot this issue

@fenugrec
Copy link
Collaborator

I recommend you don't waste time with the 1.0 tree for reasons stated above.

Closing as currently out of scope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants