In the past two months, I have been studying AM2634, found some minor problems, and some confusion. Here are some of my feelings and suggestions.
1. Missing and incorrect information in the TRM
1.1 Missing of figures and tables
a. Figure 7-110. Multiple ePWM Modules
b. Figure 7-113. ePWM Modules and Critical Internal Signal Interconnects
c. Figure 7-156. Digital-Compare Submodule High-Level Block Diagram
d. Table 7-103. Submodule Configuration Parameters
1.2 Discrepancy between the figures and the actual situation
a. Figure 7-43. PRU-ICSS Interrupt Controller Block Diagram
In figure 7.43 , system events 0 to 31 are generated from different peripherals, and it appears that all events come from peripherals. However, this is not the case.
(I asked about this in this post and also got a reply AM2634: There seems to be missing information in the ePWM section of the Technical Reference Manual. - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums)
b. Figure 7-112. Submodules and Signal Connections for an ePWM Module
This figure shows that TZ1-TZ3 and TRIPINs are all from INPUTXbar, but in fact TZ1-TZ4 are from INPUTXbar, and TRIPINs are connected to PWMXbar through INPUTXbar and then output to the DC submodule of PWM.
This error and the lack of Figure 7-156 will cause the configuration to fail when using the DC module and not work properly.
(There is also a point that Figure 7-111 and Figure 7-112 have the same title)
1.3 Body content
a. The first sentence in Chapter 4.5.3 ePWM Modules Overview “32 submodules are included in every ePWM peripheral.”
Only 8 submodules appear in 7.4.5.1 Introduction, why 32 are written here.
b. 2.5.2.2.3.1 PRU EGPIs Direct Input
The red dash marks whether the information is missing.
2. Some suggestions for software tools
2.1 There is a missing line of code in the demo “gpio_input_interrupt_am263x-lp_r5fss0-0_nortos_ti-arm-clang”.
I couldn't trigger interrupts properly when I ran this demo, but later found out that it was because the GPIO bank was not enabled.
I don't know if the latest SDK version adds enablement, if not, you can add it for the convenience of future learners.
2.2 It’s difficult for me to understand API Reference.
I looked for the API I wanted by asking for help from resource explorer-user guide. But I feel that the functionality of them is not clearly explained.
Or slowly look in the SDK program, but it is troublesome.
I sincerely hope you can optimize this or tell me what quick ways to do it.
2.3 The section on PRUs in the tool is not comprehensive enough.
There are too few PRU-related examples, and the PRU configuration in syscofig is very single, which makes it difficult for me to develop PRU-related projects.
3. The naming of demos, TRM, and register manual is inconsistent.
It is difficult to find uniform laws, which is confusing. I don't know if there's anything I've overlooked.
Thank you for your patience in reading this and looking forward to your reply.
