You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
change to '>' for multiple trices in one package (TriceOutMultiPackMode instead of TriceOutMultiSafeMode)
The text was updated successfully, but these errors were encountered: