Closed tbaumann closed 10 months ago
$ sigrok-cli --version
sigrok-cli 0.7.1
Libraries and features:
- libsigrok 0.5.1/5:0:1 (rt: 0.5.2/5:1:1).
- Libs:
- glib 2.67.5 (rt: 2.68.4/6804:4)
- libzip 1.7.3
- libserialport 0.1.1/1:0:1 (rt: 0.1.1/1:0:1)
- libusb-1.0 1.0.24.11584 API 0x01000108
- hidapi 0.10.1
- bluez 5.56
- libftdi 1.5
- Host: x86_64-pc-linux-gnu, little-endian.
- SCPI backends: TCP, serial, USBTMC.
- libsigrokdecode 0.5.2/6:0:2 (rt: 0.5.3/6:1:2).
- Libs:
- glib 2.66.2 (rt: 2.68.4/6804:4)
- Python 3.9.0+ / 0x30900f0 (API 1013, ABI 3)
- Host: x86_64-pc-linux-gnu, little-endian.
Ubuntu 21.10
USB UART is connected to GPIO 1 and 3 according to https://docs.m5stack.com/en/core/atom_lite I suppose that means UART0/Serial
With "#define USE_SERIAL2_FOR_OLS 1" you should use UART2 device (with some other UART to USB dongle etc...) but you look like you are using UART0 because of "ets" word at pulseview error line...
You also shouldn't use UART0 because you don't have GPIO15. That silences boot messages so pulseview / sigrok should detect the device.
Only way that reset device via some terminal, remove all boot messages, than try to connect... but. I think it doesn't worth to fight with it. We should accept that your device is not compatible.
Hello! I make a new version and... You can use your board with it also! Only necessity is connecting 2 not-needed GPIO pins together... GPIO15 is not needed anymore.
Hi,
I need to look into closer detail of a IR sensor attached to an M5Stack Atom Lite. This looked perfect to analyse the timing.
I get it built and flashed no big deal.
With
With this default I get this
And I get some binary output on the serial monitor
With it set to
0
I get no output on serial. But sigrok isn't happy either.I suppose I'm either holding it wrong or I need to adapt it somehow to the hardware?
I do for example have no GPIO15 on this chip to tie down as the readme suggests.