**** BEGIN LOGGING AT Thu Nov 10 02:59:57 2022 Nov 10 11:48:49 I tried the vs code solution, but I probably messed up some step along the way Nov 10 12:32:11 sudo apt install bb-code-server && sudo systemctl enable bb-code-server ? Nov 10 12:33:32 I was reading in the forums. It seems those two commands install it and enable it for booting into the server when starting the BBB. Nov 10 12:33:52 Use the 3000 port. Nov 10 12:33:55 So I start the vs code at my windows' machine side Nov 10 12:34:04 Yes and no. Nov 10 12:34:11 You go to the web browser. Nov 10 12:34:20 But it is served from the BBB. Nov 10 12:34:22 my pocket only has a terminal Nov 10 12:34:28 oh on the windows side Nov 10 12:34:31 Yes. Nov 10 12:34:47 So, your IP_ADDRESS:3000 Nov 10 12:34:58 for instance, 192.168.7.2:3000 Nov 10 12:35:02 maybe it will have to wait a while, I tried to set up a static ip address for my pocket and now cant ssh into it anymore Nov 10 12:35:10 No! Nov 10 12:35:14 Fine. Nov 10 12:35:36 I am battling arducopter on my bbblue now. Nov 10 12:35:42 Dying at every turn. Nov 10 12:35:43 is there a solution other than reflashing it? Nov 10 12:35:50 Um... Nov 10 12:35:52 Maybe. Nov 10 12:36:35 Someone else will have to help you, though. I may take two years to conquer the issues at hand. Nov 10 12:36:58 Oh. Nov 10 12:37:00 COM ports Nov 10 12:37:04 Try that... Nov 10 12:37:20 Do you use PuTTY and have a valid IP Address? Nov 10 12:37:52 I use bitvise and used to ssh with 192.168.7.2/ Nov 10 12:37:57 Right. Nov 10 12:37:59 Okay. Nov 10 12:38:17 but I edited /etc/network/interfces Nov 10 12:38:53 So, go to your Home Explorer where the Borris Icon shows itself. Nov 10 12:39:39 you the getting started? Nov 10 12:39:42 you mean* Nov 10 12:40:08 Under the Icon, open the file folders. Right click and go to preferences. Nov 10 12:40:18 Sure. Nov 10 12:40:50 BeagleBone Getting Started Nov 10 12:40:52 Right. Nov 10 12:41:14 Then, right click and go to preferences. YOu will find a COM Port in one of the options in the task menu. Nov 10 12:41:38 Then, in your TTY editor, go to the COM Port listed from the preferences tabs. Nov 10 12:42:35 Sorry. Nov 10 12:42:41 Ok, I open my computer and I can see Beaglebone getting started as my E disc Nov 10 12:42:45 Not preferences. It is called properties. Nov 10 12:42:50 Okay. Nov 10 12:42:54 Right click the icon. Nov 10 12:43:08 It is the dog icon, Borris. Nov 10 12:43:19 ok Nov 10 12:43:43 Under properties, there should be something. Let me check real quickly. My board is booting now. Nov 10 12:43:43 there is six tabs, general,tools,hardware,sharing,readyboost and customize Nov 10 12:45:19 I think I know how I messed up, when I edited interfaces, I placed this: Nov 10 12:45:19 auto usb Nov 10 12:45:20 iface usb0 inet static Nov 10 12:45:20 address 192.168.1.200 Nov 10 12:45:21 netmask 255.255.255.0 Nov 10 12:45:21 gateway 192.168.1.254 Nov 10 12:45:29 maybe I should have used another name Nov 10 12:45:32 Okay. I am wrong now. There used to be a COM Port. Nov 10 12:45:33 Ha. Nov 10 12:45:40 like eth0 Nov 10 12:45:57 I think USB_Gadgets took over and they solved the error of Windows 11 systems. Nov 10 12:46:02 I don't much about networking Nov 10 12:46:11 so I need to reflash it? Nov 10 12:46:15 Let me try something. Nov 10 12:46:24 I will brb w/ nay or yay. Nov 10 12:47:11 Okay. Nov 10 12:47:12 ! Nov 10 12:47:14 Good news. Nov 10 12:47:27 In your Serial Editor. Nov 10 12:47:41 Try COM ports starting at 1, i.e. COM1. Nov 10 12:47:47 If that is not it, try COM2. Nov 10 12:47:49 And so on. Nov 10 12:48:00 Try that until you find the correct COM port. Nov 10 12:48:04 Mine was COM4. Nov 10 12:48:32 Then, change your hardware quickly before it times out. Nov 10 12:48:42 Serial editor? Nov 10 12:48:55 yea. Not PuTTY but whatever you called it. Nov 10 12:49:05 oh Nov 10 12:49:06 ok Nov 10 12:49:13 i found, mine is 5 Nov 10 12:49:15 lets try it Nov 10 12:49:45 Do it! Nov 10 12:49:59 Alright, it may solve the issue of not logging in w/ USB. Nov 10 12:51:01 so you mean, where I place the ip, 192.168.7.2, i place now COM5? Nov 10 12:51:21 No. Nov 10 12:51:41 Let me check...what your interface looks like. Please hold. Nov 10 12:51:59 i have putty Nov 10 12:52:03 bitvise. Okay. Let me go and search this tool. Nov 10 12:52:04 i can just change for this Nov 10 12:52:05 Oh? Nov 10 12:52:08 Okay. Nov 10 12:52:32 Serial and not SSH. Nov 10 12:52:44 got it Nov 10 12:52:49 I am in Nov 10 12:52:51 Then, in the address bar, type COM5. Nov 10 12:52:54 connect. Nov 10 12:52:56 Oh! Nov 10 12:52:57 Good. Nov 10 12:53:56 so I was following this guide Nov 10 12:53:57 https://www.petemillsdev.com/Beaglebone-getting-started-p2 Nov 10 12:54:21 that said I needed to already have a static ip Nov 10 12:54:41 No. Nov 10 12:54:42 so edit the interfaces like I said above Nov 10 12:54:49 and caused this mess Nov 10 12:54:54 What are you trying to do? Nov 10 12:55:31 uart0_person: There are some forums for people called forum.beagleboard.org . Nov 10 12:55:46 With raspberry pi, I used samba so I could access the pi folders from my windows machine. With this I could open my code files with an ide Nov 10 12:56:03 They have people there, well and here too, that do things w/ the am335x and Linux. Nov 10 12:56:04 oh! Nov 10 12:56:09 basically, I want to remotely code using the ides inside my windows machine Nov 10 12:56:27 but I don't know how to do anything without guides Nov 10 12:56:41 and the guides I find assume I connecting via wifi to the board Nov 10 12:56:41 sudo apt install bb-code-server Nov 10 12:56:52 Oh. Nov 10 12:57:11 I got it now. Do you have the Ethernet attached yet? Nov 10 12:57:28 I think it is five pins from the Pocket Beagle. Nov 10 12:58:41 do I need ethernet or can I use the usb connection? Nov 10 12:59:08 when seeing the connections inside my windows machine, the pocket connection is listed as ethernet 2 Nov 10 12:59:39 Well... Nov 10 12:59:47 Hmm. Nov 10 13:00:09 I have not used the Pocket Beagle before today. I do not have one to test. Nov 10 13:00:21 Let me go and read some. Nov 10 13:01:54 Here: https://github.com/beagleboard/pocketbeagle/wiki/FAQ#how-do-i-get-connected-to-the-internet Nov 10 13:02:54 Oh, my pocket is already connected to the internet through the usb connection Nov 10 13:02:58 That will take some work. Neat. Nov 10 13:03:04 Oh. Nov 10 13:03:18 You can access the Internet? Nov 10 13:03:30 w/ WiFi or tethering or Ethernet? Nov 10 13:04:35 in my windows machine, I set my internet connection to share with the name of the usb connection to pocket Nov 10 13:04:49 which is ethernet2 Nov 10 13:05:33 Oh! Nice. Nov 10 13:05:36 Tethering. Nov 10 13:05:37 here, I followed this guide Nov 10 13:05:38 https://www.google.com/search?client=firefox-b-d&q=internet+over+pocketbeagle+usb Nov 10 13:05:40 Okay. Nov 10 13:06:26 sorry I am kinda ignorant about this subject and I am only sending the guides I am following instead of knowing how to do things myself Nov 10 13:06:46 I used to know. I used to follow guides. I still follow guides. Nov 10 13:07:07 I used to know how to tether the BBB from a guide from Adafruit_BBIO. Nov 10 13:07:16 But...I just went to look it up. No more... Nov 10 13:08:46 I used to have it written somewhere. Back to the files! Nov 10 13:13:11 Oh well... Nov 10 13:13:19 I will not find it until it is time. Nov 10 13:13:24 oh! BBL! Nov 10 13:21:09 well, thank you for the help so far Nov 10 13:30:56 idk if it helps anything figuring out how to do the remote thing, but my ifconfig output is this: Nov 10 13:30:57 https://pastebin.com/NzSiC7A3 Nov 10 13:57:37 "the remote thing" (neither sshfs nor vscode remote development via ssh) doesn't require any sort of meddling with networking nor any configuration on the beaglebone whatsoever Nov 10 13:57:54 since you can already ssh into the beaglebone and that's all it needs Nov 10 13:59:00 I tried adding the same ip I use for ssh into vs code remote plugin Nov 10 13:59:09 but it doesn't connect Nov 10 14:01:30 like https://code.visualstudio.com/docs/remote/ssh#_connect-to-a-remote-host says, the exact same user@host (i.e. debian@192.168.7.2) that works for normal ssh should work for vscode Nov 10 14:07:20 (since vscode *uses* ssh to connect) Nov 10 14:13:22 Could not establish connection to "192.168.7.2" Nov 10 14:13:36 its the vs code output when I try Nov 10 14:14:23 but ssh from the commandline (cmd.exe or powershell) does work? Nov 10 14:15:29 (i.e. what step 1 requests you to verify) Nov 10 14:15:31 I use bitvise for ssh, but yeah, using that same ip Nov 10 14:16:05 I didn't ask whether ssh using some other software worked Nov 10 14:16:21 oh sorry Nov 10 14:16:46 one moment Nov 10 14:16:52 I asked whether using the ssh command invoked from the commandline worked, since that's what vscode requires (as it does the same thing behind the scenes) Nov 10 14:17:07 and it's what vscode's guide explicitly asked you to verify Nov 10 14:19:22 i thought if I could ssh from the software, it meant it worked Nov 10 14:21:36 I need to add a key to known hosts to make it work Nov 10 14:22:19 it'll offer to add a key to known hosts if it's missing Nov 10 14:23:33 I did ssh debian@192.168.7.2 and give me warnings saying the key was changed and needed to add the key, but it didn't me the option to add Nov 10 14:24:26 if there's a conflicting entry in known hosts then you need to *remove* that entry, not add one Nov 10 14:24:49 recent versions of ssh actually give you the command to remove the conflicting entry, but I guess windows still ships an older versions Nov 10 14:25:28 ok, deleted and now added the ip Nov 10 14:25:35 now I can ssh with powershell Nov 10 14:26:08 ok, it seems i can ssh with vscode now Nov 10 14:26:39 turns out following step 1 of the instructions in the guide actually helps :P Nov 10 14:27:18 now wait for the setup to finish Nov 10 14:44:19 ok, now I can ssh into pocketbeagle with vs code Nov 10 14:44:20 finally Nov 10 14:46:32 just one last question Nov 10 14:46:51 in my pocketbeagle I downloaded the API dronekit Nov 10 14:47:08 is there a way with vs code I can autocomplete the code? Nov 10 14:48:17 probably? I've never used vscode myself but I know autocompletion is definitely a feature, though I don't know what things it can autocomplete exactly (but anything not supported out of the box probably has some extension/plugin out there that will) Nov 10 14:48:53 i think the name is IntelliSense Nov 10 16:58:54 Hello, I'm having some trouble with PWM accuracy. I'm trying to use it to get a 12.0 MHz clock signal, but it varies between 12.5MHz and 11.1MHz on my oscilloscope, the difference is me changing period from 79 ns to 80 ns. 79 ns is a 12.5 MHz and 80 ns is 11.1 MHz. Why the huge difference at this step? Is the PWM channel just not accurate enough Nov 10 16:58:54 for this purpose Nov 10 17:01:25 there are three types of peripherals on the BBB that can generate a PWM signal: eHRPWM and eCAP devices run off a 100 MHz clock hence can only vary the period in 10ns steps, the Timer peripherals run on a 24 MHz clock hence these can produce a 12 MHz clock Nov 10 17:02:19 for some reason the timer pwm outputs aren't enabled by default, but there are overlays to enable them (/lib/firmware/BB-PWM-TIMER-P8.*) Nov 10 17:05:22 Ah, thanks that makes a lot of sense. Nov 10 17:10:23 How do I config timer pins once I have the overlay? Nov 10 17:13:38 right, /etc/udev/rules.d/81-pwm-noroot.rules is missing rules for creating symlinks for these in /dev/pwm/ ... hold on Nov 10 17:16:56 I guess something like https://pastebin.com/YXzY9LU4 should fix it, lemme test Nov 10 17:22:16 yep that works, https://pastebin.com/G90qSFA4 Nov 10 17:33:21 for completeness I've also added examples to overlay-utils, including one that enables all four timer pwm outputs on P8: https://github.com/mvduin/overlay-utils/commit/eab34a0e37eeee246b0c12e4e04fe3785cc9427f Nov 10 17:33:59 (note: the timer pwm outputs also have alternative mux options on some P9 pins, if you want to use one of those you'd need to make a custom overlay for that) Nov 10 17:54:10 so to apply, do I just edit my pwm-noroot.rules file? Nov 10 17:54:56 enable the overlay (to create the pwm devices) and edit the udev rules rule (to create symlinks in /dev/pwm/) Nov 10 17:55:18 the latter is of course just for convenience of being able to easily locate the pwm outputs Nov 10 18:35:12 Still having trouble getting timer to show up in  ls -l /dev/pwm/. I edited the rule adding all four timers and added uboot_overlay_addr0=/lib/firmware/BB-PWM-TIMER-P8.9 to my uEnv.txt file, for timer5 Nov 10 18:40:02 you mean uboot_overlay_addr0=/lib/firmware/BB-PWM-TIMER-P8.09.dtbo ? Nov 10 18:45:27 Ah. That might be it Nov 10 18:45:47 configuring the path of a file that actually exists may help Nov 10 19:00:35 Thank you, it's starting to work. Though now when I write to the pwm, writing period as 83 and duty as 42 seems to be giving me 686 Hz, not 12MHz Nov 10 19:01:24 wut Nov 10 19:02:41 can you check: grep timer5 /sys/kernel/debug/clk/clk_summary Nov 10 19:03:24 grep timer5 /sys/kernel/debug/clk/clk_summary Nov 10 19:03:25        timer5_fck 1 1 0 24000000 0 0 50000 Nov 10 19:26:49 nick12310: https://drive.google.com/file/d/1llS4onj3jzkK5_ZQzhcKHJNb14OHbJz0/view?usp=sharing a small utility that dumps the configuration of all timers directly from hardware (requires sudo) Nov 10 19:34:13 https://pastebin.com/8JuKbvkG Nov 10 19:42:29 ... it sure seems to claim it ought to be producing a 12 MHz clock? Nov 10 19:43:22 a 12 MHz pwm output I mean Nov 10 19:48:53 and the timer5 clock seems to be 24 MHz indeed... if I configure a period of 2 seconds and then monitor the 'timer 5 counter' value (using e.g. watch -n 0.1 sudo ./check-timers ) then the counter indeed appears to wrap every 2 seconds Nov 10 19:49:03 Yeah. I really don't know at this point, could it be a hardware issue somehow? Nov 10 19:49:45 (interestingly if I try to configure a 3 second period the math in the kernel driver seems to blow up and it programs a 51.5 second period instead, lol) Nov 10 19:53:45 nick12310: I don't have an easy way to verify the output (I could do that tomorrow at work), but as far as I can tell the timer is working correctly and at the correct frequency Nov 10 19:54:35 Yea, very weird. Anyways thanks for taking a look Nov 10 19:55:05 Is it possible to do this with a pru pin? It seems like the timer is giving me enough trouble lol Nov 10 19:55:30 that would be much much harder Nov 10 19:56:19 are you sure your measurement is right? Nov 10 19:56:32 (and you measured the right pin? :P ) Nov 10 20:01:47 Lol nvm yea... I never zoomed in all the way. There is a 680 Hz square wave for sure. After I actually zoom in a 12 MHz square wave shows up as well. Nov 10 20:02:28 nick12310: https://en.wikipedia.org/wiki/Aliasing Nov 10 20:02:36 Yep Nov 11 00:15:59 Does anyone have the newest Debian Bullseye am355x image with GUI interface? I've tried Robert Nelson's Debian 11.x (Bullseye) Minimal Snapshot and IOT Snapshot but they haven't been readable on my SD card. Nov 11 00:16:21 what do you mean by "haven't been readable" ? Nov 11 00:17:47 note btw that neither minimal nor iot images have a gui, if for some reason you want a desktop gui on a beaglebone you'd need the xfce image Nov 11 00:17:55 The image would flash using etcher but I would get a message on my mac saying "Disk is not readable." I couldn't see any of the contents on the SD card Nov 11 00:18:08 that's expected, mac doesn't understand linux filesystems Nov 11 00:18:39 that's fine, if etcher completes successfully your sd card has been successfully flashed. that your mac doesn't understand how to read the card is not important Nov 11 00:21:26 I never got that message before when I used Buster. Also, when I flashed it to my BBB, the LED lights never stopped flashing Nov 11 00:21:27 btw don't expect a desktop environment to run well on a beaglebone.... the AM335x is an industrial SoC with very limited graphics capability meant mainly for simple touchscreen interfaces, it's not really designed to be used like a desktop pc Nov 11 00:22:26 strange that you didn't get the message before, I would actually *expect* such a message Nov 11 00:22:27 I'm trying to run a PyQT5 through the BBB onto my Mac. So don't I need a GUI? Nov 11 00:23:24 also these images are not flashers, the beaglebone will simply boot from them Nov 11 00:23:45 the flashing leds, presumably a heartbeat on the usr1 led, is just indicating the system is running Nov 11 00:24:22 what do you mean by "through the BBB onto my Mac" ? like, with X11 forwarding? you definitely don't need x11 for that on the beaglebone at all Nov 11 00:25:41 if you want to flash to eMMC you can invoke a command for that after logging in while booted from sd card Nov 11 00:28:10 So I insert the SD card with the image, log into my ssh then enter the command to flash to eMMC? Nov 11 00:28:24 yeah, the commands to flash are here: https://forum.beagleboard.org/t/debian-11-x-bullseye-monthly-snapshots/31280#emmc-flasher-7 Nov 11 00:28:52 Do I have to hold the S2 button down when powering on, or can I just insert USB? Nov 11 00:31:36 *usually* holding down S2 during power-on (you can let go once the power led turns on) isn't required to make a beaglebone boot from sd card, it only is if there's a really old/weird/broken bootloader on eMMC that fails to (properly) boot the linux system on sd card Nov 11 00:31:43 it doesn't hurt though Nov 11 00:32:34 ok, that's good to know Nov 11 00:32:44 note that S2 is only sampled at power-on and the setting remains in effect until next power-cycle Nov 11 00:33:29 Is it possible to run PyQt5 on beaglebone black and have it displayed on your Mac like a monitor? Nov 11 00:34:15 there are ways to do that yes, e.g. using x11 forwarding via ssh, or using something like vnc Nov 11 00:35:12 I'd try the x11 forwarding solution first (you can just google "mac x11 forwarding") since it's less hassle and has less resource requirements on the beaglebone Nov 11 00:36:01 if it turns out unreasonably slow then you may need to resort to vnc, but I don't really know the steps to set it up Nov 11 00:40:13 ah apparently qt5 has a vnc backend that makes a single qt5 application accessible via vnc: https://raymii.org/s/articles/Expose_any_QT_program_via_VNC.html Nov 11 00:40:14 ok, but neither vnc or x11 forwarding need a GUI interface in the image? Nov 11 00:40:48 x11 forwarding doesn't, vnc via the method I just linked doesn't either Nov 11 00:41:09 Ok, so this image should work then? am335x-debian-11.5-minimal-armhf-2022-11-01-2gb.img.xz 12 Nov 11 00:42:00 minimal or iot is your choice... keep in mind that the minimal image is pretty... minimal. use it only if you're comfortable with manually installing whatever debian packages you end up needing Nov 11 00:42:27 then again, you're going to need to install some packages either way, so minimal may be fine for you Nov 11 00:44:48 Ya I'll need the anaconda package with all the python libraries (NumPy, Matplotlib, PyQt5 etc) Nov 11 00:47:41 It's saying, Nov 11 00:47:43 Matts-MacBook-Air:~ mattlyon$ ssh debian@beaglebone.local Nov 11 00:47:43 ssh: connect to host beaglebone.local port 22: Connection refused Nov 11 00:49:10 does the mac see the usb network interface? Nov 11 00:49:21 like, in your network settings or whatever? Nov 11 00:49:43 Ya Nov 11 00:49:44 oh wait, connection refused Nov 11 00:49:53 might it still be booting? Nov 11 00:50:41 just try it again Nov 11 00:50:54 Ya it was still booting. Nov 11 00:51:10 I got the WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ message Nov 11 00:51:42 yeah that happens if you've previously logged into a different system with the same hostname Nov 11 00:52:45 just remove the old key from your known_hosts using ssh-keygen -R beaglebone.local Nov 11 00:59:26 Ya that worked. I think it's rebooting now. It won't let me enter into the local network Nov 11 01:00:14 note that to provide the beaglebone with internet access you'll probably want to connect it to an ethernet network if possible (or to wifi if you have a beaglebone variant with wifi) Nov 11 01:00:53 in principle it's possible via usb but this is a lot more fiddly and prone to cause loss of the ability to reach the beaglebone at all Nov 11 01:05:47 ok, I have an ethernet so I will use that instead Nov 11 01:06:20 once the system is rebooted. Can I leave the SD card in as extra storage? Do I have to erase the image off first Nov 11 01:08:14 you'll probably want to erase it since otherwise if you leave the sd card in the beaglebone it'll just boot from it instead of booting from eMMC Nov 11 01:08:55 and then setup a mountpoint for it or something Nov 11 01:09:29 but installing a minimal system probably leaves more than 3G of free space, what are you planning to do that needs that much space? Nov 11 01:09:40 the beaglebone isn't a great system for video editing or whatever ;) Nov 11 01:12:04 I probably don't need it, it's just in case the eMMC gets full Nov 11 01:13:50 It's for real-time data processing Nov 11 01:17:01 I read on Derek Molloy's Exploring Beaglebone that the blacks aren't good for real-time applications but I couldn't get a Pi due to the shortage so I'm hoping it will still work Nov 11 01:17:23 "aren't good for real-time applications" ?? Nov 11 01:17:45 compared to what? Nov 11 01:18:21 Raspberry Pi's Nov 11 01:20:14 people use the beaglebone for real-time audio processing (https://bela.io/) and have turned it into a 12-channel 100Msps logic analyzer (BeagleLogic) Nov 11 01:20:35 PRU gives it real-time capabilities the rpi can only dream of Nov 11 01:22:00 and if you're just using it as a linux system.... it's just a linux system, with the limitations on real-time processing that comes with any linux system. you can use an rt kernel or xenomai to improve its real-time capabilities just like you can on any linux system obviously, hardware doesn't have a great deal to do with it Nov 11 01:22:45 if you're doing stuff in python, it can't be *that* real-time anyway :P Nov 11 01:23:07 I know! Nov 11 01:23:39 Sorry. Carry on. Nov 11 01:24:06 Bela is a neat thing for digital I/O and for instrumentation! Nov 11 01:24:45 Guest9023: how "real-time" are we talking anyway? Nov 11 01:24:51 Ya, I don't care about crazy precision. 500ms - 1s is good enough Nov 11 01:25:52 that's... not really what people generally mean when they say "real-time" lol ;) the only thing you'd need to beware of is blocking for a long time on disk access Nov 11 01:28:33 What's considered real time? Microseconds? Nov 11 01:29:22 I mean, in the end "real-time" is more about assurance than about a specific latency, but generally it's not particularly challenging to do something within a 500ms-1s time constraint Nov 11 01:31:15 like, at the most extreme end, BeagleLogic uses PRU to sample its digital inputs every 10 nanoseconds, in software, with not a single cpu cycle (5ns) of jitter Nov 11 01:35:15 of course that's excessive for many applications. bela has an "action-to-sound" latency of 0.5ms Nov 11 01:36:35 they use xenomai: https://bela.io/about#the-software Nov 11 01:36:49 Ya that's insane. Isn't that coming close to moving at the speed of light? Nov 11 01:38:01 light travels 30cm per nanosecond Nov 11 01:38:22 30cm is a huge distance though, on chip-scale ;) Nov 11 01:42:55 What is the theoretical limit for real time with chips? Nov 11 01:43:14 that sounds like an ill-defined question Nov 11 01:43:44 the limit is defined by what you actually want to do and the budget you have to do it ;) Nov 11 01:44:26 like, if you want extremely low latency, use analog processing... if that happens to make sense for a particular application Nov 11 01:53:03 Well at a certain point the chips will be too small to build on a quantum level so the distance for light to travel will be finite. So whatever that distance is will have some minimum time with speed of light Nov 11 01:55:23 anyway, zZ **** ENDING LOGGING AT Fri Nov 11 02:59:57 2022