Hello World on C6670 EVM - Verify_Init message to console

Hi Ran,

It is not happening all the time right? Are you running the gel file that we provided before you run the demo?

Thanks,

Arun.

Hi Arun,

No, it happens only sometimes. 

Yes, I keep the following load process: launch target configuration file, connect to target which executes the C6670 GEL file and initializes PLL, memory, etc., then load the program to Core 0 and run Core 0.

Thanks

Ran

HI Ran,

One more question. Is this happens the first time you run this code right after power on reset? I suspect that when you run the code multiple time and exit there is some issue in tearing these queues.

Thanks,

Arun.

Hi Arun,

Quite difficult to reproduce as it happens quite rarely. But yesterday I had this once in my app, and I always do a full reset between executions.

Thanks

Ran

Hi, Arun,

Could you  tell me  where  I can get  the EVMC6670L.gel?

Thanks,

Tao.

Hi Tao,

The EVMC6670L.gel can be obtained under :

C:\Program Files\Texas Instruments\ccsv5\ccs_base_5.0.3.00028\emulation\boards\evmc6670l\gel/evmc6670l.gel

But i wanted to reconfirm with Arun too  if its MANDATORY to load the GEL file for running any application on EVM c6670 ? Pls confirm the same.

No it is not needed. But make sure you initialize all peripherals using platform library APIs.

Thanks,

Arun.

Hi,

Arun

Accurately to say, when I run the Hello World NDK example on the C6670 EVM lite for the first time after power on reset, it will show correct messages, But when i run it again without a power on reset, it will show messages as below:

......

......

[C66xx_0] Network Added: failed...

I am very confused, can you explain this phenomenon? Do i need to do a power on reset before I run the NDK examples?

thank you.

Best regards.

Tao.

Hello. I get the same message (Verify_Init: Expected 0 entry count for Queue number = <xxx>, found <yyy> entries) ALWAYS when I'm executing my application. What does mean this warning and in which case does it appear?

The Verify_Init() in NIMU driver checks for all the Queue Entry Counts available in all the QMSS Queues availabe in the system.

If the NIMU driver is initialized after assigning some Descriptors to the QMSS queues in the system, then the Verify_Init() print above states that it expects the Other queues in the system should have "0" descriptors , but since you have already assigned some descriptors to the Queues, they are not empty.

This is just a warning situation and there is no problem in the general running of the application.

Santosh Pinto said:

but since you have already assigned some descriptors to the Queues

Does this mean queues used by NIMU, or any other queues?

No. It means the Queues which are not used by NIMU.

For the queues used by NIMU, there is a check in the NIMU driver where it ignores the Descriptor Counts in the queues used by NIMU.

This is a general check and the application will work fine even with these warnings.

If you dont want these warnings to come up, try to Initialize the NIMU driver at startup before defining any descriptors for the other queues.