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 am using the Ubertooth-One board and attempting to retrieve (or set) IQ samples from the CC2400 chip. I have configured the registers as follows:
ATESTMOD_PD = 0 [to disable power down]
ATESTMOD_MODE = 0x2 [to output signals from the VGA]
These configurations should bring the IQ signals to pins ATEST1/2 (as referenced in issue #523). However, I am unable to observe these signals on the oscilloscope.
Could there be an issue with using ubertooth-rx alongside the modified firmware, or might there be another potential cause for this behavior?
Steps to Reproduce
Modify the firmware bluetooth-rxtx (details below).
Upload the modified firmware to the board.
Run ubertooth-rx in the terminal.
Connect pin ATEST1 or ATEST2 to an oscilloscope.
I added the following lines in the main function to enable the Analog Test Module (ATEST) of the CC2400:
I expected to observe the logic signals (high/low voltage) on the oscilloscope.
Actual Behavior
Instead of logic signals, I observed a constant voltage of 0.7V on the oscilloscope, while the terminal successfully outputs some decoded BLE information.
Version Information
Operating System:Ubuntu 18.04
Ubertooth tools version (ubertooth-rx -V):libubertooth 1.1 (2020-12-R1)
libbtbb version:libbtbb 1.0 (2018-06-R1)
Ubertooth firmware version (ubertooth-util -v):Firmware Version: 2020-12-R1 (API:1.07)
Thank you for your support and guidance! Please let me know if any additional details or clarifications are needed.
The text was updated successfully, but these errors were encountered:
Hi Team,
I am using the Ubertooth-One board and attempting to retrieve (or set) IQ samples from the CC2400 chip. I have configured the registers as follows:
These configurations should bring the IQ signals to pins ATEST1/2 (as referenced in issue #523). However, I am unable to observe these signals on the oscilloscope.
Could there be an issue with using
ubertooth-rx
alongside the modified firmware, or might there be another potential cause for this behavior?Steps to Reproduce
bluetooth-rxtx
(details below).ubertooth-rx
in the terminal.Expected Behavior
I expected to observe the logic signals (high/low voltage) on the oscilloscope.
Actual Behavior
Instead of logic signals, I observed a constant voltage of 0.7V on the oscilloscope, while the terminal successfully outputs some decoded BLE information.
Version Information
Ubuntu 18.04
libubertooth 1.1 (2020-12-R1)
libbtbb 1.0 (2018-06-R1)
Firmware Version: 2020-12-R1 (API:1.07)
Thank you for your support and guidance! Please let me know if any additional details or clarifications are needed.
The text was updated successfully, but these errors were encountered: