**** BEGIN LOGGING AT Tue Dec 07 02:59:56 2021 Dec 07 03:05:00 hmm good question as to how to do it. I know a lot of people are interested in using the M4. I believe it's primary function is to facilitate boot up correct? Dec 07 03:05:15 it's not related to boot whatsoever Dec 07 03:06:10 the primary use is as part of software stacks for managing other hardware subsystems such as IVA-HD, and I think TIDL uses it too Dec 07 03:07:17 No. Dec 07 03:07:28 It is for video and one is open! Dec 07 03:08:21 Since there are two! Two, I say! One, me, can access the unused one to handle M4 technologies like UART, GPIO, i2c, and so on... Dec 07 03:08:23 Right Dec 07 03:08:37 none of those are "M4 technologies" Dec 07 03:08:57 I understand what I said and how it is wishy-washy. Forgive me. Dec 07 03:09:07 I knew you were here! Dec 07 03:09:17 GenTooMan and @zmatt at the helm, heh? Dec 07 03:09:24 So? Dec 07 03:09:26 in general, the M4 cores may very well be the most hostile programming environment on the am572x Dec 07 03:09:53 I have been in some tedious understudying of the M4 for about a week now. Dec 07 03:09:56 I am up to speed. Dec 07 03:10:01 What makes it hostile? Dec 07 03:10:07 the M4 subsystem of the AM572x ? Dec 07 03:10:11 Oh. Dec 07 03:10:14 generic M4 information is of little or no help Dec 07 03:10:14 Right. Dec 07 03:10:26 Okay...well. Dec 07 03:10:39 I think we should get crackin' on this excursion! Dec 07 03:10:44 What say you? Dec 07 03:10:47 (the cores aren't the problem as such, the subsystem around them is awkward) Dec 07 03:10:55 Oh. Dec 07 03:11:16 I mean, we have a bus or two, right? Dec 07 03:11:36 One for specific pins and another for a separate sections of pin usage. Dec 07 03:11:55 ??? Dec 07 03:12:13 So, BUS or interconnect or whatever, it is how to transport data to and from for I/O. Dec 07 03:12:44 Stop and think. This could really be a nice project to show people. Dec 07 03:13:16 doubtful, the M4 cores are the least interesting ones Dec 07 03:13:39 Yes but it is a start on the AI. I see nothing these days of the AI. Dec 07 03:14:05 Except some strands from the people at Bela and KiwiSDR. Dec 07 03:14:32 Speakin' of... Dec 07 03:14:42 @zmatt, do you know anyone from KiwiSDR? Dec 07 03:15:38 no Dec 07 03:15:59 Oh. Well, that AI is still the fastest board produced from the .org I know about so far. Dec 07 03:16:55 Anyway...so. I am sure you already understand how to make the pins and offsets work w/ the M4 core. Dec 07 03:16:58 But... Dec 07 03:17:18 I still do not know to transfer data to and from the I/O just yet. Dec 07 03:17:28 the M4 has nothing to do with pins Dec 07 03:17:41 It can have something to do w/ pins. Dec 07 03:18:26 I can use M4 cores for specific instances of pin usage like specific peripherals. Like UART, i2c, SPI, and so on... Dec 07 03:18:55 Is that not allowed on the AI right now for any reason that is not described? Dec 07 03:19:10 it can access most if not all of the system, just like every other core can, although iirc it's harder from the M4 than e.g. from PRU Dec 07 03:19:47 Right. But...I am not studying the PRU. I never have time to learn everything PRU related. I keep failing out of PRU studying. Dec 07 03:20:02 in general if you want another core to access a peripheral like an uart or i2c controller you'd need to ensure it has _exclusive_ access (i.e. the linux driver is disabled) to avoid conflicts Dec 07 03:20:19 Right. I get why. Dec 07 03:20:30 I mean, what you are saying makes sense. Dec 07 03:21:14 When you say _exclusive_ access, what does that exactly mean, i.e. baremetal? Dec 07 03:21:47 Oh. Dec 07 03:21:59 it means what I put in parenthesis right after that Dec 07 03:22:11 can't have two cores try to use the same peripheral Dec 07 03:22:28 Okay, okay. I understand. So, somewhere in the kernel, there is a M4 kernel driver. Dec 07 03:22:30 Okay. Dec 07 03:22:41 I mean, there is, but that's not what I was talking about Dec 07 03:22:53 the driver for the peripheral Dec 07 03:23:01 Like, not writing a device...right. Dec 07 03:23:23 anyway, afk Dec 07 03:23:27 Did the .org make one or something...I am not sure exactly where this is coming from right now. Dec 07 03:23:28 No! Dec 07 03:24:31 Fine...I will try to suck up this info. I keep reading and then try to establish a connection and comm. to the M4 on the AI. Argh. Dec 07 03:57:38 perhaps the traditional goal of blinking an LED might be good? Dec 07 04:02:24 Right-o...I thought it was as simple as using some .h, .c, and .s files. Dec 07 04:02:58 Now, I need to find the base address and offsets. Dec 07 04:09:42 all things are possible just not practical. I think Zmatt was saying that. Dec 07 04:10:13 Oh. Right...I understand a bit and it may be a labor intensive job to get the first LED lit but what is not from scratch? Dec 07 04:10:45 I am completely new to the am5729, e.g. I have not been studying it for years. Dec 07 04:11:44 OK just like you were to the BBB right? Dec 07 04:12:36 Exactly. Lots of crying and yelling at @zmatt! Dec 07 04:12:39 Ha. Dec 07 04:16:13 I could not figure out anything at first and I was technically inferior, still am, to the BBB. Dec 07 04:18:00 Now! Look at this ole Joe here. I can alter things, make adjustments, and do things. Dec 07 04:19:17 congrats? Well see you aren't dead and you can learn stuff. That's better than most people apparently. Dec 07 04:21:36 Right-O. I feel spoiled rotten, thankfully. Dec 07 04:22:06 Like a fresh BBB in the wild! New, ready for deployment, and triggering input and output ideas. Dec 07 04:24:09 On the BBB, right now/right now, I am updating Jessie images. Ha. Hopefully this Cape works for me. Dec 07 04:33:42 wow jessie is ancient Dec 07 04:34:06 I know. It seems this Cape demands it for some reason. Dec 07 04:34:25 I think it's 12 years old. Dec 07 04:34:30 I think during this update I am currently performing, the image may get updated. Dec 07 04:34:31 Dang. Dec 07 04:34:38 IE 2008 debian Dec 07 04:34:43 Wozzers. Dec 07 04:35:04 Hmm. I am compiling now and upating the info. I will see! Dec 07 04:35:18 clang++ 6.0 Dec 07 04:35:20 well that said since the BBB is a different animule things aren't as simple to get a new image. Dec 07 04:35:39 Right? Dec 07 04:36:04 I mean...from the org, there are tons of images and current ideas dedicated to updating the images via the command line. Dec 07 04:36:33 But...w/ poky and oe or buildroot, it is not as easy as it once was... Dec 07 04:37:10 I cannot configure the buildroot process any longer nor can I get the yocto project to just accept my installations. Dec 07 04:37:41 Ideas and books faded and Yocto and Buildroot just kept keeping on. Dec 07 04:38:13 i.e. my yocto books are from '13. Dec 07 04:38:41 I think yocto now relies on python2 still. Dec 07 04:39:42 Updating everything to Python3 will take some time, i.e. as it has a lot of print statements and older ideas associated w/ it. Dec 07 04:41:08 I believe yocto is a basis for making images not an actual distribution Dec 07 04:41:20 Oh. Dec 07 04:41:37 it builds what you tell it too. That sounds simple at least. Dec 07 04:41:57 Yocto is a build tool is what I know. Right...does it listen? Dec 07 04:42:23 Every time I listen to their ideas, it stops midstream and tells me in output, stopping due to error 1. Dec 07 04:43:13 But yes sir, you can build many images or singular, specific builds for the BBB (once upon a time). Dec 07 04:43:26 I have been very unsuccessful lately. Dec 07 04:45:06 * set_ sounds spoiled w/ build tools b/c of some reason... Dec 07 04:46:35 4.4.9 kernel over here. Argh. Dec 07 04:52:24 You guys? Dec 07 04:52:44 Did someone here muscle the Buildroot people or Yocto individuals? Dec 07 05:05:34 Well anyway, it is working! Dec 07 05:05:55 the update is not done yet. I had to redo it too. Dec 07 06:34:53 Is there a way to enable HDMI in IoT version of Beaglebone? Dec 07 07:10:08 Like installing LXDE? Is that a good idea? Dec 07 08:08:34 Hello, World! Dec 07 08:10:08 Does anybody knows the differences between drawing of beaglebone AI and beaglebone black? Dec 07 08:28:41 zmatt: alright thanks for the answer :) Dec 07 22:41:25 Is there any beagle hardware comparable to the Pi4 in the works? Dec 07 23:08:02 sam90: is there any pi hardware comparable to beagles in the works? like having a SoC that's actually documented and available for purchase ;-) Dec 07 23:10:59 "comparable" is very vague and subjective since they're very different devices, with the beaglebones and bbx15 using industrial/automotive SoCs while the Pi is very much a consumer/media device Dec 07 23:14:03 for our applications, given a choice between the beaglebone black and the rpi4, I'd choose the beaglebone black. if you're going to use one as a small desktop computer however, you'd definitely want the rpi4 and not the bbb Dec 08 01:11:51 Yeah I dunno, lack of full documentation is a dealbreaker and I know BBBs have generally good support by now Dec 08 01:12:02 Don't need so much power really Dec 08 01:19:11 "full documentation" ? the rpi4 SoC doesn't even have a product page, or any evidence on broadcom's website that the SoC even exists: https://www.google.com/search?q=BCM2711+site%3Abroadcom.com&hl=en&tbs=li:1 Dec 08 01:22:43 but yeah, the 164-page document from the rpi foundation is obviously nothing compared to the thousands of pages of TI docs Dec 08 01:26:58 wait wtf, the rpi4 SoC has the same data ordering bug that the original rpi soc had? they still haven't solved that problem?!? duuude Dec 08 01:30:40 (performing a reads from a peripherals while a read from another peripheral is in progress can cause the data from those reads to get swapped) Dec 08 01:30:49 *a read from a peripheral **** ENDING LOGGING AT Wed Dec 08 02:59:56 2021