**** BEGIN LOGGING AT Mon Apr 04 02:59:56 2022 **** BEGIN LOGGING AT Mon Apr 04 07:40:04 2022 Apr 04 20:25:44 How can you upgrade from buster to bullseye on the BBB Apr 04 20:25:55 I need a new version of a package and I need to upgrade to do it Apr 04 20:26:07 mattb0ne: just one package? Apr 04 20:26:11 (which package) Apr 04 20:26:16 pyqt5 Apr 04 20:26:43 ah, that looks fun. ;) Apr 04 20:26:55 (qt5 would need to be rebuilt..) Apr 04 20:27:06 just edit /etc/apt/sources.list buster -> bullseye.. Apr 04 20:27:20 then sudo apt update ; sudo apt install apt dpkg ; sudo apt update ; sudo apt upgrade.. ;) Apr 04 20:27:59 even after going to bullseye? Apr 04 20:28:10 I need something later than 5.11 Apr 04 20:28:21 i saw that bullseye had 5.15 Apr 04 20:28:25 no... sadly, pyqt5... to backport that from bullseye to buster, would need the whole qt5 stack. ;) Apr 04 20:28:42 damn Apr 04 20:28:46 not sure I want to do that Apr 04 20:29:24 grab a spare board, install teh "lxde" image from here.. https://forum.beagleboard.org/t/debian-11-x-bullseye-monthly-snapshots/31280/4 and sadly qt5... Apr 04 20:29:38 lxde -> sorry xfce... Apr 04 20:30:42 how solid are these images Apr 04 20:31:07 what feature are you woried about... Apr 04 20:31:42 other then using v5.10.x-ti they are not any more tested then I tagged teh 2020-04-06 image 2 years ago... https://beagleboard.org/latest-images Apr 04 20:32:23 if you don't like v5.10.x, you can downgrade to any other major brnach: https://forum.beagleboard.org/t/debian-10-x-11-x-kernel-updates/30928 Apr 04 20:32:50 otherwise feel free to dist-upgrade your version of buster.. Apr 04 20:33:19 i am stuck in package limbo with pyqt5, I just do not want any other headaches Apr 04 20:33:37 pyqt5 depends on qt5... so it's already a headache.. Apr 04 20:33:43 lol Apr 04 20:34:24 you know, i see a lot of v5.9.x in pyqt's depends... Apr 04 20:34:32 i wonder if it would bui.d Apr 04 20:34:38 sudo apt update ; sudo apt install devscripts Apr 04 20:34:54 then: dget http://deb.debian.org/debian/pool/main/p/pyqt5/pyqt5_5.15.2+dfsg-3.dsc Apr 04 20:35:04 cd ./pyqt5-*/ ; debuild -us -uc Apr 04 20:48:31 back Apr 04 20:48:43 having some difficulties with windows 11 arrrgggg Apr 04 20:51:40 Sorry i tired the above on Buster, pyqt5 has more things that needed to be backported to Buster... Just grab a spare microsd and start fresh with bullseye, and set it up to mirror what your buster image does today.. Apr 04 20:57:59 ok Apr 04 20:58:01 this sucks Apr 04 20:58:14 I was fine and someone when and updated a package and broke my whole setup Apr 04 21:01:02 which package update broke it for you? Apr 04 21:01:51 pyqtgraph is the one complaining Apr 04 21:02:00 if I downgrade it wants pyqt4 Apr 04 21:02:05 which gives me other headaches Apr 04 21:02:47 https://packages.debian.org/source/buster/python-pyqtgraph Apr 04 21:02:55 yeah it depends on qt4.. Apr 04 21:03:21 here's all teh old debian versions.. https://snapshot.debian.org/package/python-pyqtgraph/ Apr 04 21:04:19 https://metadata.ftp-master.debian.org/changelogs//main/p/python-pyqtgraph/python-pyqtgraph_0.11.1-1_changelog qt5 first in python-pyqtgraph (0.10.0-2) python-pyqtgraph (0.11.0-6) _. full qt... Apr 04 21:04:22 https://metadata.ftp-master.debian.org/changelogs//main/p/python-pyqtgraph/python-pyqtgraph_0.11.1-1_changelog qt5 first in python-pyqtgraph (0.10.0-2) python-pyqtgraph (0.11.0-6) _. full qt5... Apr 04 21:12:33 so just to be sure if I switch to these monthly that are on bullseye I wont have a problem or I still will Apr 04 21:12:44 I know you answered but I am dense on these things Apr 04 21:33:41 back Apr 04 21:33:49 are these monthly flasher images Apr 04 21:33:53 not working for me Apr 04 21:47:34 what's "not working for me" Apr 04 21:48:51 I cannot load the monthly was it a flasher image? Apr 04 21:49:18 flashers cost me 2x the space.. (as we are adding arm64 and riscv) images.. Apr 04 21:50:30 if you want a flasher, i have one line command listed here: https://forum.beagleboard.org/t/debian-11-x-bullseye-monthly-snapshots/31280 "eMMC flasher"... Apr 04 21:50:44 https://www.irccloud.com/pastebin/Z8UmhbvY/ Apr 04 21:51:02 ok Apr 04 21:51:30 so I would boot from SD with the bullseye image Apr 04 21:51:44 then input those commands and it will move the OS from the SD to flash memory? Apr 04 21:52:36 correct.. Apr 04 21:53:20 after typing that first command, the microSD is now a "auto eMMC flasher" so if you have a bank of BBB"s you can flash them one at a time with the same microSD.. Apr 04 21:55:00 would I restart and hold the button or the first one is already convereted Apr 04 21:55:05 converted* Apr 04 21:56:08 if i want to run a cpu intensive dsp operation, is it reasonable to do the analog i/o on the pru's, and the math in the application processor? Apr 04 22:50:02 solrize: what do you mean by "do the analog i/o" ? Apr 04 22:56:46 if you want to process samples from the integrated adc on the cortex-a8 then just using the kernel driver to stream the data probably makes more sense than using pru Apr 04 22:58:48 but there are certainly situations where using pru to perform i/o and then streaming that data to the cortex-a8 (e.g. via a ringbuffer) for further processing makes sense Apr 04 22:59:24 your description is too vague to really make any kind of judgement on whether it does in your specific situation **** BEGIN LOGGING AT Mon Apr 04 23:06:59 2022 Apr 04 23:08:53 normally the adc periodically samples the enabled inputs, at a rate that depends on the configuration defined using device tree properties, and the linux driver will stream these to memory using DMA Apr 04 23:09:25 zmatt, ah ok, i didn't realize that. yeah that would do it Apr 04 23:09:26 thanks Apr 04 23:09:42 some details about this DT configuration and resulting timing: https://github.com/mvduin/overlay-utils/blob/master/adc.dtsi Apr 04 23:10:22 is there also a dac? Apr 04 23:11:41 and is there just one adc muxed between those pins? Apr 04 23:12:12 not really no, there are pwm outputs but no sigma-delta modulator or something... could be something that could be made with pru probably Apr 04 23:12:16 (dac) Apr 04 23:12:51 and yes it's a single adc shared between the 8 inputs, i.e. it will sample and convert the enabled inputs sequentially, not simultaneously Apr 04 23:13:39 if you want something better you may want to consider interfacing an external audio codec Apr 04 23:14:05 but it depends on the application... if you're doing 8 kHz sampling then it doesn't sound like you're aiming for particularly high quality anyway Apr 04 23:15:11 well it's going into a radio tranceiver... wondering if pocketbeagle would be suitable for this https://hackaday.com/2021/09/25/the-simplest-ft8-transceiver-youll-ever-build/ Apr 04 23:15:38 in order to get slightly higher audio sample rate, and do more modulations Apr 04 23:17:11 and the general conveniences of programming linux ;) Apr 04 23:19:20 ah Apr 04 23:19:56 yeah, that doesn't sound like it needs a particularly good audio quality Apr 04 23:21:51 cool, pocketbeagle is still a nice board despite being kind of old by now thanks Apr 04 23:21:53 and for the output you could probably perform the sigma-delta encoding in advance for the various tones you need to generate and have PRU output those directly (and then add an analog low-pass filter) Apr 04 23:22:11 oh interesting point yeah Apr 04 23:22:57 or just add a dac... this is not so tiny any more but it is still ok Apr 04 23:23:58 do you think the adc resolution matters much? i am wondering why the original design uses the pjrc teensy 3 (which has 13 bit adc's but is cpu limited) instead of the teensy 4 (much faster cpu, but 10 bit adc) Apr 04 23:24:08 for this? nah Apr 04 23:24:18 hmm maybe can just use teensy 4 then Apr 04 23:24:44 the am335x adc is 12-bit Apr 04 23:26:05 https://www.pjrc.com/teensy/techspecs.html i was looking here and it says 10 Apr 04 23:26:07 up to 200 kHz sampling (shared across the inputs, so up to 25 kHz when having all 8 inputs enabled) Apr 04 23:26:17 am335x is what's on the pocketbeagle and beaglebone Apr 04 23:26:22 right yeah, 12 bits Apr 04 23:26:50 don't need 8 inputs but need about 4, two of them slow Apr 04 23:27:13 well maybe a few more really slow, for stuff like battery monitoring Apr 04 23:27:24 that would just make things inconvenient Apr 04 23:28:00 hmm they would interfere with the audio sampling? Apr 04 23:28:18 yes Apr 04 23:28:42 oh blech. i see Apr 04 23:29:10 like, the best you could do is probably run the slow ones at half the sampling rate by using the sampling pattern { 0, 1, 2, 0, 1, 3 } (where 0 and 1 are the fast inputs and 2 and 3 the slow ones) Apr 04 23:29:49 that sounds ok, or could just use a tiny mcu board for the slow stuff Apr 04 23:29:50 assuming the kernel driver tolerates having multiple steps for the same input (the adc is fine with that, dunno the driver) Apr 04 23:30:21 or some i2c adc Apr 04 23:30:36 yeah Apr 04 23:30:55 or use a proper external adc for the fast stuff and the integrated one for the misc inputs Apr 04 23:31:04 plenty of options Apr 04 23:31:13 two of the slow channels are to read a touch screen, so an mcu could do that whole thing and just report coordinates Apr 04 23:31:31 well the integrated adc is also a resistive touchscreen controller Apr 04 23:31:36 yeah i guess so, if sampling and dma are how it is usually done Apr 04 23:31:44 oh interesting Apr 04 23:32:25 maybe can ditch the touch screen altogether, and use a phone for the UI Apr 04 23:32:49 all valid options Apr 04 23:32:56 i wonder if the whole thing can be done as a phone app, with just the adc/dac external? hmm Apr 04 23:33:16 as if your phone doesn't have an audio adc and dac? :D Apr 04 23:33:40 yeah maybe that suffices Apr 04 23:33:44 oh right, need the rf stuff Apr 04 23:34:21 you can bet that your phone's adc and dac are better than what the pocketbeagle or a teensy has to offer Apr 04 23:34:26 i'm a good linux programmer but don't know that much about hardware or phone apps Apr 04 23:34:27 and definitely more processing power Apr 04 23:34:36 interesting Apr 04 23:34:58 just using the 3.5mm headphone jack (which on my phone sucks pretty bad, and which is going extinct on newer phones though) Apr 04 23:35:49 i guess getting a carefully chosen phone for the purpose is acceptable Apr 04 23:36:18 newer phones probably still support analog audio in/out via the usb-c port (via a passive converter) ? Apr 04 23:37:05 anyway, lots of ways you could implement this Apr 04 23:37:09 there are analog pins in usb-c? omg Apr 04 23:37:13 ok thanks Apr 04 23:37:35 i'll look into stuff some more Apr 04 23:37:36 there's a weird but standardized hack to use the usb-c plug to transform analog audio yeah Apr 04 23:37:41 solrize: usb-c alt mode's.. Apr 04 23:38:22 https://en.wikipedia.org/wiki/USB-C#Alternate_Mode_partner_specifications Apr 04 23:38:26 https://en.wikipedia.org/wiki/USB-C#Audio_Adapter_Accessory_Mode yikes that poor little connector Apr 04 23:38:30 yeah i was looking there too Apr 04 23:38:43 they are going to send 240 watts of power and multi-ghz signals through it Apr 04 23:38:47 and also analog Apr 04 23:39:08 scarry, i won't trust that signal. ;) Apr 04 23:39:11 well, when Audio Adapter Accessory mode is used there's no digital data going over it Apr 04 23:40:01 ah you mean there are the two traditional signal pins, and these modes change their functions Apr 04 23:40:05 so no using with a hub Apr 04 23:40:06 ok Apr 04 23:40:28 and charge-through in that mode only supports 5V 500 mA Apr 04 23:40:55 actually in audio mode, tx/rx's get disabled... so your device only has to worry about 240 watt's thru Vbs/gnd.. so audio might be fine.. at full load.. Apr 04 23:41:08 as long as that load doesn't change... Apr 04 23:41:09 2.5 W max Apr 04 23:41:29 ah, i see that at the bottom.. was thinking about the normal power charging.. Apr 04 23:41:33 thanks! Apr 04 23:41:37 the audio accessory grounds both CC pins (which is how the phone recognizes it) Apr 04 23:41:57 which prevents charger current detection and PD communication Apr 04 23:42:19 ok i will read this Apr 04 23:42:41 yeah jeez, i sort of had the idea of using the phone to power the external stuff.. i thought there was a way to do that with usb-c Apr 04 23:42:42 hence no way to go above 5V 0.5A Apr 04 23:42:57 sure, but not in audio accessory mode Apr 04 23:43:03 but 2.5w into the phone sounds like plenty, i hope, to be able to run the thing from external power Apr 04 23:43:59 anyway, all this is of course only relevant if you actually want to get into making a phone app Apr 04 23:44:05 which is its own set of headaches Apr 04 23:44:24 yeah :(. i've never done it but it's closer to my clue area than this electronic stuff Apr 04 23:45:41 ok well i'll think about this some more, i gotta go now before the bank closes. thanks 1e6 again Apr 05 02:51:01 so I habe a bullseye image but my apt is referencing buster **** ENDING LOGGING AT Tue Apr 05 02:59:57 2022