• State
  • Locked Locked
  • Replies 12 replies
  • Subscribers 97 subscribers
  • Views 892 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.

TDA4VM: Why the tisci binary execute failed ?

Ruifeng Zhang
Intellectual 570 points
Part Number: TDA4VM


Hi Expert,

I work on the sdk8.2 with qnx os. And I found the tisci failed to execute about 1/600 probability.

Test case : power on / off

The log on A72 : 

[2023-02-10 20:34:31.638] Starting tisci-mgr..
[2023-02-10 20:34:31.640] /ti_fs/tibin/tisci-mgr[1]: syntax error: `(' unexpected
[2023-02-10 20:34:33.629] Unable to access /dev/tisci
[2023-02-10 20:34:33.631] Starting shmemallocator..
[2023-02-10 20:34:33.635] Starting tiipc-mgr..
[2023-02-10 20:34:33.716] Starting TI IPC Resmgr
[2023-02-10 20:34:33.718] open(/dev/tisci): No such file or directory
[2023-02-10 20:34:33.722] open(/dev/tisci): No such file or directory
[2023-02-10 20:34:33.726] open(/dev/tisci): No such file or directory
[2023-02-10 20:34:33.730] open(/dev/tisci): No such file or directory
[2023-02-10 20:34:33.734] open(/dev/tisci): No such file or directory

The code failed on scripts, e.g. user.sh

echo "Starting tisci-mgr.."
tisci-mgr
waitfor /dev/tisci 2

Please help to give some suggestions, thanks.

  • 0
    TI__Guru** 124711 points

    Hi Ruifeng,

    Will work to provide you a patch to test against, by the end of this week.  Patch may or may not be applicable to the issue you are seeing.

    Regards,

    kb

  • 0 in reply to KB
    Intellectual 570 points

    Hi KB,

    Could you please share the patch with me ?

  • 0 in reply to Ruifeng Zhang
    TI__Guru** 124711 points

    Hi Ruifeng,

    Attached patch will be part of SDK 8.6 release, please consider attached patch as unofficial for testing purposes.  This patch may or may not be related to the issue you are seeing.  Patch can be applied to SDK 8.2 as below:

    patch psdkqa/pdk/packages/ti/drv/sciclient/src/sciclient/sciclient_indirect.c < sciclient_indirect.c.patch

    Regards,

    kb

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/sciclient_5F00_indirect.c.patch

  • 0 in reply to KB
    Intellectual 570 points

    Hi KB,

    The patch doesn't work, the error was still reproduced. 

    The reason of this error seems to be related to the shell. The tisci program is not actually executed.

    [20230222_14:20:27]*RTOS-08_02_00_05 QNX-08_02_00_03 LINUX-08_02_00_03*
[20230222_14:20:27]****************************************************
[20230222_14:20:27]Starting tisci-mgr..
[20230222_14:20:27]/ti_fs/tibin/tisci-mgr[1]: syntax error: `(' unexpected
[20230222_14:20:29]Unable to access /dev/tisci
[20230222_14:20:29]Retry Starting tisci-mgr..
[20230222_14:20:29]/proc/boot/.console_ti.sh: /ti_fs/scripts/user.sh[20]: tisci-mgr: Input/output error
[20230222_14:20:31]Unable to access /dev/tisci
[20230222_14:20:31]Starting shmemallocator..
[20230222_14:20:31]/ti_fs/tibin/shmemallocator[1]: syntax error: `)' unexpected
[20230222_14:20:31]Starting tiipc-mgr..
[20230222_14:20:31]/ti_fs/tibin/tiipc-mgr[4]: ELF��@8: cannot execute - No such file or directory
[20230222_14:20:31]/ti_fs/tibin/tiipc-mgr[4]: @: cannot execute - No such file or directory
[20230222_14:20:31]/ti_fs/tibin/tiipc-mgr[4]: @: cannot execute - No such file or directory
[20230222_14:20:31]/ti_fs/tibin/tiipc-mgr[4]: �d�dP: cannot execute - No such file or directory
[20230222_14:20:31]/ti_fs/tibin/tiipc-mgr[4]: P: cannot execute - No such file or directory
[20230222_14:20:31]/ti_fs/tibin/tiipc-mgr[4]: P: cannot execute - No such file or directory
[20230222_14:20:31]/ti_fs/tibin/tiipc-mgr[4]: PPP: cannot execute - No such file or directory
[20230222_14:20:31]/ti_fs/tibin/tiipc-mgr[4]: @: cannot execute - No such file or directory
[20230222_14:20:31]/ti_fs/tibin/tiipc-mgr[4]: @: cannot execute - No such file or directory
[20230222_14:20:31]/ti_fs/tibin/tiipc-mgr: no closing quote
[20230222_14:20:31]Starting tiudma-mgr..
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]open(/dev/tisci): No such file or directory
[20230222_14:20:31]Start screen..
[20230222_14:20:31]screen started with dss_on_r5 configuration..
[20230222_14:20:31]done...
[20230222_14:20:31]J7EVM@QNX:/# ls /dev/tis*
[20230222_14:20:31]ls: No such file or directory (/dev/tis*)
[20230222_14:21:52]J7EVM@QNX:/# 
[20230222_14:22:01]J7EVM@QNX:/# ti 
[20230222_14:22:01]ti_fs/       tiboot3.bin  tilib/       times        timmlibenc   tispl.bin   
[20230222_14:22:01]tibin/       tiipc-mgr    time         timestamp    tisci-mgr    tiudma-mgr  
[20230222_14:22:03]J7EVM@QNX:/# tisci-mgr 
[20230222_14:22:07]J7EVM@QNX:/# ps
[20230222_14:22:07]       PID TTY          TIME CMD
[20230222_14:22:07]        11 ?        00:00:00 ksh
[20230222_14:22:07]    118798 ?        00:00:00 ksh
[20230222_14:22:07]    151568 ?        00:00:00 ps
[20230222_14:22:14]J7EVM@QNX:/# ls /dev/tis*
[20230222_14:22:14]/dev/tisci
[20230222_14:24:09]J7EVM@QNX:/#

  • 0 in reply to Ruifeng Zhang
    TI__Guru** 124711 points

    Hi Ruifeng,

    In the previously posted log it appears that all binaries are corrupt.   Is the reproducibility of above log still 1/600?

    Does the QNX command prompt return after the errors being shown?  If so please, provide output from 'slog2info' along with full boot log. 

    Regards,

    kb

  • 0 in reply to KB
    Intellectual 570 points

    Hi KB,

    The slog2info when error occur as following:

     9725 J7EVM@QNX:/# slog2info
 9726 Jan 01 00:00:00.030                       random.5                  low*     0  qcrypto: loading configuration file '/etc/qcrypto.conf' [qcrypto_common.c(190)]
 9727 Jan 01 00:00:00.031                    random.5..0                 slog*   700  Random is using the Fortuna PRNG
 9728 Jan 01 00:00:00.035                       random.5                  low      0  qcrypto: 'openssl' plugin loaded [qcrypto_plugins.c(354)]
 9729 Jan 01 00:00:00.035                    random.5..0                 slog    700  Selecting timer as an entropy source
 9730 Jan 01 00:00:00.035                    random.5..0                 slog    700  Registered path names
 9731 Jan 01 00:00:00.035                    random.5..0                 slog    700  random: starting resmgr
 9732 Jan 01 00:00:00.035                    random.5..0                 slog    700  random: Daemonizing the process
 9733 Jan 01 00:00:00.049             devb_sdmmc_am65x.9                 slog*  1800  devb-sdmmc-am65x 1.00A (Feb 28 2023 09:46:25)
 9734 Jan 01 00:00:00.049             devb_sdmmc_am65x.9                 slog      0  libcam.so (Sep  3 2021 11:57:38) bver 7010004
 9735 Jan 01 00:00:00.050             devb_sdmmc_am65x.9                 slog   1800  sdio_cd:  insertion path 0, cd state 0x1
 9736 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800  MMC CID:
 9737 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    MID 0x15, OID 0x0, PNM BGUF4R
 9738 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    PRV 0x39, PSN 0x79d35396, MDT 6-2021
 9739 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800  MMC CSD:
 9740 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    CSD_STRUCTURE 3, SPEC_VERS 4, CCC 0xf5
 9741 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    TAAC 39, NSAC 1, TRAN_SPEED 50
 9742 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    C_SIZE 4095, C_SIZE_MULT 7
 9743 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    READ_BL_LEN 9, WRITE_BL_LEN 9
 9744 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    ERASE GRP_SIZE 31, GRP_MULT 31, SIZE 0
 9745 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    blksz 512, sectors 2097152, dtr 25000000
 9746 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800  MMC EXT CSD:
 9747 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    DEVICE_TYPE 0x57, EXT_CSD_REV 8
 9748 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    SEC_COUNT 61079552, dtr 200000000
 9749 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    HC_ERASE_GRP_SIZE 1, HC_WP_GRP_SIZE 16
 9750 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    STROBE 0x1, BKOPS_EN 0x0
 9751 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800    Driver type: 0x0
 9752 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog   1800  CFG:  Timing HS200, DTR 200000000, Bus Width 8 bit
 9753
 9754 Jan 01 00:00:00.132             devb_sdmmc_am65x.9                 slog    100  cam-disk.so (Sep  3 2021 11:57:42)
 9755 Jan 01 00:00:30.707            devb_sdmmc_am65x.10                 slog*     0  _scsi_io_cbf:  status b, retry 3
 9756 Jan 01 00:00:30.908            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x200, lba 1064880, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
 9757 Jan 01 00:00:30.908            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a040, vuflag=0x0001, cmd=0x28
 9758 Jan 01 00:00:30.908            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 4
 9759 Jan 01 00:00:31.109            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x200, lba 1064880, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
 9760 Jan 01 00:00:31.109            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a040, vuflag=0x0001, cmd=0x28
 9761 Jan 01 00:00:31.109            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 5
 9762 Jan 01 00:00:31.310            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x200, lba 1064880, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
 9763 Jan 01 00:00:31.310            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a040, vuflag=0x0001, cmd=0x28
 9764 Jan 01 00:00:31.310            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 6
 9765 Jan 01 00:00:31.511            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x400, lba 127680, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
 9766 Jan 01 00:00:31.511            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x00000080, vuflag=0x0001, cmd=0x2a
 9767 Jan 01 00:00:31.511            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 1
 9768 Jan 01 00:00:31.712            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x200, lba 1064880, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
 9769 Jan 01 00:00:31.712            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a040, vuflag=0x0001, cmd=0x28
Jan 01 00:00:31.712            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 7
Jan 01 00:00:31.913            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x400, lba 127680, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
Jan 01 00:00:31.913            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a080, vuflag=0x0001, cmd=0x2a
Jan 01 00:00:31.913            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 2
Jan 01 00:00:32.114            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x200, lba 1064880, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
Jan 01 00:00:32.114            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a040, vuflag=0x0001, cmd=0x28
Jan 01 00:00:32.114            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 8
Jan 01 00:00:32.315            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x400, lba 127680, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
Jan 01 00:00:32.315            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a080, vuflag=0x0001, cmd=0x2a
Jan 01 00:00:32.315            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 3
Jan 01 00:00:32.516            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x200, lba 1064880, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
Jan 01 00:00:32.516            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a040, vuflag=0x0001, cmd=0x28
Jan 01 00:00:32.516            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 9
Jan 01 00:00:32.717            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x400, lba 127680, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
Jan 01 00:00:32.717            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a080, vuflag=0x0001, cmd=0x2a
Jan 01 00:00:32.717            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 4
Jan 01 00:00:32.918            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x200, lba 1064880, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
Jan 01 00:00:32.918            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a040, vuflag=0x0001, cmd=0x28
Jan 01 00:00:32.918            devb_sdmmc_am65x.10                 slog      0  scsi_io_done ptl-0:0:0:  I/O error 5 lba 1064880 (1064880 - 1064880), nlba 1, resid 1
Jan 01 00:00:33.119            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x400, lba 127680, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
Jan 01 00:00:33.119            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a080, vuflag=0x0001, cmd=0x2a
Jan 01 00:00:33.119            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 5
Jan 01 00:00:33.320            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x400, lba 127680, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
Jan 01 00:00:33.320            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a080, vuflag=0x0001, cmd=0x2a
Jan 01 00:00:33.320            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 6
Jan 01 00:00:33.521            devb_sdmmc_am65x.10                 slog   1800  sdmmc_rw:  flgs 0x400, lba 127680, len 512, status 0x104, cstatus 0x104, rsp[0] 0x900
Jan 01 00:00:33.521            devb_sdmmc_am65x.10                 slog      0  scsi_error (sdmmc ptl-0:0:0):  cam_status=0x4b, scsi_status=0x0, flag=0x0000a080, vuflag=0x0001, cmd=0x2a
Jan 01 00:00:33.521            devb_sdmmc_am65x.10                 slog      0  _scsi_io_cbf:  status b, retry 7

  • 0 in reply to Ruifeng Zhang
    Intellectual 570 points

    Hi KB,

    According to the log, the SD card seems init failed and drop into the tisci error.

    Please help to give some suggestions, thanks.

  • 0 in reply to Ruifeng Zhang
    Intellectual 570 points

    Hi KB,

    Please help to give some suggestions, thanks.

  • 0 in reply to Ruifeng Zhang
    TI__Guru** 124711 points

    Hi Ruifeng,

    Regarding logs shown above, where below line is taken from.   The log is not expected, and this indicates that the filesystem is not working as expected, and/or the binary is not in a correct format.  Both of these scenarios, could be caused by the driver for the device upon which the filesystem is located (sd card, emmc etc).

    [20230222_14:20:31]/ti_fs/tibin/tiipc-mgr[4]: ELF��@8: cannot execute - No such file or directory

    Some thoughts:

    • If a different SD card is used, is issue still seen?
    • If a different board is used is issue still seen?
    • If a slower mode of the driver is run (see "use" information of driver), is issue still seen?
    • If an "ls" is done on filesystem are files present?
    • Can binaries be run from filesystem under any conditions?
    • When formatting the filesystem, are same steps as those used for TI EVM used?

    Regards,

    kb

  • 0 in reply to KB
    Intellectual 570 points

    Hi KB,

    The log was output by the serial console when the error occur. Now the error reproduced probability is up to 1/50.

    > If a different SD card is used, is issue still seen?
    > If a different board is used is issue still seen?

    Yes, we test many SD cards on the different boards, the error occur in all boards. And the error only occur when filesystem mount by SD card, there is no problem with filesystem mount by emmc.


    > If a slower mode of the driver is run (see "use" information of driver), is issue still seen?

    We were using the HS SD card speed, it seems the most slow speed mode in the QNX support.

    timing=[~]timing  Set/Clear timings (hs, ddr, sdr12, sdr25, sdr50, sdr104, hs200, hs400).

 93     display_msg Starting MMC/SD memory card driver... SD
 94     devb-sdmmc-am65x blk cache=1m sdio addr=0x04fb0000,irq=36,timing=hs,bs=sscfg=0x8000 cam pnp disk name=sd

    > If an "ls" is done on filesystem are files present?

    Sometimes, after an error occurs, the file system will recover and "ls" will run normally. However, sometimes the file system cannot be recovered after an error occurs. At this time, the "ls" command will fail and an "Input/Output error" error will be reported.


    > Can binaries be run from filesystem under any conditions?

    As explained in the previous item, after the file system is recovered, the binary file can be executed normally, otherwise an "Input/Output Error" error will be reported.


    > When formatting the filesystem, are same steps as those used for TI EVM used?

    Yes, we used the format scripts in the SDK, the path is "psdkqa/qnx/scripts/mkcard_qnx.sh".

  • 0 in reply to Ruifeng Zhang
    Intellectual 570 points

    Hi KB,

    Please pay attention to the above reply. Is there any analysis direction? What causes the SD card initialization error in slog2info?

  • 0 in reply to Ruifeng Zhang
    TI__Guru** 124711 points

    Hi Ruifeng,

    Apologies for delayed response.  I did not understand below feedback on lower speed, did issue occur or not occur when testing SD at lower speeds?

    "We were using the HS SD card speed, it seems the most slow speed mode in the QNX support".

    Running the driver with something like below would ensure a lower speed, the timing parameter can be manipulated to see if speed makes a difference:

          devb-sdmmc-am65x blk cache=1m sdio addr=0x04fb0000,irq=36,timing=~hs200,bs=sscfg=0x8000 cam pnp disk name=sd

    The timing at which driver is running is shown in slog2info, the hs200 log from log provided above, is shown here below.

    9752 Jan 01 00:00:00.132 devb_sdmmc_am65x.9 slog 1800 CFG: Timing HS200, DTR 200000000, Bus Width 8 bit

    In general the findings above seem to point to an issue with the SD driver, which is owned by QNX, please ensure that they are part of the investigation.  TI is not aware of any issues with the SD driver on the TI EVM for SDK 8.6.

    Other possibilities are the pin configuration is not correct, or a possible H/W issue with the boards.   

    • To rule out possible H/W issue, the SD card could be mounted from different driver, be it from PSDK RTOS or PSDK Linux if those are available in your environment.
    • To rule out pin mux configuration, the pins which are being used could have their settings compared between EVM and H/W under test.

    Regards,

    kb