<GenTooMan>
set_, not really things are a bit of a mess at the moment for me :D
<set_>
oh. Okay. I am just getting back and you are not okay. What is wrong? Does the BBB got you down?
<set_>
You got the BBBlues?
<set_>
All jokes aside, okay. I understand.
<set_>
sometimes things just are completely $*%&.
<set_>
I got this M4 source runnin'. But...not on the AI yet. It is a start on another board w/ a M4.
<set_>
I am using just the MCU right now w/out having access to the ARM am5729 on the AI, i.e. if that is even needed.
<set_>
Linux has processes, i.e. so this would be nice. I could use baremetal w/ a Linux Distro!
<set_>
Learnin' awaits...
<set_>
I think the main issue is this...
<set_>
How would i install the binary of the executable on the M4 on the AI?
<set_>
You know what I am thinking? I am thinking that there is a specific set of commands to install this binary file to the M4 via the am5729.
starblue has quit [Ping timeout: 256 seconds]
starblue has joined #beagle
<GenTooMan>
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?
<zmatt>
it's not related to boot whatsoever
<zmatt>
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
<set_>
No.
<set_>
It is for video and one is open!
<set_>
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...
<set_>
Right
<zmatt>
none of those are "M4 technologies"
<set_>
I understand what I said and how it is wishy-washy. Forgive me.
<set_>
I knew you were here!
<set_>
GenTooMan and @zmatt at the helm, heh?
<set_>
So?
<zmatt>
in general, the M4 cores may very well be the most hostile programming environment on the am572x
<set_>
I have been in some tedious understudying of the M4 for about a week now.
<set_>
I am up to speed.
<set_>
What makes it hostile?
<zmatt>
the M4 subsystem of the AM572x ?
<set_>
Oh.
<zmatt>
generic M4 information is of little or no help
<set_>
Right.
<set_>
Okay...well.
<set_>
I think we should get crackin' on this excursion!
<set_>
What say you?
<zmatt>
(the cores aren't the problem as such, the subsystem around them is awkward)
<set_>
Oh.
<set_>
I mean, we have a bus or two, right?
<set_>
One for specific pins and another for a separate sections of pin usage.
<zmatt>
???
<set_>
So, BUS or interconnect or whatever, it is how to transport data to and from for I/O.
<set_>
Stop and think. This could really be a nice project to show people.
<zmatt>
doubtful, the M4 cores are the least interesting ones
<set_>
Yes but it is a start on the AI. I see nothing these days of the AI.
<set_>
Except some strands from the people at Bela and KiwiSDR.
<set_>
Speakin' of...
<set_>
@zmatt, do you know anyone from KiwiSDR?
<zmatt>
no
<set_>
Oh. Well, that AI is still the fastest board produced from the .org I know about so far.
<set_>
Anyway...so. I am sure you already understand how to make the pins and offsets work w/ the M4 core.
<set_>
But...
<set_>
I still do not know to transfer data to and from the I/O just yet.
<zmatt>
the M4 has nothing to do with pins
<set_>
It can have something to do w/ pins.
<set_>
I can use M4 cores for specific instances of pin usage like specific peripherals. Like UART, i2c, SPI, and so on...
<set_>
Is that not allowed on the AI right now for any reason that is not described?
<zmatt>
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
<set_>
Right. But...I am not studying the PRU. I never have time to learn everything PRU related. I keep failing out of PRU studying.
<zmatt>
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
<set_>
Right. I get why.
<set_>
I mean, what you are saying makes sense.
<set_>
When you say _exclusive_ access, what does that exactly mean, i.e. baremetal?
<set_>
Oh.
<zmatt>
it means what I put in parenthesis right after that
<zmatt>
can't have two cores try to use the same peripheral
<set_>
Okay, okay. I understand. So, somewhere in the kernel, there is a M4 kernel driver.
<set_>
Okay.
<zmatt>
I mean, there is, but that's not what I was talking about
<zmatt>
the driver for the peripheral
<set_>
Like, not writing a device...right.
<zmatt>
anyway, afk
<set_>
Did the .org make one or something...I am not sure exactly where this is coming from right now.
<set_>
No!
<set_>
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.
Konsgn has quit [Remote host closed the connection]
<GenTooMan>
perhaps the traditional goal of blinking an LED might be good?
<set_>
Right-o...I thought it was as simple as using some .h, .c, and .s files.
<set_>
Now, I need to find the base address and offsets.
<GenTooMan>
all things are possible just not practical. I think Zmatt was saying that.
<set_>
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?
<set_>
I am completely new to the am5729, e.g. I have not been studying it for years.
<GenTooMan>
OK just like you were to the BBB right?
<set_>
Exactly. Lots of crying and yelling at @zmatt!
<set_>
Ha.
<set_>
I could not figure out anything at first and I was technically inferior, still am, to the BBB.
<set_>
Now! Look at this ole Joe here. I can alter things, make adjustments, and do things.
<GenTooMan>
congrats? Well see you aren't dead and you can learn stuff. That's better than most people apparently.
vd has quit [Ping timeout: 256 seconds]
<set_>
Right-O. I feel spoiled rotten, thankfully.
<set_>
Like a fresh BBB in the wild! New, ready for deployment, and triggering input and output ideas.
<set_>
On the BBB, right now/right now, I am updating Jessie images. Ha. Hopefully this Cape works for me.
<GenTooMan>
wow jessie is ancient
<set_>
I know. It seems this Cape demands it for some reason.
<GenTooMan>
I think it's 12 years old.
<set_>
I think during this update I am currently performing, the image may get updated.
<set_>
Dang.
<GenTooMan>
IE 2008 debian
<set_>
Wozzers.
<set_>
Hmm. I am compiling now and upating the info. I will see!
<set_>
clang++ 6.0
<GenTooMan>
well that said since the BBB is a different animule things aren't as simple to get a new image.
<set_>
Right?
<set_>
I mean...from the org, there are tons of images and current ideas dedicated to updating the images via the command line.
<set_>
But...w/ poky and oe or buildroot, it is not as easy as it once was...
<set_>
I cannot configure the buildroot process any longer nor can I get the yocto project to just accept my installations.
<set_>
Ideas and books faded and Yocto and Buildroot just kept keeping on.
<set_>
i.e. my yocto books are from '13.
<set_>
I think yocto now relies on python2 still.
<set_>
Updating everything to Python3 will take some time, i.e. as it has a lot of print statements and older ideas associated w/ it.
<GenTooMan>
I believe yocto is a basis for making images not an actual distribution
<set_>
Oh.
<GenTooMan>
it builds what you tell it too. That sounds simple at least.
<set_>
Yocto is a build tool is what I know. Right...does it listen?
<set_>
Every time I listen to their ideas, it stops midstream and tells me in output, stopping due to error 1.
<set_>
But yes sir, you can build many images or singular, specific builds for the BBB (once upon a time).
<set_>
I have been very unsuccessful lately.
* set_
sounds spoiled w/ build tools b/c of some reason...
<set_>
4.4.9 kernel over here. Argh.
<set_>
You guys?
<set_>
Did someone here muscle the Buildroot people or Yocto individuals?
<set_>
Well anyway, it is working!
<set_>
the update is not done yet. I had to redo it too.
ikarso has joined #beagle
otisolsen70 has joined #beagle
otisolsen70 has quit [Remote host closed the connection]
otisolsen70 has joined #beagle
Raajeshwar has joined #beagle
<Raajeshwar>
Is there a way to enable HDMI in IoT version of Beaglebone?
Raajeshwar has quit [Ping timeout: 256 seconds]
Raajeshwar has joined #beagle
Raajeshwar has quit [Ping timeout: 256 seconds]
Raajeshwar has joined #beagle
<Raajeshwar>
Like installing LXDE? Is that a good idea?
Raajeshwar has quit [Ping timeout: 256 seconds]
Raajeshwar has joined #beagle
Guest70 has joined #beagle
<Guest70>
Hello, World!
<Guest70>
Does anybody knows the differences between drawing of beaglebone AI and beaglebone black?
ikarso has quit [Quit: Connection closed for inactivity]
ikarso has joined #beagle
Raajeshwar has quit [Ping timeout: 256 seconds]
<Daulity>
zmatt: alright thanks for the answer :)
Shadyman has quit [Quit: Leaving.]
Guest70 has quit [Ping timeout: 256 seconds]
Raajeshwar has joined #beagle
Guest70 has joined #beagle
florian has joined #beagle
rob_w has joined #beagle
Guest70 has quit [Quit: Client closed]
Raajeshwar has quit [Ping timeout: 256 seconds]
Raajeshwar has joined #beagle
lucascastro has joined #beagle
lucascastro has quit [Ping timeout: 252 seconds]
Raajeshwar has quit [Ping timeout: 256 seconds]
Raajeshwar has joined #beagle
CygniX has quit [Ping timeout: 245 seconds]
CygniX has joined #beagle
Raajeshwar has quit [Quit: Client closed]
rob_w has quit [Remote host closed the connection]
Konsgn has joined #beagle
xet7 has joined #beagle
PhotoJim has quit [Ping timeout: 240 seconds]
lucascastro has joined #beagle
rob_w has joined #beagle
lucascastro has quit [Ping timeout: 265 seconds]
lucascastro has joined #beagle
lucascastro has quit [Ping timeout: 265 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
rob_w has quit [Remote host closed the connection]
vd has joined #beagle
lucascastro has joined #beagle
Guest18 has joined #beagle
florian has quit [Quit: Ex-Chat]
xet7 has quit [Quit: Leaving]
lucas_ has joined #beagle
lucascastro has quit [Ping timeout: 265 seconds]
xet7 has joined #beagle
set_ has quit [Ping timeout: 252 seconds]
Guest18 has quit [Quit: Client closed]
Shadyman has joined #beagle
lucas_ has quit [Ping timeout: 256 seconds]
troth has quit [Ping timeout: 252 seconds]
troth has joined #beagle
lucascastro has joined #beagle
ikarso has joined #beagle
otisolsen70 has quit [Quit: Leaving]
sam90 has joined #beagle
<sam90>
Is there any beagle hardware comparable to the Pi4 in the works?
PhotoJim has joined #beagle
buzzmarshall has joined #beagle
sam90 has quit [Ping timeout: 256 seconds]
<zmatt>
sam90: is there any pi hardware comparable to beagles in the works? like having a SoC that's actually documented and available for purchase ;-)
<zmatt>
"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
<zmatt>
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
lucascastro has quit [Remote host closed the connection]