This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: enable and parser the DMSC log in TDA4

Part Number: TDA4VM


Hi guys,

  I think that we can enable and parser the DMSC log via the python script in TDA4, but I still have below questons:

1. In default 7.1 SDK, SD BOOT mode, and we can get the DMSC log as below via minicom:

  

   and when I dump the trace buffer via ccs, I can find the data as below:

  

    my question is, why these data are different? Before I thought they should be the same things, just output way is different, correct?

2. I enabled the log output via modify the sciclient_defaultboardcfg.c file, and also build & generate the update h file. my question is, how should I update the binary/lib to SD card while using the SD boot mode?

Thanks a lot!

Br,

Neo

  • Hi Neo,

    1. In default 7.1 SDK, SD BOOT mode, and we can get the DMSC log as below via minicom:

    I need to check this myself and get back to you.

    2. I enabled the log output via modify the sciclient_defaultboardcfg.c file, and also build & generate the update h file. my question is, how should I update the binary/lib to SD card while using the SD boot mode?

    I believe you are using SBL, the SBL consumes the board configuration and links it from the PDK. Once you rebuild the boardcfg then you can simple clean the SBL and rebuild the SBL too.

    Run:

    make sbl_mmcsd_img_clean

    make sbl_lib_mmcsd_clean

    make sbl_lib_mmcsd

    make sbl_mmcsd_img

    You can then just use the new SBL. Please let me know if you are able to get the detailed DMSC traces with this.

    Regards,

    Karan

  • Hi Karan,

       I think the issue2 can be closed, but still confused about the issue1, hope you can help give some comments about this, thanks a lot!

    Br,

    Neo

  • Hi Neo,

    So the issue with the boardcfg is resolved but you still want to know why there is a delta between the memory browser and WKUP UART?

    Regards,

    Karan