Hello Pedro 
The thread I found turned into a big argument it looks like thats why I 
remembered it and made a reference to too many cooks giving advice. I will 
provide link but I am having trouble finding entire thread in the mail archive
[beagleboard] Re: Problems Reconfiguring GPIO's


| 
| 
| 
|  |  |

 |

 |
| 
|  | 
[beagleboard] Re: Problems Reconfiguring GPIO's


 |

 |

 |

As you see some members active in group were postulating and I don;t want to 
start trouble I wanted to help but I was afraid the couldd result in bad advise.
Start with Part 1 and convince yourself its possible by finding some PRU code 
for I2C that pretty much means its possible at least you will learn about PRUs 
start simple. Feel free to start another thread but check github and Marks PRU 
stuff Ill be watching for updates I would like to be more helpful. 
Did you find  the L3 Per block diagram ?
Best wishes my friend keep plugging!
Mark
    On Thursday, January 21, 2021, 08:54:22 AM CST, Pedro Henrique Fonseca 
Bertoleti <[email protected]> wrote:  
 
 Mark, thanks!
Em qui, 21 de jan de 2021 00:38, 'Mark Lazarewicz' via BeagleBoard 
<[email protected]> escreveu:

Hello Pedro
Is their a block diagram that shows the Interconnect peripherals in TRM? That 
used to be pretty standard in TRM and answers #1
I avoid Linux so I can't answer #2 but I'm pretty sure this question was asked 
before in this group.
Lastly refine your Google arguments I did find this but it may be for bare 
bones system.

https://e2e.ti.com/support/processors/f/791/t/458311?AM335x-PRU-access-to-I2C-and-other-peripherals-on-L4-PER-bus


I would start with the block diagram for L4 
Lastly Mark Yoder a professor who teaches embedded Linux has various tutorial 
and cookbooks. He's very gifted and his documents are clearly written and 
updated. Dig around their last after understanding what's possible would be my 
approach.
You know what they say about about too many cooks in the Kitchen Pedro? 
They spoil the soup 🤔🤗 
If you do some research and then narrow down the specifics you won't be misled
Hopefully I've offered something positive to help you.
Mark



Sent from Yahoo Mail on Android 
 
  On Wed, Jan 20, 2021 at 8:10 PM, Pedro Henrique Fonseca 
Bertoleti<[email protected]> wrote:   Hi everyone. My name is Pedro 
Bertoleti and I'm from Brazil.
I'm learning about the PRUs on BeagleBone (I'm using BeagleBone Black board) 
and I wanna read IMU and another I2C sensors in PRU firmware (to be able to 
implement some motion algorithms and stuffs like that in PRU firmware, due to 
its real-time scope).
However, I'm not sure on how to use I2C in PRU. Per my understanding:
A) PRUs have no hardware dedicated to I2C (nor SPI)B) I've seen some SPI 
examples with PRU on Internet, however in all of them SPI communication was 
made using bit-bang technique.
So, would you help me answering the following questions?
1) Do I need bit-banging to communicate PRU to I2C devices? I mean, isn't there 
another way to use I2C in PRU?2) If answer above is yes, is there an way to 
change gpio direction (input to outut and vice versa) inside PRU firmware? I 
ask this because, as I read so far, only config-pin (Linux side) can "enable" a 
gpio to PRU and set its direction, and glio direction change will be needed if 
I need to make I2C using bit-bang technique.
Please, would anyone shed some light on it?


Thanks in advance.

-- 
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/CAJK9pqfpzE1n7ZY%2BFN2px7uKyYtBVEaj3Acg2dAw7qOb0bUwhA%40mail.gmail.com.
  


-- 
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/1412944254.2544582.1611200267458%40mail.yahoo.com.



-- 
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/CAJK9pqdVZTq5R3W64Fkpgy1bq6mPbG999J1_Jk55%2B5UFud8ePw%40mail.gmail.com.
  

-- 
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/315867166.2789069.1611271641734%40mail.yahoo.com.

Reply via email to