• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 468 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

SK-AM62A-LP: rpmsg_char_zerocopy sample code boot fail : DMSC ABI revision 3.1 Some tests have failed!!

Matt Liu
Prodigy 20 points
Part Number: SK-AM62A-LP

I am a new user, I would like to test rpmsg_char_zerocopy on my am62a evm.

I have test MCU SDK sample code ipc_rpmsg_echo_linux, all tests are fine. I can send and receive by default mcu code and linux app rpmsg_char_simple on am62a EVM.

Then, I built out the zerocopy sample code image as  rpmsg_char_zerocopy\am62ax-sk\mcu-r5fss0-0_freertos\ti-arm-clang\ipc_rpmsg_zerocopy_linux.release.appimage.hs_fs.

I flash to ospi nand just replace with zerocopy image , 

# When sending application image, make sure to flash at offset 0x800000 (default) or to whatever offset your bootloader is configured for
#--file=../../examples/drivers/ipc/ipc_rpmsg_echo_linux/am62ax-sk/mcu-r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage.hs_fs --operation=flash --flash-offset=0x800000
--file=../../examples/drivers/ipc/rpmsg_char_zerocopy/am62ax-sk/mcu-r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_zerocopy_linux.release.appimage.hs_fs --operation=flash --flash-offset=0x800000

but it boots fail:


DMSC Firmware Version 9.0.5--v09.00.05 (Kool Koala)
DMSC Firmware revision 0x9
DMSC ABI revision 3.1

Some tests have failed!!

What else should I check to this boot issue?

my sdk : 

mcu_plus_sdk_am62ax_09_00_00_19

ti-processor-sdk-linux-edgeai-am62axx-evm-09_00_01_03

linux sdcard image : tisdk-edgeai-image-am62axx-evm.wic.xz

my flash script :

default_sbl_ospi_nand_linux_zerocopy_hs_fs.cfgdefault_sbl_ospi_nand_linux_zerocopy_hs_fs.cfg

  • +1
    TI__Guru 69581 points

    Hi Matt,

    I believe you have taken the rpmsg_char_zerocopy example from the following repo

    https://git.ti.com/cgit/rpmsg/rpmsg_char_zerocopy/

    If yes, the boot failure occurs because of the incompatible authentication type the makefiles are using. The examples for every core in this repo uses authentication type 1 which is incompatible with the authentication type 2 used by the MCU+ SDK v9. Please change the authentication type as shown below.

    This should resolve the issue.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hi Prashant,

    Thank you for your answer that resolved my issue.

    Now, I can test it on my EVM correctly.

    # ./rpmsg_char_zerocopy -r 0 -e carveout_edgeai_shared-memories -s 1 -p16
    Created endpt device rpmsg-char-0-1196, fd = 4 port = 1025
    Exchanging 1 messages with rpmsg device on rproc id 0 ...

    dma-buf address: 0xa3000000
    Buffer @0xffffa2147000 (size 1024) filled with pattern 0xaaaa5555
    Sending buffer data #0
    Address: 0xa3000000
    Size: 1024
    Pattern: 0xaaaa5555
    Receiving buffer data #0:
    Address: 0xa3000000
    Size: 1024
    Pattern: 0x5555aaaa
    Buffer @0xffffa2147000 (size 1024) successfully validated with pattern 0x5555aaaa

    Completed 1 buffer updates successfully on rpmsg-char-0-1196

    TEST STATUS: PASSED