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: TDA4VM: MCU2_1 crash when system start to run

Part Number: TDA4VM
Other Parts Discussed in Thread: SYSBIOS

Hi expert,

we met a issue: TDA4 can't run our customize mcu2_1 firmware, detail error as follow:

A72: QNX

thanks

  • Hi,

    Can you please provide some more detail on what is being tested, for example

    • Is the test being run on TI EVM, or custom platform?
    • Which SDK version is being used?  For example Processor SDK QNX 7.3?
    • Was the unmodified SDK MCU2_1 firmware image able to be run in the same setup under test?
    • What modifications were made to MCU2_1?   
      • Was a full clean/scrub done after making the changes?
    • Is the vision_apps framework being used, and the exception is seen when attempting to run a demo?
      • If so please provide full console logs, including boot.

    Thanks,

    kb

  • 1. TDAVM

    2. SDK QNX 7.1.

    3. Add some algorithm code to MCU2_1.

    4. Use vision_apps demo can run successfully, BUT after add our code, it can't run.

    Log shown crash in main thread.

    Jtag information as follow:

      

  • Hi expert,

    Detail log information from CCS as follow:

    ROV error log as follow:

    HWI:

    Caught exception in view init code: "/media/liufu/8CEA9AF9EA9ADF30/code/ti-processor-sdk-rtos-j721e-evm-07_01_00_11/bios_6_83_00_18/packages/ti/sysbios/family/arm/v7r/keystone3/Hwi.xs", line 554: Cannot read property "ENABLEDSET" from undefined

    Queue:

    Error: Problem scanning pend Queue: JavaException: java.lang.Exception: Target memory read failed at address: 0xffffffff, length: 8This read is at an INVALID address according to the application's section map. The application is likely either uninitialized or corrupt.

    Sample code as follow, include mcu2_1 firmware, lateapp1, sample code and cfg files. 5125.firmware.zip

    It is block issue for us,  please help check this issue.

    SDK version: 7.1

    QNX version: 7.0

    Thanks

  • Thank you for providing the sample code, it has not been reviewed as of yet.

    Regarding the error/issue being seen, when running vision_apps demos, the A72 logging mechanism is started as part of the "../vision_apps_init.sh" script.

    Please also run the ./vision_apps_init.sh" prior to running the new application, and provide all the console logs that are generated, when the vision_apps application is started.

    Thanks,

    kb

  • Sorry for that we can't provide log information, due to TDA4 couldn't enter OS when met this issue.

  • This issue is related with protobuf,  we have resolved it. 

    thanks for your support!

  • Can you provide some materials for debug R5F/DSP?

  • Thanks for the update, glad to hear it is working now.

    Please create a new thread for the question on "material for debug R5F/DSP"

    Regards,

    kb