On Tuesday, December 9, 2014 8:13:45 PM UTC-5, Matthew Heitzenroder wrote: > > > I would hate to downgrade the kernel back to 3.8, just to get the capes to > work. I’ll give those overlays a try. >
@Matt - Well, if you REALLY don't want to go back, another thing you can try is to memory map the chip address space and directly control the pin registers. Search for the android devmem.c utility. It's a small C program that memory maps physical address space into user space. Compile and run it on the BBB. See the TI AM335x TRM (http://www.ti.com/lit/ug/spruh73k/spruh73k.pdf) for physical memory locations for EVERYTHING on the chip. You need to understand the architecture a little because the ARM core accesses most SoC peripherals using the L3 or L4 buses (L1 and L2 are inside the ARM core.) For example, to read the GPIO_DATAOUT register in the GPIO1 register set and then set the USR1 LED (bit 22): sudo devmem2 0x4804c13c w sudo devmem2 0x4804c13c w 0x400000 To confirm the device, read the device_id reg in the CONTROL_MODULE register set. This should always return something containing B944h and 17h - the unique JTAG id for the TI AM3358 chip. sudo devmem2 0x44e10600 w According to the BBB SRM you want to look in section 9.2.2 of the TRM for your pins. -- 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]. For more options, visit https://groups.google.com/d/optout.
