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

Unable to decode channel 9-31 #225

Open
soerenbnoergaard opened this issue Aug 20, 2015 · 1 comment
Open

Unable to decode channel 9-31 #225

soerenbnoergaard opened this issue Aug 20, 2015 · 1 comment

Comments

@soerenbnoergaard
Copy link

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.
analyse_wing_data

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:
analyse_wing_data_2

My captured data (called Channel 0 though the trigger is on Channel 16 in the trigger setup) looks like this:
analyse_wing_data_3

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:
analyse_wing_data_settings_1
analyse_wing_data_settings_2
analyse_wing_data_settings_3

Kindest regards
Søren Bøgeskov Nørgaard

@soerenbnoergaard
Copy link
Author

I have found a work-around for this issue:

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.

Best regards
Søren Bøgeskov Nørgaard

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

No branches or pull requests

1 participant