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

Use XCPlite in an ECU #32

Closed
wants to merge 1 commit into from
Closed

Conversation

albert6541
Copy link

  • xcpTl.c/h implements XCP over CAN
  • main.c implements a scenario (connect, short up, daq, disconnect) to show behavior of XCPlite
  • xcpLite reused with modification:
    • avoid dependency on SOCKET from platform.h (could we split the networking part into a separate platform_networking.h?)
    • #error -> #warning, where does protocol assume CTO/DTO >= 16?
    • ApplXcpGetBaseAddr removed. Typical Win/Linux behavior should not be in protocol. Changed by ApplXcpGetPointer, this will increase run-time. Could we store the pointer from ApplXcpGetPointer instead of addr at the moment of XcpAddOdtEntry?
    • removed unused functions XcpEventAt and XcpEventExt (avoid usage of ApplXcpGetBaseAddr)

- xcpTl.c/h implements XCP over CAN
- main.c implements a scenario (connect, short up, daq, disconnect) to show behavior of XCPlite
- xcpLite reused with modification:
  - avoid dependency on SOCKET from platform.h (could we split the networking part into a separate platform_networking.h?)
  - #error -> #warning, where does protocol assume CTO/DTO >= 16?
  - ApplXcpGetBaseAddr removed. Typical Win/Linux behavior should not be in protocol. Changed by ApplXcpGetPointer, this will increase run-time. Could we store the pointer from ApplXcpGetPointer instead of addr at the moment of XcpAddOdtEntry?
  - removed unused functions XcpEventAt and XcpEventExt  (avoid usage of ApplXcpGetBaseAddr)
@RainerZ RainerZ closed this May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants