Thank you for your reply!
I am indeed using the ETB (which by the way is 16KB on the I.MX6Q :smileyhappy: ), and I'm sure I configure all the CoreSight components correctly because I can get meaningful trace output. However, the trace output is limited to P0 (Linux user-space), whereas I also want trace from P1 (Linux kernel) in my buffer. The PTMs "ETMAUTHSTATUS" register informs me that Secure non-invasive debugging is not permitted, which is the reason the kernel trace is not generated and thus does not end up in the ETB. Documentation states that the "secure non-invasive debugging enable" bit is defined as (SPNIDEN OR SPIDEN) AND (NIDEN OR DBGEN). NIDEN and/or DBGEN are high, because non-secure non-invasive debugging is permitted (verified in the same ETMAUTHSTATUS register), so getting the SPNIDEN signal high should solve my problems.
I was hoping/assuming that SPNIDEN is controlled by a value in one of the fuses, but you claim it is not. Is there any way to control this signal from software?