mpfs-rpmsg-bm(remote) "start_demo" affected timer interrupt print on uart

[EricZhangjie]

hello，I am running linux+BM demo on icicle kit，the BM program used mpfs-rpmsg-bm(remote) ,config linux uboot running on u54_1、u54_2、u54_3, and BM running on u54_4. I add a Timer interrupt and print a message per second on uart3, also some messages when timer is enabled. The red lines below are added lines.



The uart3 print result:

As BM code only running on hart4, so I modified makefile and do not compile hart0,hart1,hart2,hart3 codes ins application folder, then I find uart3 do not print "[Dsp] timer_cnt = ..."message per second in timer interrupt.


I find "start_demo->rpmsg_setup"function in u54_1 that affected the result. It does not print timer interrupt message if remove "start_demo" in u54_1. I modified "start_demo",and only "rpmsg_setup" left.


In addition, I find if do not compile hart0,hart2,hart3 codes ins application folder, that will not affect timer interrupt print on uart3.
It is strange. The BM program runs on hart4, why u54_1 function affected? does hart1's u54_1 function also run on any hart? how can it affected timer interrupt running?

[vfalanis]

Hi,

Have you tried debugging with GDB to find out which instruction is running on U54_4 when you see the issue?
You can attach to GDB from SoftConsole by doing a right click on the " mpfs-rpmsg-bm-hw one-hart attach remote.launch" -> Debug as -> mpfs-rpmsg-bm hw one-hart attach remote

Then on the debug window you can see the current program counter value (pc) and the function being run

Also, could you please let us know which SoftConsole version are you using?

Thanks

[EricZhangjie]

My SoftConsole version is v2021.1 and v2021.3-7.0.0.599, they all have the timer interrupt print issue.
I try to debug with SoftConsole v2021.3-7.0.0.599 as you suggested, but failed, log as below

[vfalanis]

Hi,

If using SoftConsole in Windows, could you please try to edit the launch configuration as suggested below and try again?

1. Right click in the "mpfs-rpmsg-bm hw one-hart attach remote.launch" configuration and select Debug- as -> Debug Configurations...
   

2. Select the "mpfs-rpmsg-bm hw one-hart attach remote" configuration in the right panel. Then go to the debugger tab and delete the following line from the "Commands" field:

file ${workspace_loc:/mpfs-rpmsg-bm/Remote-Default}/mpfs-rpmsg-remote.elf

3. After deleting the line on step 2, the configuration should look as shown below:
   

4. Click the "Apply" button followed by the "Debug" button

5. You should be able to see the program counter in the Debug window. For example:

Thanks

[nitindeshpande]

Could you add below line at line 32 in above snippet?
(void) mss_config_clk_rst(MSS_PERIPH_MMUART3, (uint8_t) 1, PERIPHERAL_ON);

This will bring the MMUART3 out of reset and enable clock to it.
It seems the U54_1 has that line and hence when you run code on U54_1, your UART3 also works.

[nitindeshpande]

Hi @EricZhangjie, were you able to get the issue resolved?