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
I have unfortunately fried my on-board buffer chip, so I have bought a buffer wing and use channel group 2 and 3 in ols.
I have today tried to use the UART analyser to decode some simple UART. However, I only see an option to choose channel 0-7 for any of the options.
I can capture and trigger on, e.g., channel 16 with no problem. I figured, if I only have 8 tracks on the screen and the first one is the data I want to decode, maybe choosing "Channel 0" would be the solution. Doing so, I get the following result:
My captured data (called Channel 0 though the trigger is on Channel 16 in the trigger setup) looks like this:
I use OLS version 0.9.7.2 on Linux soren-arch 4.1.4-1-ARCH #1 SMP PREEMPT Mon Aug 3 21:30:37 UTC 2015 x86_64 GNU/Linux.
My settings are:
Kindest regards
Søren Bøgeskov Nørgaard
The text was updated successfully, but these errors were encountered:
If both Channel Groups 0, 1, and 2 are enabled (in OLS Capture Settings -> Acquisition above), all channels from 0 to 23 can be chosen in the UART decoder.
However, this effectively cuts the sample memory to one third so it is not a good solution.
I have unfortunately fried my on-board buffer chip, so I have bought a buffer wing and use channel group 2 and 3 in ols.
I have today tried to use the UART analyser to decode some simple UART. However, I only see an option to choose channel 0-7 for any of the options.
I can capture and trigger on, e.g., channel 16 with no problem. I figured, if I only have 8 tracks on the screen and the first one is the data I want to decode, maybe choosing "Channel 0" would be the solution. Doing so, I get the following result:
My captured data (called Channel 0 though the trigger is on Channel 16 in the trigger setup) looks like this:
I use OLS version 0.9.7.2 on Linux soren-arch 4.1.4-1-ARCH #1 SMP PREEMPT Mon Aug 3 21:30:37 UTC 2015 x86_64 GNU/Linux.
My settings are:
Kindest regards
Søren Bøgeskov Nørgaard
The text was updated successfully, but these errors were encountered: