TI E2E support forums
Menu
Search through millions of questions and answers
User
Menu
Search through millions of questions and answers
User
E2E™ support forums
Forums
Amplifiers
Audio
Clock & timing
Data converters
DLP® products
Interface
Isolation
Logic
Microcontrollers
Motor drivers
Power management
Processors
RF & microwave
Sensors
Site support
Switches & multiplexers
Tools
Wireless connectivity
Archived forums
Archived groups
Technical articles
Analog
Automotive
DLP® technology
Embedded processing
Industrial
Power management
0
TI training
Tech days
Online training
Live events
Power Supply Design Seminar
Getting started
More
Cancel
简体中文
Search tips
Showing 52 results
View by: Thread
Post
Sort by
Relevance
Oldest to Newest
Newest to Oldest
Lucas Rolfes
over 2 years ago
Processors
Processors forum
RE: Compiler/PRU-SWPKG: Application-PRU Support for GNU G++
Hello Nick, Sorry for the confusion. I was confused with the difference between the PRU and the IPU subsystem, without recognizing that the PRU is a Risc-32-bit versus and Arm M4. Closing the issue as it is arguably a non-issue.
user5835157
over 2 years ago
Processors
Processors forum
RE: Linux/PRU-SWPKG: PRU PWM/RPMsg control GPIO
Hi Nick, Thank you for your reply, For testing, I am trying to have PWM signals working on LEDs. I am more interested in generating my PWM signal manually from the PRU. Do you have some application note about this use case ? Thanks
George Mock
over 2 years ago
Code Composer Studio™
Code Composer Studio™ forum
RE: Compiler/PRU-SWPKG: clpru behaves differently in docker image vs ubuntu desktop; fails with "exec() error spawning acpiapru: No such file or directory"
We do not test clpru (or any other TI compiler) under Docker. Whether running under Linux or Docker, the shell clpru invokes the sub-process acpiapru with the system call execvp. It has worked this way for a long time. Therefore, it is likely the problem...
Kazuya Nakamura
over 3 years ago
Processors
Processors forum
RE: Linux/PRU-SWPKG: PRU program load
Will read further about the Processor SDK and the Remoteproc framework, but as far as i know, the Processor SDK does not support non-Ubuntu Linux distros, correct? Thanks for the quick answer.
Puneeth Bandikatla
over 3 years ago
Processors
Processors forum
RE: PRU-SWPKG: PRU access to host memory
Hi Jason, Thanks for the reply, It cleared all the doubts I had on Address Mapping of PRU.
Jason Reeder
over 3 years ago
Processors
Processors forum
RE: PRU-SWPKG: Sharing variables across PRUs
Puneeth, Please see the memory map for the PRU subsystems in the AM437x TRM ( http://www.ti.com/lit/pdf/spruhl7 ) in Table 30-5 in section 30.3.1.2. You'll see that PRU-ICSS0's PRU0 accesses its own local memory (PRU0 DRAM) at address 0x0000...
Jason Reeder
over 3 years ago
Processors
Processors forum
RE: PRU-SWPKG: Sharing data between ARM and PRU
Puneeth, Please try adding pinctrl-names = "default"; to your pru0_1 node (shown below). I just copied and pasted your pru0_1 node into my DT and without that line my devmem2 was showing mux mode 7 (like yours). When I added that line, devmem2...
Ahmad_Rashed
over 3 years ago
Processors
Processors forum
RE: PRU-SWPKG: PRU-ICSS UART pins
Once you find the pins, they will need to be muxed to the proper mux-mode in order to bring out the signals from the PRU core to the SoC pins. There is a user guide for the PRU Cape for BeagleBone Black. It has a table that details which BBB header pins...
Jason Reeder
over 3 years ago
Processors
Processors forum
RE: CCS/PRU-SWPKG: Loading PRU code from Linux
Puneeth, The latest versions of the TI Provided C compiler for the PRU can be found here: http://software-dl.ti.com/codegen/non-esd/downloads/download.htm#PRU . There is no need to download CCS to get it or use the old beta link that you've posted...
Jason Reeder
over 3 years ago
Processors
Processors forum
RE: Linux/PRU-SWPKG: PRU PWM issue
Puneeth, The eQEP pins belong to the eQEP module that is outside of the PRU Subsystem. The PRU code that is controlling the eQEP peripheral in the example (in prupid_fw_1/PRU_IO_1.c) is actually just reading from and writing to the eQEP registers using...
>
Didn't find what you are looking for? Post a new question.
Ask a new question