17:02 <brook> In the TI Technical Reference Manual for the AM33xx processor used in the BBB, a number of GPIO registers have the following sentence: "This register is not used within the module, its only function is to carry the pads configuration." Does that mean that it only reflects the configuration selected in the control registers?

20:10 <Sid93> Hello, can the beagleConnect Freedom be used as a radio front end for a beaglebone black?

20:11 <Sid93> I want to use these two devices to make an edge router

20:17 <zmatt> brook: what register(s) are you talking about exactly?

20:20 <mattb0ne> when are we going to get a new image

20:20 <mattb0ne> for the beagle black

20:23 <zmatt> brook: ah I see what you mean, it's a bit awkwardly phrased but what they mean is that these bits doesn't affect the functionality of the GPIO module itself but instead merely drive output-enable control signals from the gpio module (via pinmux) to the I/O cells at the SoC boundary

20:26 <zmatt> brook: the GPIO module has three signals for each of its 32 GPIOs: an input signal, an output signal, and an output-enable signal. now typically these will be hooked up exactly like their name suggests, hence for example the output signal will be ignored by the I/O cell if output-enable is not asserted, but ultimately it's not the GPIO module's business how the SoC hooks up these signals

20:33 <zmatt> brook: (I'm assuming you're talking about the GPIO_OE register, I didn't spot any other register with that remark)

20:49 <set_> mattb0ne: on forums. Dang it. On the forums are new images...

20:49 <zmatt> he probably means an officially released image

20:50 <set_> I think 3/1/2023 if I am not mistaken.

20:50 <set_> Oh.

20:50 <zmatt> on the forum are testing images

20:50 <set_> Right. Not official images. Got it.

20:50 <set_> They work...for the most part. I got GPIO/PWM/i2c and what looks like counters.

20:52 <set_> I guess these are the methods in which one would count for say an incrememnt or decrement in steps?

20:55 <set_> Or like for encoders?

20:57 <set_> ? == Yeppers!

20:57 <set_> anyway...back to my boring life!

21:33 <mattb0ne> hey

21:34 <mattb0ne> if you have beagle

21:34 <mattb0ne> with no lights

21:34 <mattb0ne> not the bleep of death

21:34 <mattb0ne> but nothing

21:34 <mattb0ne> how can i reset

21:34 <mattb0ne> trying to help someone

21:36 <mattb0ne> i get zero lights

21:37 <mattb0ne> no eletctronics were ever involved so it couldnt have been fried

22:56 <brook> zmatt: OK, but what is the difference between the GPIO registers like GPIO_OE and the bits of the control registers?

23:25 <zmatt> brook: uhh, there's no overlap in functionality?

23:28 <zmatt> the pad control registers control: 1. pinmux (i.e. which set of in/out/oe signals gets connected to the I/O cell), 2. the integrated weak pull-up/down on the pad 3. whether the input receiver is enabled

23:30 <zmatt> and the output driver's slew rate, in theory (it doesn't really seem to work in practice)