On Monday, May 16, 2016 at 10:59:33 AM UTC-5, RobertCNelson wrote: > > > Oh my mistake, i thought getting the pwm sub-system working in > v4.1.x/v4.4.x with bonescript was something you were personally interested > in. > Only to the point that an LED and CdS photocell make a nice demo using the bone A/D and PWM to ramp up the LED as the photocell gets shaded. Without the PWM is just switching on a light :)
Better certainly is the enemy of good enough, but I won't argue against "better" until it starts breaking "good enough". Thus i was more interested in helping push that developer to scratch their > own itch. (developers with their own itch to scratch are 10 X better, then > a developer who's just fixing a bug report to fix it..) > > pwm developer, we must export, X, Y, Z with feature A, B, C, and D, E, & F > need to be adjustable in real time, and with the PRU ding G, H & I..... > > me: it's blinks an led, ship it! ;) > I'm with you here :) While having Bonscript launch a PRU process would be impressive, I'm not sure how someone needing the PRU timing would be looking at Bonescript in the first place. OTOH if Bonescript, Python, C-library, or whatever had functions to upload the appropriate PRU code and stream data to or from the PRU functionality created by the uploaded code, it'd surely make the PRU become a building block instead of a project. But is it even possible to do such a thing without ending up with something equally as complicated as uio_pruss or remoteproc? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/7bdf7b7a-bc28-463c-9f28-b8142dabb52e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
