CC2652R7: Issue in using Log_printf function for values of variable inside a structure

Hi Garvit,

Thank you for reaching out.

With "%s", Log_printf can only prints constant strings. I would then suggest to print the Bluetooth address byte-byte (instead of all at once).

Notes:

- it looks like the value printed for RSSI is correct. 4294967258 = 0xFFFF FFDA corresponding to -38

- the value printed for the address may be the address of the variable in RAM (536890212 = 0x20004B64)

I hope this will help,

Best regards,

Hello Clement,

Thanks for pointing out the right way to interpret the results.

Is there a way we can modify the number of arguments allowed to be logged in single log_printf statement ? 

The issue is in logging the address byte by byte - If I want to log the address in a single log_printf statement I need 6 arguments to be logged but there are only 4 arguments space in ROV. 

The code I used for logging is - 

 Log_printf(LogModule_App1, Log_INFO, "RSSI = %d Address = %d %d %d %d %d %d",pAdvRpt->rssi,pAdvRpt->addr[0],pAdvRpt->addr[1],pAdvRpt->addr[2],pAdvRpt->addr[3],pAdvRpt->addr[4],pAdvRpt->addr[5]);

Also, please let me know if this is the best way to log this information or should I be using some other approach like using the BLE_LOG_INT functions ?

Output - 

Thanks,

Garvit

Hi Garvit,

In this case, I would recommend using the Log_buf function. The code below should do the trick:

 Log_buf(LogModule_App1, Log_INFO, "Address: ", pAdvRpt->addr, 6);

Let me know your results.

Regards,

Hello Clement,

There seems to be some error in -  Log_buf(LogModule_App1, Log_INFO, pAdvRpt->addr, 6);

Error - Too too few arguments provided to function-like macro invocation

syntax -  Log_buf(LogModule_App1, Log_INFO, "The contents of bufferToLog are: ",pAdvRpt->rssi, 6);

This syntax was not able to load data to arguments

produced following results - 

I tried using - Log_buf(LogModule_App1, Log_INFO, "The contents of bufferToLog are: ",pAdvRpt->rssi[1], 6);

to see if this changes the argument to non zero value but this also produced error.

Thanks,

Garvit

Hi Garvit,

Sorry I forgot one argument - I have updated my previous message with a fix.

Garvit Periwal said:

I tried using - Log_buf(LogModule_App1, Log_INFO, "The contents of bufferToLog are: ",pAdvRpt->rssi[1], 6);

If I may, it looks like you pass a value (not a pointer) as 4th argument. I would rather suggest: Log_buf(LogModule_App1, Log_INFO, "The contents of bufferToLog are: ",&(pAdvRpt->rssi[1]), 6);

Can you try this for me?

Regards,

Hello Clement,

Thanks a lot, It worked. I still have some doubt though, If I make use of %x in Log_printf, the message is printed in hex format although the arguments are stored in unsigned integer format as shown in image below -

1) Is there a way to print -94 in front of RSSI in message box ?

2) Also, Is there a way we can display the address in hex format under the message tab in Log_buf ?

I do understand that since we are passing an address here so directly writing %x won't work.

The output for the syntax - Log_buf(LogModule_App1, Log_INFO, "The address of device is : ",&(pAdvRpt->addr), 6);

The output format I am looking for in message is - "The address of device is: 0x5B4C01450AE3"

Thanks,

Garvit

Hi Garvit,

Great to see your progress.

I have run your results by my colleagues in the R&D team. I am afraid the current version of the Log driver will not get you much better display. We will work to improve this and make it more user friendly in future releases.

In the mean time, you can consider slightly modifying the Log driver so you can modify the way the in Log_printf function displays the messages. I could not run proper testing so far (I do not have the right boards with me), but modifying the function rsprintf the file <SDK>\source\ti\log\LogSinkBuf.rov.js you can modify the way the parameters "%d" are interpreted.
For example, you could create the parameter "%i" so the passed argument will be interpreted as a signed integer. To do so, add the following code in the switch within rsprintf:

            case 'i': val = parseInt(args[i]); 
                      if(temp & 0x80000000)
                      {
                        val = val - 0x100000000;
                      }; break;

Then, you should call Log_printf as following: Log_printf(LogModule_App1, Log_INFO, "RSSI = %i",pAdvRpt->rssi);

Let me know your results and I'll try to help for a way to display the BLE address in a better way as well.

Kind regards,

Hello Clement,

I have added the code as you suggested and removed the older log project from workspace and reloaded it to CCS.

The results using %i are not coming as expected. Do I need to do some other changes as well ?

Output - 

Thanks,

Garvit

Hi Garvit,

I have asked for some internal inputs that I haven't received yet.

Please give me a bit more time (mid-week next week to come back to you).

Thank you for your comprehension.

Best regards,

Hi Clement,

Thanks for the help. The code does function as expected now. 0x00 won't be a problem as the devices I want to detect as of now are assigned a static address starting from CA, CB and so on.

Thanks,

Garvit