@ P B: > I want to ensure the pump is not triggered from any noise. Perhaps I > misunderstood this feature. >
You should also consider to implement an external pulldown. The weak internal resistance isn't present in the early boot phase (it comes up 7-10 seconds after power-on). @ Dennis Am Donnerstag, 18. Juni 2020 22:50:03 UTC+2 schrieb Dennis Bieber: > > On Thu, 18 Jun 2020 12:11:23 -0700 (PDT), > > >Am Donnerstag, 18. Juni 2020 19:11:20 UTC+2 schrieb Dennis Bieber: > >> > >> -- Linux app sending command to PRU application to modify pin-mux so > Linux > >> app can make use of new state > >> > > > >How do you make the PRU modify pinmuxing? You have no idea what you're > >talking about! > > > > I can only state then, that a quick perusal of the online > documentation > (in particular, the github readme) gives this one the impression that the > package provides a specific program running on a PRU which must be used, > and that a host application, via a library, talks to that PRU to perform > I/O. If setting the configuration and subsequent I/O performed without > involving a PRU, it is not readily apparent. The presence of that warning > about the PRU being able to access any memory reinforces this, as it > implies that a PRU could write to the pin-mux registers to change > configuration. > The warning applies to all PRU deployment. The only difference: libpruio users get informed. IMHO you shouldn't try to create the impression that you're an expert with years of experience before you misread the short introduction of a project. Regards -- 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/0c96b3fe-a70f-4eb7-973c-f41fa85b48cbo%40googlegroups.com.
