• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 249 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.

MMWCAS-RF-EVM: SDK support for AWR2243

6336368
Prodigy 30 points
Part Number: MMWCAS-RF-EVM
Other Parts Discussed in Thread: AWR2243,

When can we expect SDK support for the AWR2243 eval kits you're currently selling?  I don't understand why you would sell evaluation kits that aren't supported by your SDK in the first place.

There a number of problems with using the current SDK (3.08) with the 2243 MMWCAS-RF-EVM.  I've applied the patches for the RF chips available elsewhere on this "forum", but I'm still having problems with the ethernet driver (seems to be a problem with MDI detection, as it works through a hub, but not directly connected to the host), and the SSD driver.

Repro instructions for the SSD driver issue:

root@dra7xx-evm:/run/media# dd if=/dev/null count=1024 of=nvme0n1p1/test

root@dra7xx-evm:/run/media# umount nvme0n1p1 && mount /dev/nvme0n1p1 nvme0n1p1 && md5sum nvme0n1p1/test
[ 168.066957] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
c1efd1a11c93c126bc054182580eda8e nvme0n1p1/test
root@dra7xx-evm:/run/media# umount nvme0n1p1 && mount /dev/nvme0n1p1 nvme0n1p1 && md5sum nvme0n1p1/test
[ 169.687736] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
f312cc3ed19016ae65c6051dda01183b nvme0n1p1/test
root@dra7xx-evm:/run/media# umount nvme0n1p1 && mount /dev/nvme0n1p1 nvme0n1p1 && md5sum nvme0n1p1/test
[ 171.226974] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
c69a7a1294fe15fadbcfb8b98f50f670 nvme0n1p1/test
root@dra7xx-evm:/run/media# umount nvme0n1p1 && mount /dev/nvme0n1p1 nvme0n1p1 && md5sum nvme0n1p1/test
[ 172.577590] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
320864c4370758227e0b5533e9e990ef nvme0n1p1/test
root@dra7xx-evm:/run/media# umount nvme0n1p1 && mount /dev/nvme0n1p1 nvme0n1p1 && md5sum nvme0n1p1/test
[ 173.647441] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
a964504e402650a2dbebdf21a2255f0f nvme0n1p1/test

  • 0
    Prodigy 30 points

    Pardon me, that should /dev/zero in the dd command above rather than /dev/null.

  • 0 in reply to 6336368
    TI__Guru 50045 points

    Hi,

    Was SSD card mounted correctly after boot? Were you able to access the drive?

    Regards,
    Stanley 

  • 0 in reply to Stanley Liu
    Prodigy 30 points

    It "mounts" after the boot, but the contents of files are not deterministic.  I consider determinism a key quality of the file abstraction.

    I'm not really interested in solving that problem at this point.  It's a problem with the 3.8 SDK, and I've moved on to getting things working with a hacked up version of the 3.7.1 SDK, which is what the mmWave Studio image is based on.  The problem that I'm really interested in solving is: Why did you sell me an EVM with no SDK support, with no warning that it wasn't supported?  This is not the quality that I've come to expect from TI.  In general, I *do* expect to have to hack, to some extent, on eval SDKs to get them to work, but in this case, the extent of hacking required is simply unprofessional.