So I've been debugging various things on my RK3566 based soquartz and standard debugging is becoming insufficient for my needs. Hardware tracing would be really nice to have and there is Coresight ETM support in Linux.
However before I spend lots of time trying to get it working can someone clarify for me if RK3566 actually has a functioning Coresight ETM component? If yes, is it version ETMv4 and what subcomponents it has(trace funnel? anything else)?
The RK3568 (that is supposedly very similar to rk3566) TRM document claims rk3568 has DAP-Lite2 debug component which is described on ARM;s website as "a simple debug component with no tracing capability."
So if there is no tracing capability why does the ROM table contain tracing components for each CPU? (listing below)
Code:
AP # 0x0
AP ID register 0x24770002
Type is MEM-AP APB2 or APB3
MEM-AP BASE 0x80000003
Valid ROM table present
Component base address 0x80000000
Peripheral ID 0x0000080000
Designer is 0x000, <invalid>
Part is 0x000, Unrecognized
Component class is 0x1, ROM table
MEMTYPE system memory not present: dedicated debug bus
ROMTABLE[0x0] = 0x01000003
Component base address 0x81000000
Peripheral ID 0x04007bb4e3
Designer is 0x23b, ARM Ltd
Part is 0x4e3, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x00, Miscellaneous, other
Dev Arch is 0x47700af7, ARM Ltd "CoreSight ROM architecture" rev.0
Type is ROM table
MEMTYPE system memory not present: dedicated debug bus
[L01] ROMTABLE[0x0] = 0x00001006
Component not present
[L01] ROMTABLE[0x4] = 0x00002006
Component not present
[L01] ROMTABLE[0x8] = 0x00004003
Component base address 0x81004000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x15, Debug Logic, Processor
Dev Arch is 0x47708a15, ARM Ltd "Processor debug architecture (v8.2-A)" rev.0
[L01] ROMTABLE[0xc] = 0x00005003
Component base address 0x81005000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x15, Debug Logic, Processor
Dev Arch is 0x47708a15, ARM Ltd "Processor debug architecture (v8.2-A)" rev.0
[L01] ROMTABLE[0x10] = 0x00006003
Component base address 0x81006000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x15, Debug Logic, Processor
Dev Arch is 0x47708a15, ARM Ltd "Processor debug architecture (v8.2-A)" rev.0
[L01] ROMTABLE[0x14] = 0x00007003
Component base address 0x81007000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x15, Debug Logic, Processor
Dev Arch is 0x47708a15, ARM Ltd "Processor debug architecture (v8.2-A)" rev.0
[L01] ROMTABLE[0x18] = 0x00008002
Component not present
[L01] ROMTABLE[0x1c] = 0x00009002
Component not present
[L01] ROMTABLE[0x20] = 0x0000a002
Component not present
[L01] ROMTABLE[0x24] = 0x0000b002
Component not present
[L01] ROMTABLE[0x28] = 0x0000c003
Component base address 0x8100c000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x16, Performance Monitor, Processor
Dev Arch is 0x47702a16, ARM Ltd "Processor Performance Monitor (PMU) architecture" rev.0
[L01] ROMTABLE[0x2c] = 0x0000d003
Component base address 0x8100d000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x16, Performance Monitor, Processor
Dev Arch is 0x47702a16, ARM Ltd "Processor Performance Monitor (PMU) architecture" rev.0
[L01] ROMTABLE[0x30] = 0x0000e003
Component base address 0x8100e000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x16, Performance Monitor, Processor
Dev Arch is 0x47702a16, ARM Ltd "Processor Performance Monitor (PMU) architecture" rev.0
[L01] ROMTABLE[0x34] = 0x0000f003
Component base address 0x8100f000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x16, Performance Monitor, Processor
Dev Arch is 0x47702a16, ARM Ltd "Processor Performance Monitor (PMU) architecture" rev.0
[L01] ROMTABLE[0x38] = 0x00014003
Component base address 0x81014000
Peripheral ID 0x04007bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x14, Debug Control, Trigger Matrix
Dev Arch is 0x47701a14, ARM Ltd "Cross Trigger Interface (CTI) architecture" rev.0
[L01] ROMTABLE[0x3c] = 0x00015003
Component base address 0x81015000
Peripheral ID 0x04007bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x14, Debug Control, Trigger Matrix
Dev Arch is 0x47701a14, ARM Ltd "Cross Trigger Interface (CTI) architecture" rev.0
[L01] ROMTABLE[0x40] = 0x00016003
Component base address 0x81016000
Peripheral ID 0x04007bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x14, Debug Control, Trigger Matrix
Dev Arch is 0x47701a14, ARM Ltd "Cross Trigger Interface (CTI) architecture" rev.0
[L01] ROMTABLE[0x44] = 0x00017003
Component base address 0x81017000
Peripheral ID 0x04007bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x14, Debug Control, Trigger Matrix
Dev Arch is 0x47701a14, ARM Ltd "Cross Trigger Interface (CTI) architecture" rev.0
[L01] ROMTABLE[0x48] = 0x0001c003
Component base address 0x8101c000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x13, Trace Source, Processor
Dev Arch is 0x47724a13, ARM Ltd "Embedded Trace Macrocell (ETM) architecture" rev.2
[L01] ROMTABLE[0x4c] = 0x0001d003
Component base address 0x8101d000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x13, Trace Source, Processor
Dev Arch is 0x47724a13, ARM Ltd "Embedded Trace Macrocell (ETM) architecture" rev.2
[L01] ROMTABLE[0x50] = 0x0001e003
Component base address 0x8101e000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x13, Trace Source, Processor
Dev Arch is 0x47724a13, ARM Ltd "Embedded Trace Macrocell (ETM) architecture" rev.2
[L01] ROMTABLE[0x54] = 0x0001f003
Component base address 0x8101f000
Peripheral ID 0x04003bbd05
Designer is 0x23b, ARM Ltd
Part is 0xd05, Unrecognized
Component class is 0x9, CoreSight component
Type is 0x13, Trace Source, Processor
Dev Arch is 0x47724a13, ARM Ltd "Embedded Trace Macrocell (ETM) architecture" rev.2
[L01] ROMTABLE[0x58] = 0x00000002
Component not present
[L01] ROMTABLE[0x5c] = 0x00000002
Component not present
It is clear we have a CTI, a PMU and an ETM for each core. Can anyone confirm/deny if those can be made to work?
BTW. If anyone is interested how to do hardware level debug on Quartz64 I wrote a quick description here: http://notes.zahoryzontnik.com/
A couple days ago I received my Pinebook Pro. Immediately after first boot I started to hear an occasional startling sound coming from the lower half of the machine. It is the kind of sound that reminds me of a speaker getting its cable pulled out (although much "smaller" sounding of course). On the other hand, it plausibly sounds like a fan having a malfunction -- I have not heard a fan on this during use so far, presumably it has one?
If I had to guess, it is coming from the lower left side, e,g, under the caps lock and the meta key. It happens randomly, but at least 5 times in a couple hours of use.
Got the new PBP this week. The first couple of hours went well getting setup. Have had the following issues:
random humming for a few seconds followed by a popping sound coming from speakers.
Then did not plug in before battery drained and next time I tried to boot after charging for a few hours, got the green power-on light but nothing on the display. I know the battery is charged so I suspect something on the software side has gone amiss. I ordered the emmc-usb adapter in order to flash new os. Will try that once I get it
Today while booting off the Fedora32 image on an SD card, I got the popping sounds again and the keyboard dies.
Is this a defective laptop or are there things I can try to fix these issues? (Willing to try if there are options)
I have been struggling to make Bluetooth audio work with it. It stuttered a lot, but yesterday I found a solution. Please test it and report back, I need feedback from a few people so I can submit a kernel patch with enough confidence.
Quick explanation: A patch that fixes the stutters on ROCK Pi 4 boards, also based on the rk3399 board with the same BCM4345C5 Bluetooth device, also on UART0, has been submitted last November: https://patchwork.kernel.org/project/lin...tions.com/
This fix sets the correct right max-speed and compatibility configurations for the Bluetooth device to work correctly. It is already present for the Pinebook Pro. The same fix needs to be applied for the RockPro64.
I'm using Armbian, so the following instructions might need to be adapted for other distributions, though the fix not to be specific to Armbian and the instructions might be generic enough.
I attached 3 files to this post. Please remove the .txt extensions when downloading them. Here's how to use them.
Testing quicky
First, I only tested this on linux 5.18. This is not the default kernel version on Armbian for the RockPro64. The default kernel is 5.15. To install version 5.18, you can use the armbian-config tool which will install the linux-image-edge-rockchip64 kernel. 5.15 might work but I haven't tested it.
So:
Backup your stuff. We are messing with boot files.
If you haven't already, install linux 5.18 (the linux-image-edge-rockchip64 kernel, which can be installed using armbian-config)
Download the rk3399-rockpro64-v2.dtb and rk3399-rockpro64.dtb files attached to this post. Remove the .txt extensions.
And then reboot. Be aware that any kernel upgrade will probably erase these files and you'll need to copy them back after upgrade.
These files actually come from a kernel build, so if you want, you can recompile the kernel with the fix.
Recompiling the kernel
The previous instructions are sufficient to use the fix. However, if you may want to recompile your kernel with this fix.
Apply the attached patch. I'm testing this on kernel 5.18. The patch should cleanly apply on versions 5.18 and 5.19. I've not tested this on 5.15. On Armbian, you can download the kernel sources using apt install linux-source-5.18.0-edge-rockchip64. You'll find the kernel sources and the config used in Armbian for the RockPro64 in the /usr/src folder. The following is sufficient to build the dtb files:
Code:
make dtbs
If you want to build deb packages, use make deb-pkg.
Hey folks. Been enjoying messing around with my new PBP this past week. Manjaro out the box has been an enjoyable experience... However, I took a dive into trying Kali out on this & have ran into an issue. Cant seem to get internal wifi working on Kali SD boot or on emmc boot. Have attempted to list available interfaces but Kali seems to think I have nothing available. Am I potentially missing something? On a side note: this is my first time trying these systems on arm & have enjoyed things so far, issues aside.
Any suggestions on what I may be overlooking? Could it potentially be firmware/ drivers do not exist on my install? The image I am using is the current one offered on Kali official site for PBP.
tl;dr: I bought rp64 in like 2021 and did few tests on it mainly running Armbian and NixOS to see if everything works during which it was powered on for around 6 hours max with everything working fine as far as i can remember [https://github.com/Mic92/nixos-aarch64-images/issues/3].
Then i put it in a box without power for around a year and now i am trying to use it for further development, but i can't get USB and Ethernet to work on armbian, debian, DietPi and Manjaro images which leads me to suspect hardware damage -> Is there a way to diagnose what/if is wrong with it so that i can fix it? (I have experience with fixing and fabricating hardware i can do microsolder, reballing and make simple PCBs)
The flash-it script is now working again for both sdcards and emmc. After an update to eg25manager several problems have been resolved, chiefly an incoming call now actually wakes the phone up. The display behaves correctly, wakes up immediately even after deep sleeps. Call audio is not great and the camera doesn't work at all - apart from that everything works, updated to 4.4.0.58.
I have a new Pinebook Pro (August 2022 run). It works fine in all other respects, but I have had zero luck with it recognizing 5GHz wireless networks with the included Manjaro distribution, a new Fedora installation, and a new Manjaro installation. The 2.4GHz wireless service works fine, if a bit slowly. The only way that I have managed to get 5GHz wireless to work is with an external RTL8812AU USB device (which worked immediately without any necessary configuration).
Is this a known issue? If so, is it a hardware problem or a software one? Am I missing a firmware update?
