Shadyman has quit [Remote host closed the connection]
vd has quit [Quit: Client closed]
vd has joined #beagle
troth has joined #beagle
buzzmarshall has joined #beagle
Guest89 has quit [Quit: Client closed]
troth has quit [Ping timeout: 244 seconds]
troth has joined #beagle
set_ has quit [Ping timeout: 264 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
florian has quit [Quit: Ex-Chat]
set_ has joined #beagle
lucascastro has quit [Ping timeout: 256 seconds]
mattb0ne has quit [Ping timeout: 244 seconds]
lucascastro has joined #beagle
mattb0ne has joined #beagle
ikarso has joined #beagle
set_ has quit [Ping timeout: 250 seconds]
mattb0ne has quit [Ping timeout: 250 seconds]
mattb0ne has joined #beagle
<mattb0ne>
would the OS and PRU clash if I store a shared variable in PRU1 memeory
<mattb0ne>
zmatt: do you have that cheat sheet of the memory mapping names like dmam2 etc...
set_ has joined #beagle
<set_>
GenTooMan: I found a assembly co. that may be able to produce a couple of Capes! neat, heh?
<set_>
I do not have the machinery nor will I ever be able to get it. So, outsourcing may just prove valuable this time.
lucascastro has quit [Ping timeout: 240 seconds]
<GenTooMan>
well good fortune don't get too carried away with things, also it will cost monetary units :D
<set_>
Right...
<set_>
I know. Things are expensive these days.
<set_>
I just wanted one to call my own for now. Then, I can produce something else w/ different components, i.e. updated TI components!
<set_>
If they ever are going to be available.
<set_>
GenTooMan: Have you ever used a MSP w/ the ARM am335x for Cape making?
lucascastro has joined #beagle
vd has quit [Quit: Client closed]
vd has joined #beagle
<set_>
This is a complicated process, i.e. everyone wants something different and things are mismatched. Software is dedicated to specific formats, file ext, and processing the data needed is not straight forward.
otisolsen70 has quit [Quit: Leaving]
<GenTooMan>
msp430? or the MSP432 The 430 is an old 16 bit RISC toy and the 432 is a ARM M4 with the old 430's peripherals
<set_>
Either/or...Oh! The MSP432 then!
<set_>
The ARM M4 is the one I was discussing.
m-atoms has joined #beagle
<GenTooMan>
right you may want to get one of TI's lunch pads for the 432 if you want to experiment with it. However at that point it may make more sense to use a normal ARM from another provider such as uChip if you can get parts ... from anywhere. :D
<set_>
Okay.
<set_>
I have a launchpad for testing now. I am just not sure if the MSP432 is a good path to take for Cape making.
<set_>
I am sure TI sells them alone.
<set_>
Dang...they actually have some available still.
<set_>
Really, there is too many to pick from currently. I will have to figure out how to push a set of instructions to it first, i.e. outside of just random source.
mattb0ne has quit [Ping timeout: 244 seconds]
<set_>
Why are the PRUs up to 500Mhz when the other M4s are about 16MHz?
mattb0ne has joined #beagle
<set_>
So, I will need I/O, UART, and maybe PWM but I can add a controller and drivers later.
<set_>
I actually have currently a controller for drivers. A UC something or other...I think it is 2637. But, I am lacking drivers. Boo!
<set_>
Sorry. 200MHz.
<zmatt>
set_: pru has nothing to do with cortex-m, and what do you mean by "the other M4s are about 16MHz" ? the max clock frequency of cortex-m4 cores varies depending on implementation but I don't think I've ever seen one as slow as 16 MHz
<zmatt>
mattb0ne: "the OS" you mean linux? why would it care in any way whatsoever what you do with PRU's various memories?
<zmatt>
mattb0ne: and you already have shared variables so I'm not sure what you're asking
<zmatt>
you have the SharedVars struct for sharing variables between pru and python
<set_>
Right. They are variable.
<set_>
@zmatt: I was looking at their MHz frequencies and you are right. Most of them from TI show 16 to 24MHz.