Along with what the others have described, since you're the arm processor gpio rather than a pru gpio, meaning you're going all the way out to system memory, you have to connect the pru to system memory. Here's an example of accessing system memory with the pru:
http://nomel.tumblr.com/post/30006622413/beaglebone-tutorial-accessing-main-memory-from-the-pru To set the pin mux for arm gpio, you can use one of these gpio overlays. Just follow the instructions: https://github.com/nomel/beaglebone/tree/master/gpio-header Also, there are a few pru debuggers out there now so you can view/step pru execution. -Brandon On Sunday, March 9, 2014 6:37:09 PM UTC-7, Manu wrote: > > I was trying a few days to enable PRU (BBB Ubuntu 12.04) and run a input > testing code using the pin P9_24. > > MUX = pin 97 (44e10984) 00000006 pinctrl-single (SET to MODE 6) > > P9 24 pr1_pru0_pru_r31_16.GPIO0_15: | MODE6 | INPUT > > Nothing happens when I put the pin to 1.8 or GND > > The ASM code is: > > .origin 0 > .entrypoint START > > #define PRU0_ARM_INTERRUPT 19 > #define AM33XX > > #define GPIO1 0x4804c000 > #define GPIO_CLEARDATAOUT 0x190 > #define GPIO_SETDATAOUT 0x194 > > START: > // clear that bit > LBCO r0, C4, 4, 4 > CLR r0, r0, 4 > SBCO r0, C4, 4, 4 > > MOV r0, 1000000000 //# cycles > > INPUTTEST: > > WBS r31.t15 //Wait til GPIO-15-in is high... P9_24 > SUB r0, r0, 1 //Subtract from counter > QBNE INPUTTEST, r0, 0 //Loop if counter not at zero > // Send notification to Host for program completion > MOV R31.b0, PRU0_ARM_INTERRUPT+16 > > MOV r0, 0 > HALT > > I don't know what I am doing wrong and in Internet are not examples for > INPUT tests. > > > > > -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
