Hello,
I am using Dstream with a Pactron sherwood board with Marvell armada xp, since there isnt an existing platform in DS-5 I tried PCE and got warnings about several components not having a connection e.g. CSTFunnel. I read in another discussion that could be caused if I ran the PCE in uboot, since it only powers on one core. So I got linux to run and did the configuration again but with same results.
My goal is to debug u-boot and kernel, so I can figure out how to switch the kernel to big endian properly(as I understand u-boot doesnt need to be BE). Due to some limitations in the u-boot, I have to make the switch in kernel.
So, do these warnings only limit the trace and linux application debug? Or also the bare metal? I have tried just proceeding with the warning and I can make a connection but I run into trouble when I try to set a break point and step through u-boot.
I am very new to this environment please do let me know if I can provide further information?
Hi,
I would start by using PCE to create a configuration containing a single core + its CTI. You need to choose the core that will run uboot - probably core_0 but you may have to experiment a bit. Then connect DS-5 to just that core and see if you get more success and a stable debug environment. If uboot only uses this one core and you dont need trace capability you will have all you need for uboot debug.
Thank you for the suggestions. I havent watched those videos as it seems like, yes, core_0 is the active core. I can connect to it but its unable to find the entry point, also it doesnt seems to stop at any breakpoints.
I am trying to debug the problem where u-boot is in little endian and kernel is compiled in a big endian. U-boot hangs with "Starting kernel ..." message.