PA_unitTest is not stable

Murat,

Please refer below thread for solution,

http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/197239.aspx

If the above thread did not solve the issue, please post below information.

Do you see this behavior with EVM? If yes, what is the failure rate? Do you see this behavior with multiple boards? 

Thank you for the post.

Thanks Rajasekaran for reply.

I test the sample on EVM. Above fifty percent I see the failure.

I have several boards at hand, they all behave the same.

The thread you refer to doesn't afford a solution to this, it just 

solve another question. Meanwhile, It proves that somebody

else also has this trouble.

The program also print the following error

(now this error occurs more often):

verifyTestFramework: Expected 0 entry count for queue 911, found 1 entries
verifyTestFramework: Expected 0 entry count for queue 913, found 1 entries

Then the sample exits.

Murat,

I have checked this test code and can be reproduce the issue. But this test code implemented like power cycle required if you reload and run this test code again and again.
We have discussed already similar issue on other test code like ndk based client example. Please see this will be help you better understand.
http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/384796/1362410.aspx#1362410

Did you get the error when you load and run each time freshly(like do the powr cycle the board)?
I tested this PA unit test code with out error when do power cycle the board each time.

hi, Pubesh:

Thanks for reply.

I used to power down the EVM and power it again. The situation seems

getting better. However, I noticed that it can't completely solve this.

The problem continues after power cycle.

I will read the thread you referred in the above post. Hope it help!

Murat,

Murat: said:

The problem continues after power cycle.

Please share the error log or snapshot for this scenario. So that I can try to reproduce.

The mentioned thread for client example, but you can find the reset solution from that discussion. 

hi, Pubesh:

I don't know how to get the error log. Would you tell me the procedure? Thanks!

I am not at office, when I go back, I'll get the log and snapshot for you.

Murat,

If you get the error, it will print the CCS console window. Other way when you debug the project through CCS, you can find the error exactly which function gives the error statement. 

hi, Pubesh:

I seem to remember the ccs can be set to log a lot of messages when debug begins, but

I forget where I can set this on in the ccs.

The error occurs when the program finishes setting the qmss and pktdma, it will verify Q907~Q1006.

They should be empty, but you have seen that some of these queues are not.

hi, Pubesh

I upload the snapshot.

The console output is the following:

[C66xx_0]

------- PA Unit Test Starting ---------
PDSP 0 version = 0x01020303
PDSP 1 version = 0x01020303
PDSP 2 version = 0x01020303
PDSP 3 version = 0x01020303
PDSP 4 version = 0x01020303
PDSP 5 version = 0x01020303
0count of Q900 = 128
1count of Q900 = 100
2count of Q900 = 68
3count of Q900 = 60
verifyTestFramework: Expected 0 entry count for queue 911, found 1 entries
verifyTestFramework: Expected 0 entry count for queue 913, found 1 entries
Packet reception while unconfigured: PASSED
verifyTestFramework: Expected 0 entry count for queue 911, found 1 entries
verifyTestFramework: Expected 0 entry count for queue 913, found 1 entries
topLevelTest (C:/ti/pdk_C6678_1_1_2_6/packages/ti/drv/pa/test/PAUnitTest/testMain.c:172): verifyTestFramework returned error after test Packet reception while unconfigured. Exiting.

Murat,

I have tested PA_unit_test as per the following steps,

1. Power ON the board, connect the target configuration file.
2. Select the core0 and connect the target.
3. Load the PA_unit_test out file and run on the EVMC6678.
4. Got the test result on CCS console window.
5. Terminate the target using CCS debug window.
6. Power OFF the board.
7. Repeat the steps 1-6 again.
8. In this test case, I did not find any error on ccs console window. I have done this testing 15 times. There is no issue.

But in your case, you are getting error message. Please share some more details to reproduce your issue.
Did you modify anything in this test code? If yes, please share the modification source.

hi, Pubesh:

I tried the original file and rebuild it, the error continues the same.

(I replace the directory c:\ti\pdk_C6678_1_1_2_6 with the ones

I backup when the MCSDK has just been installed, that is the original one)

The following is the snapshot.

The steps I take is the same as your saying. 

I tried 2 boards with the same result.