Replies: 5 comments 3 replies
-
demo.c: #include "trice.h"
int main( void ){
trice( "msg:Hello World!\n");
return 0;
} Am I understand you right, that you want compile and run this on a PC as separate application, so that the trice tool grabs the binary data and displays "Hello World!"? To get that:
|
Beta Was this translation helpful? Give feedback.
-
The trice tool assumes TCOBS framing per default. When using COBS, you need to tell that via CLI. I am not sure what happens if you close and open the trice.raw file all the time. I would open it only once. When you have a trice.raw, the trice tool should be able to display it also alone. For that it maybe better to use |
Beta Was this translation helpful? Give feedback.
-
That are good news! I am unsure how to deal with the file trice/src/triceAuxiliary.c in a clean way. Any idea? |
Beta Was this translation helpful? Give feedback.
-
In main branch file ./src/triceAuxiliary.c is now changed into: #if TRICE_DIRECT_AUXILIARY == 1
//! UserNonBlockingDirectWriteAuxiliaryFn can get a user function address for writing to an auxiliary interface.
WriteAuxiliaryFn_t UserNonBlockingDirectWriteAuxiliaryFn = (void*)0;
//! TriceNonBlockingDirectWriteAuxiliary writes to a user defined interface.
void TriceNonBlockingDirectWriteAuxiliary( uint8_t const * enc, size_t encLen ){
if( UserNonBlockingDirectWriteAuxiliaryFn != (void*)0 ){
UserNonBlockingDirectWriteAuxiliaryFn( enc, encLen );
}
}
#endif // #if TRICE_DIRECT_AUXILIARY == 1
#if TRICE_DEFERRED_AUXILIARY == 1
//! UserNonBlockingDeferredWriteAuxiliaryFn can get a user function address for writing to an auxiliary interface.
WriteAuxiliaryFn_t UserNonBlockingDeferredWriteAuxiliaryFn = (void*)0;
//! TriceNonBlockingDeferredWriteAuxiliary writes to a user defined interface.
void TriceNonBlockingDeferredWriteAuxiliary( uint8_t const * enc, size_t encLen ){
if( UserNonBlockingDeferredWriteAuxiliaryFn != (void*)0 ){
UserNonBlockingDeferredWriteAuxiliaryFn( enc, encLen );
}
}
#endif // #if TRICE_DEFERRED_AUXILIARY == 1 This allows to add user code without editing the library code. It would be great, if you give it a try. |
Beta Was this translation helpful? Give feedback.
-
Should we close this now or do you want to make a pull request first? |
Beta Was this translation helpful? Give feedback.
-
After coming across the direct mode output option with Trice over RTT using a debug probe, was wondering if it would be possible to implement this feature without access to a device using protocols such as UART or USB, for example by routing the necessary data using another interface, and get the output to a console or virtual serial port
I've been looking for the OpenOCD Debugger in order to bypass any physical link, therefore taking advantage of all the Trice characteristics for an isolated application used for code development prior to an evaluation phase and hardware deployment
The main reason is to keep a sandbox-testing environment with the least amount of external interaction and as close to a pure-software domain
TLDR: objective - the goal is to explore the feasibility of implementing the Trice direct mode output option without the need for a physical device
Thank you and keep up the good work!
Beta Was this translation helpful? Give feedback.
All reactions