TMS320C6748: Technical Reference Manual

Hi Suzuki, 

That seems to just be a formatting irregularity. The PRU-ICSS Chapter appears to be all there. 

What do you mean by "anything special to set"? 

Section 12.8.1.3 immediately following lists the control/status registers for example. 

Best Regards,

Andrei

Hi Andrei.
Thank you for your reply.
I did not do enough checking.

I found the address and contents of the register, but when I checked the entity using CCS, it did not exist.
Local Memory shows XXXXXXXXXXX when read, and an error occurs when written.
Global Memory is set to 00000000 when read and does not change when written.
The existence of the PRUSS register cannot be confirmed in the register list.

Where is the substance of the PRUSS register?
I'm using CCS version 10.3.1.00003.
Thank you very much for your help.
Suzuki

I did not receive an email notification of receipt, so I am replying again.

Hi Andrei.
Thank you for your reply.
I did not do enough checking.

I found the address and contents of the register, but when I checked the entity using CCS, it did not exist.
Local Memory shows XXXXXXXXXXX when read, and an error occurs when written.
Global Memory is set to 00000000 when read and does not change when written.
The existence of the PRUSS register cannot be confirmed in the register list.

Where is the substance of the PRUSS register?
I'm using CCS version 10.3.1.00003.
Thank you very much for your help.
Suzuki

Hi Suzuki, 

What what memory offset are you trying to look at? And from the perspective of what core? 

I will loop in a colleague more familiar with the CCS side of things as well. 

Best,

Andrei

Hi Andrei.
I am looking at the data after address 0x00007000 (PRU0_CONTROL) and after address 0x01C37000 (PRU0_CONTROL) in the Memory Browser of CCS.
The core is a DSP.

In the "Table 3-4. C6746 Top Level Memory Map" in the datasheet, there is no allocation for 0x01C30000 to 0x01C3FFFF.
In "Table 6-126. Programmable Real-Time Unit Subsystem (PRUSS) Global Memory Map" in the datasheet, there is an allocation.
Is there any other way to check the contents of PRUSS in CCS other than using the Memory Browser?

Best regards.
Suzuki

Suzuki I see what you mean about seemingly the discrepancy between Table 3-4 and 6-126. I will have that looked at. 

In the meantime, you are looking at the right address range as far as I can tell (0x01C3 0000) , and using the memory browser is the correct way of doing this from CCS. Another way would be to write code to print out contents over UART for example.

Are you able to get some other known registers other than PRUSS and modify them? That way we can isolate this being a software setup issue. 

Best,

Andrei

Hello Andrei.
I have not checked all of them, but I can read and write other registers.
Best regards.
Suzuki

Ok, thank you for checking. I don't have a TMS320 on hand but I've been trying to replicate your issues on newer boards unsuccessfully. 

Have you also tried to connect to the PRUs in CCS and explore their memory from their perspective? The offset would be different of course but you should be able to access their registers that way. 

Best,

Andrei

Hi Andrei.
I did not know that I needed to connect to the PRU from CCS.
After I figured out how to connect, I did so and was able to select "PRU_Device_Memory" in the "Memory Blowser".

I don't know what the PRU does, so I'm going to disable it and not use it.
If I disable it, will it be OK if I don't need to set up the PRU initially?

Thank you for your time.
Suzuki

Hi Suzuki,

Sure thing, happy to help. 

The PRU is a small processor in its own right, so if you don't have code loaded to it, it won't do anything, you can keep them disabled if you are not using them.

Let me know if that helped solve your issue.

Best,

Andrei