-
Notifications
You must be signed in to change notification settings - Fork 42
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
Adapt transfer mode (compiler switch or better automate?) #306
Comments
rokath
changed the title
Branch trex: adapt transfer mode (compiler switch?)
Branch trex2: adapt transfer mode (compiler switch?)
Aug 20, 2022
-relaxPackgeCheck ? |
Automate this? |
rokath
changed the title
Branch trex2: adapt transfer mode (compiler switch?)
Branch trex2: adapt transfer mode (compiler switch or better automate?)
Aug 27, 2022
rokath
changed the title
Branch trex2: adapt transfer mode (compiler switch or better automate?)
Branchadapt transfer mode (compiler switch or better automate?)
Aug 27, 2022
rokath
changed the title
Branchadapt transfer mode (compiler switch or better automate?)
adapt transfer mode (compiler switch or better automate?)
Aug 27, 2022
rokath
changed the title
adapt transfer mode (compiler switch or better automate?)
Adapt transfer mode (compiler switch or better automate?)
Aug 27, 2022
The target code is configurable to have a 0-delimiter byte after each trice message (default) or to have several trice messages before a 0-delimiter byte (decision is only possible in double buffer mode). That reduces the binary data further but in a disruption case more messages are lost. This issue raises the question, how to tell the trice tool about the target setting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
change to '>' for multiple trices in one package (TriceOutMultiPackMode instead of TriceOutMultiSafeMode)
The text was updated successfully, but these errors were encountered: