Part Number: EVMK2H

Tool/software: TI-RTOS

Hello,

The SDK that is posted states there is a Template Application located in the processor_sdk_rtos_<platform>_<version> directory. Looking in demo folder in this directory I can't find any template application. Has this been moved to another location in more recent SDKs or can you post the template application here? I would like to use it to get started developing with the RTOS and this template seems like the most straight forward method. 

My SDK is a clean install and I have the latest two versions, 6.00.00.07 & 5.03.00.07. Both don't have them in the directory.

SDK reference: http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_examples_demos.html

Thanks,

Kevin

Part Number: TMS320C6678

I have a situation where occasionally in the field one core becomes non-responsive to the point that not even the NMI is recognized. I have reason to believe that this is the result of a bad memory address likely 0), but don't know where.

What I would like to do is have the core trigger an exception instead of hanging.

This is what I have to enable it, but is not working:

CSL_MpuHandle hMpu;
Uint32 startAddress = 0;
Uint32 endAddress = 0x00010000;
Uint32 permissions = 0;

// Open the MPU MPU Module 0
hMpu = CSL_MPU_Open (0);

// Set the permissions for the Region 1.
CSL_MPU_SetProgrammableAddressInfo (hMpu, 1, startAddress, endAddress, permissions);

// Pointer to the exception combiner mask register 3.
U32* expMask3 = reinterpret_cast<U32*>(0x018000CC);

*expMask3 = 0xC07FFFFF;

Any suggestions?

Part Number: PROCESSOR-SDK-AM65X

Tool/software: Linux

Hello,

I am trying to build U-Boot for the AM65x IDK using the version of U-Boot used with the latest Linux SDK release. Specifically, branch ti-2019.01 and commit 2654d29fd037730ebb154e9eda257acd7175b46b.

Using the instructions in board/ti/am65x/README, U-Boot fails to build the A53 portion of the build with the following errors:

  ... (previous lines snipped)
  CC      examples/standalone/stubs.o
  LD      examples/standalone/libstubs.o
  CC      examples/standalone/hello_world.o
  LD      examples/standalone/hello_world
  OBJCOPY examples/standalone/hello_world.srec
  OBJCOPY examples/standalone/hello_world.bin
  LDS     u-boot.lds
  LD      u-boot
  OBJCOPY u-boot-nodtb.bin
start=$(aarch64-linux-gnu-nm u-boot | grep __rel_dyn_start | cut -f 1 -d ' '); end=$(aarch64-linux-gnu-nm u-boot | grep __rel_dyn_end | cut -f 1 -d ' '); tools/relocate-rela u-boot-nodtb.bin 0x80800000 $start $end
  DTC     arch/arm/dts/k3-am654-base-board.dtb
  DTC     arch/arm/dts/k3-am654-r5-base-board.dtb
arch/arm/dts/k3-am654-r5-base-board.dtb: Warning (avoid_unnecessary_addr_size): /interconnect@100000/interconnect@28380000/interconnect@42040000/i2c@42120000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
  DTCO    arch/arm/dts/k3-am654-pcie-usb2.dtbo
  DTCO    arch/arm/dts/k3-am654-idk.dtbo
make[4]: 'arch/arm/dts/k3-am654-base-board.dtb' is up to date.
  SHIPPED dts/dt.dtb
  FDTGREP dts/dt-spl.dtb
/home/mmckee/dev/am6/uboot/arch/arm/mach-k3/make_fit.py am65x \
arch/arm/dts/k3-am654-base-board.dtb > u-boot.its
cannot find k3-am654-gp.dtbo. removing from its!
cannot find k3-am654-pcie-usb3.dtbo. removing from its!
cannot find k3-am654-evm-oldi-lcd1evm.dtbo. removing from its!
  MKIMAGE u-boot.itb
./tools/mkimage: Invalid FIT blob
/home/mmckee/dev/am6/uboot/Makefile:1209: recipe for target 'u-boot.itb' failed
make[2]: *** [u-boot.itb] Error 255
/home/mmckee/dev/am6/uboot/Makefile:478: recipe for target '__build_one_by_one' failed
make[1]: *** [__build_one_by_one] Error 2
make[1]: Leaving directory '/tmp/a53'
Makefile:148: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2
Error: last command exited with non-zero exit status.

I had no issue building U-Boot in the previous version of the SDK.

Thanks,

Matt McKee

Part Number: AM5728

Tool/software: Linux

We are working on custom board based on AM5728 . The board works fine with micro sd card loaded with all the linux SDK 03.02 . We wanted to copy it to eMMC and hence tried formatting it using fdisk.we observed the following errors.kindly help.

Messages on terminal of custom board 1:

root@am57xx-evm:~# fdisk /dev/mmcblk1

Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.[  340.491341] mmcblk1: error -110 sending status command, retrying

Be careful before using the write command.

[  340.507205] mmcblk1: error -110 sending status command, retrying
[  340.517452] mmcblk1: error -110 sending status command, aborting
[  340.523519] blk_update_request: 43 callbacks suppressed
[  340.528805] blk_update_request: I/O error, dev mmcblk1, sector 0
[  340.534933] mmcblk1: error -110 sending status command, retrying
[  340.541007] mmcblk1: error -110 sending status command, retrying
[  340.547048] mmcblk1: error -110 sending status command, aborting
[  340.553111] blk_update_request: I/O error, dev mmcblk1, sector 0
[  340.559177] Buffer I/O error on dev mmcblk1, logical block 0, async page read
dfisk: acnnot open /dev/mmcblk1 :Input/output error
orot@am57xx-evm:~#

Messages on terminal of custom board 2:

root@am57xx-evm:~# mkfs.vfat -F 32 -n "boot" /dev/mmcblk1p1
mkfs.fat 3.0.28 (2015-05-16)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
root@am57xx-evm:~# mkfs.ext3 -L "rootfs" /dev/mmcblk1p2
mke2fs 1.43-WIP (18-May-2015)
Discarding device blocks: done
Creating filesystem with 3586304 4k blocks and 897600 inodes
Filesystem UUID: 7f3e4b4c-699c-4750-bef3-29a3bd05b936
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done
Writing inode tables: [  245.192608] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.202165] mmcblk1: error -5 transferring data, sector 15611920, nr 2560, cmd response 0x900, card status 0xc00
[  245.212528] blk_update_request: I/O error, dev mmcblk1, sector 15611920
[  245.220815] Buffer I/O error on dev mmcblk1p2, logical block 1933314, lost async page write
[  245.230044] blk_update_request: I/O error, dev mmcblk1, sector 15611928
[  245.236698] Buffer I/O error on dev mmcblk1p2, logical block 1933315, lost async page write
[  245.246759] blk_update_request: I/O error, dev mmcblk1, sector 15611936
[  245.254236] Buffer I/O error on dev mmcblk1p2, logical block 1933316, lost async page write
[  245.263680] blk_update_request: I/O error, dev mmcblk1, sector 15611944
[  245.271187] Buffer I/O error on dev mmcblk1p2, logical block 1933317, lost async page write
[  245.280510] blk_update_request: I/O error, dev mmcblk1, sector 15611952
[  245.287164] Buffer I/O error on dev mmcblk1p2, logical block 1933318, lost async page write
[  245.297275] blk_update_request: I/O error, dev mmcblk1, sector 15611960
[  245.304587] Buffer I/O error on dev mmcblk1p2, logical block 1933319, lost async page write
[  245.313699] blk_update_request: I/O error, dev mmcblk1, sector 15611968
[  245.321008] Buffer I/O error on dev mmcblk1p2, logical block 1933320, lost async page write
[  245.330302] blk_update_request: I/O error, dev mmcblk1, sector 15611976
[  245.336950] Buffer I/O error on dev mmcblk1p2, logical block 1933321, lost async page write
[  245.346652] blk_update_request: I/O error, dev mmcblk1, sector 15611984
[  245.353958] Buffer I/O error on dev mmcblk1p2, logical block 1933322, lost async page write
[  245.363040] blk_update_request: I/O error, dev mmcblk1, sector 15611992
[  245.370361] Buffer I/O error on dev mmcblk1p2, logical block 1933323, lost async page write
[  245.385384] mmcblk1: error -84 transferring data, sector 15614480, nr 1520, cmd response 0x900, card status 0xc00
[  245.398797] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.406592] mmcblk1: error -5 transferring data, sector 15874064, nr 2560, cmd response 0x900, card status 0xc00
[  245.423686] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.431494] mmcblk1: error -5 transferring data, sector 15876624, nr 1520, cmd response 0x900, card status 0xc00
[  245.473409] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.483007] mmcblk1: error -5 transferring data, sector 16136208, nr 2560, cmd response 0x900, card status 0xc00
[  245.500495] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.509485] mmcblk1: error -5 transferring data, sector 16138768, nr 1520, cmd response 0x900, card status 0x0
[  245.521960] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.531550] mmcblk1: error -5 transferring data, sector 16398352, nr 2560, cmd response 0x900, card status 0xc00
[  245.547911] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.557532] mmcblk1: error -5 transferring data, sector 16400912, nr 1520, cmd response 0x900, card status 0xc00
[  245.571177] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.580164] mmcblk1: error -5 transferring data, sector 16660496, nr 2560, cmd response 0x900, card status 0xc00
[  245.596619] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.606205] mmcblk1: error -5 transferring data, sector 16663056, nr 1520, cmd response 0x900, card status 0xc00
[  245.619589] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.627420] mmcblk1: error -5 transferring data, sector 16922640, nr 2560, cmd response 0x900, card status 0x0
[  245.644234] mmcblk1: error -84 transferring data, sector 16925200, nr 1520, cmd response 0x900, card status 0xc00
[  245.656371] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.665535] mmcblk1: error -5 transferring data, sector 17184784, nr 2560, cmd response 0x900, card status 0xc00
[  245.681164] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.689794] mmcblk1: error -5 transferring data, sector 17187344, nr 1520, cmd response 0x900, card status 0xc00
[  245.701850] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.710890] mmcblk1: error -5 transferring data, sector 17446928, nr 2560, cmd response 0x900, card status 0xc00
[  245.725990] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.735335] mmcblk1: error -5 transferring data, sector 17449488, nr 1520, cmd response 0x900, card status 0xc00
[  245.747485] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.756755] mmcblk1: error -5 transferring data, sector 17709072, nr 2560, cmd response 0x900, card status 0xc00
[  245.772914] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.781797] mmcblk1: error -5 transferring data, sector 17711632, nr 1520, cmd response 0x900, card status 0x0
[  245.793930] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.803213] mmcblk1: error -5 transferring data, sector 17971216, nr 2560, cmd response 0x900, card status 0xc00
done
[  245.819243] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.827057] mmcblk1: error -5 transferring data, sector 17973776, nr 1520, cmd response 0x900, card status 0xc00
[  245.840659] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.849265] mmcblk1: error -5 transferring data, sector 18233360, nr 2560, cmd response 0x900, card status 0xc00
[  245.864310] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.873424] mmcblk1: error -5 transferring data, sector 18235920, nr 1520, cmd response 0x900, card status 0xc00
[  245.885559] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.894835] mmcblk1: error -5 transferring data, sector 18495504, nr 2560, cmd response 0x900, card status 0xc00
Creating journal (32768 blocks): [  245.910680] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.920546] mmcblk1: error -5 transferring data, sector 18498064, nr 1520, cmd response 0x900, card status 0xc00
[  245.932636] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.941788] mmcblk1: error -5 transferring data, sector 18757648, nr 2560, cmd response 0x900, card status 0xc00
[  245.956886] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.966058] mmcblk1: error -5 transferring data, sector 18760208, nr 1520, cmd response 0x900, card status 0xc00
[  245.978691] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  245.986480] mmcblk1: error -5 transferring data, sector 19019792, nr 2560, cmd response 0x900, card status 0xc00
[  246.002938] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.011597] mmcblk1: error -5 transferring data, sector 19022352, nr 1520, cmd response 0x900, card status 0xc00
[  246.023745] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.032790] mmcblk1: error -5 transferring data, sector 19281936, nr 2560, cmd response 0x900, card status 0xc00
[  246.047903] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.057063] mmcblk1: error -5 transferring data, sector 19284496, nr 1520, cmd response 0x900, card status 0xc00
[  246.069745] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.077525] mmcblk1: error -5 transferring data, sector 19544080, nr 2560, cmd response 0x900, card status 0xc00
[  246.093918] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.102591] mmcblk1: error -5 transferring data, sector 19546640, nr 1520, cmd response 0x900, card status 0xc00
[  246.114668] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.123801] mmcblk1: error -5 transferring data, sector 19806224, nr 2560, cmd response 0x900, card status 0xc00
[  246.140058] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.147892] mmcblk1: error -5 transferring data, sector 19808784, nr 1520, cmd response 0x900, card status 0xc00
[  246.161285] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.169894] mmcblk1: error -5 transferring data, sector 20068368, nr 2560, cmd response 0x900, card status 0xc00
[  246.184969] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.194311] mmcblk1: error -5 transferring data, sector 20070928, nr 1520, cmd response 0x900, card status 0xc00
[  246.206389] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.215534] mmcblk1: error -5 transferring data, sector 20330512, nr 2560, cmd response 0x900, card status 0xc00
[  246.231390] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.240069] mmcblk1: error -5 transferring data, sector 20333072, nr 1520, cmd response 0x900, card status 0xc00
[  246.252129] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.261318] mmcblk1: error -5 transferring data, sector 20592656, nr 2560, cmd response 0x900, card status 0xc00
[  246.276461] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.285597] mmcblk1: error -5 transferring data, sector 20595216, nr 1520, cmd response 0x900, card status 0xc00
[  246.297649] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.306742] mmcblk1: error -5 transferring data, sector 20854800, nr 2560, cmd response 0x900, card status 0xc00
[  246.322556] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.331237] mmcblk1: error -5 transferring data, sector 20857360, nr 1520, cmd response 0x900, card status 0xc00
[  246.343996] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.353148] mmcblk1: error -5 transferring data, sector 21116944, nr 2560, cmd response 0x900, card status 0xc00
[  246.368862] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.376670] mmcblk1: error -5 transferring data, sector 21119504, nr 1520, cmd response 0x900, card status 0xc00
[  246.393568] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.401373] mmcblk1: error -5 transferring data, sector 21386104, nr 2560, cmd response 0x900, card status 0xc00
[  246.420869] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.429565] mmcblk1: error -5 transferring data, sector 21388664, nr 1520, cmd response 0x900, card status 0xc00
[  246.441638] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.450933] mmcblk1: error -5 transferring data, sector 21641232, nr 2560, cmd response 0x900, card status 0xc00
[  246.466108] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.475479] mmcblk1: error -5 transferring data, sector 21643792, nr 1520, cmd response 0x900, card status 0xc00
[  246.487559] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.495980] mmcblk1: error -5 transferring data, sector 21903376, nr 2560, cmd response 0x900, card status 0xc00
[  246.513591] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.522315] mmcblk1: error -5 transferring data, sector 21905936, nr 1520, cmd response 0x900, card status 0xc00
[  246.534349] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.542199] mmcblk1: error -5 transferring data, sector 22165520, nr 2560, cmd response 0x900, card status 0xc00
[  246.557506] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.565414] mmcblk1: error -5 transferring data, sector 22168080, nr 1520, cmd response 0x900, card status 0xc00
[  246.577543] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.585368] mmcblk1: error -5 transferring data, sector 22427664, nr 2560, cmd response 0x900, card status 0xc00
[  246.600523] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.608388] mmcblk1: error -5 transferring data, sector 22430224, nr 1520, cmd response 0x900, card status 0xc00
[  246.620452] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.628248] mmcblk1: error -5 transferring data, sector 22689808, nr 2560, cmd response 0x900, card status 0xc00
[  246.643388] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.651242] mmcblk1: error -5 transferring data, sector 22692368, nr 1520, cmd response 0x900, card status 0xc00
[  246.663324] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.671129] mmcblk1: error -5 transferring data, sector 22951952, nr 2560, cmd response 0x900, card status 0xc00
[  246.686246] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.694084] mmcblk1: error -5 transferring data, sector 22954512, nr 1520, cmd response 0x900, card status 0xc00
[  246.706219] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.714059] mmcblk1: error -5 transferring data, sector 23214096, nr 2560, cmd response 0x900, card status 0xc00
[  246.729460] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.737296] mmcblk1: error -5 transferring data, sector 23216656, nr 1520, cmd response 0x900, card status 0xc00
[  246.749442] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.757218] mmcblk1: error -5 transferring data, sector 23476240, nr 2560, cmd response 0x900, card status 0xc00
[  246.772424] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.780285] mmcblk1: error -5 transferring data, sector 23478800, nr 1520, cmd response 0x900, card status 0xc00
[  246.792355] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.800183] mmcblk1: error -5 transferring data, sector 23738384, nr 2560, cmd response 0x900, card status 0xc00
[  246.815466] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.823385] mmcblk1: error -5 transferring data, sector 23740944, nr 1520, cmd response 0x900, card status 0xc00
[  246.835697] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.843558] mmcblk1: error -5 transferring data, sector 24000528, nr 2560, cmd response 0x900, card status 0xc00
[  246.858996] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.866847] mmcblk1: error -5 transferring data, sector 24003088, nr 1520, cmd response 0x900, card status 0xc00
[  246.879132] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.886919] mmcblk1: error -5 transferring data, sector 24262672, nr 2560, cmd response 0x900, card status 0xc00
[  246.902054] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.909917] mmcblk1: error -5 transferring data, sector 24265232, nr 1520, cmd response 0x900, card status 0xc00
[  246.921988] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.929791] mmcblk1: error -5 transferring data, sector 24524816, nr 2560, cmd response 0x900, card status 0xc00
[  246.944909] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.952747] mmcblk1: error -5 transferring data, sector 24527376, nr 1520, cmd response 0x900, card status 0xc00
[  246.964812] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.972610] mmcblk1: error -5 transferring data, sector 24786960, nr 2560, cmd response 0x900, card status 0xc00
[  246.987744] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  246.995573] mmcblk1: error -5 transferring data, sector 24789520, nr 1520, cmd response 0x900, card status 0xc00
[  247.007629] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.015461] mmcblk1: error -5 transferring data, sector 25049104, nr 2560, cmd response 0x900, card status 0xc00
[  247.030642] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.038561] mmcblk1: error -5 transferring data, sector 25051664, nr 1520, cmd response 0x900, card status 0xc00
[  247.050600] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.058446] mmcblk1: error -5 transferring data, sector 25311248, nr 2560, cmd response 0x900, card status 0xc00
[  247.073580] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.081436] mmcblk1: error -5 transferring data, sector 25313808, nr 1520, cmd response 0x900, card status 0xc00
[  247.093664] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.101465] mmcblk1: error -5 transferring data, sector 25573392, nr 2560, cmd response 0x900, card status 0xc00
[  247.116563] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.124398] mmcblk1: error -5 transferring data, sector 25575952, nr 1520, cmd response 0x900, card status 0xc00
[  247.136461] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.144267] mmcblk1: error -5 transferring data, sector 25835536, nr 2560, cmd response 0x900, card status 0xc00
[  247.159599] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.167414] mmcblk1: error -5 transferring data, sector 25838096, nr 1520, cmd response 0x900, card status 0xc00
[  247.179578] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.187362] mmcblk1: error -5 transferring data, sector 26097680, nr 2560, cmd response 0x900, card status 0xc00
[  247.202505] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.210358] mmcblk1: error -5 transferring data, sector 26100240, nr 1520, cmd response 0x900, card status 0xc00
[  247.222412] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.230229] mmcblk1: error -5 transferring data, sector 26359824, nr 2560, cmd response 0x900, card status 0xc00
[  247.245334] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.253178] mmcblk1: error -5 transferring data, sector 26362384, nr 1520, cmd response 0x900, card status 0xc00
[  247.265273] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.273069] mmcblk1: error -5 transferring data, sector 26621968, nr 2560, cmd response 0x900, card status 0xc00
[  247.288212] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.296019] mmcblk1: error -5 transferring data, sector 26624528, nr 1520, cmd response 0x900, card status 0xc00
[  247.308178] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.315956] mmcblk1: error -5 transferring data, sector 26884112, nr 2560, cmd response 0x900, card status 0xc00
[  247.331133] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.338974] mmcblk1: error -5 transferring data, sector 26886672, nr 1520, cmd response 0x900, card status 0xc00
[  247.351761] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.359583] mmcblk1: error -5 transferring data, sector 27146256, nr 2560, cmd response 0x900, card status 0xc00
[  247.374662] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.382503] mmcblk1: error -5 transferring data, sector 27148816, nr 1520, cmd response 0x900, card status 0xc00
[  247.394532] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.402362] mmcblk1: error -5 transferring data, sector 27408400, nr 2560, cmd response 0x900, card status 0xc00
[  247.417491] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.425330] mmcblk1: error -5 transferring data, sector 27410960, nr 1520, cmd response 0x900, card status 0xc00
[  247.437396] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.445201] mmcblk1: error -5 transferring data, sector 27670544, nr 2560, cmd response 0x900, card status 0xc00
[  247.460477] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.468324] mmcblk1: error -5 transferring data, sector 27673104, nr 1520, cmd response 0x900, card status 0xc00
[  247.480444] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.488252] mmcblk1: error -5 transferring data, sector 27932688, nr 2560, cmd response 0x900, card status 0xc00
[  247.503360] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.511218] mmcblk1: error -5 transferring data, sector 27935248, nr 1520, cmd response 0x900, card status 0xc00
[  247.523268] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.531067] mmcblk1: error -5 transferring data, sector 28194832, nr 2560, cmd response 0x900, card status 0xc00
[  247.546214] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.554049] mmcblk1: error -5 transferring data, sector 28197392, nr 1520, cmd response 0x900, card status 0xc00
[  247.566129] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.573970] mmcblk1: error -5 transferring data, sector 28456976, nr 2560, cmd response 0x900, card status 0xc00
[  247.589186] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.596990] mmcblk1: error -5 transferring data, sector 145424, nr 2560, cmd response 0x900, card status 0xc00
[  247.611977] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.619809] mmcblk1: error -5 transferring data, sector 147984, nr 2560, cmd response 0x900, card status 0xc00
[  247.634726] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.642473] mmcblk1: error -5 transferring data, sector 150544, nr 1880, cmd response 0x900, card status 0xc00
[  247.655132] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.662997] mmcblk1: error -5 transferring data, sector 152440, nr 8, cmd response 0x900, card status 0xc00
[  247.672909] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.680738] mmcblk1: error -5 transferring data, sector 156520, nr 2560, cmd response 0x900, card status 0xc00
[  247.695675] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.703517] mmcblk1: error -5 transferring data, sector 159080, nr 2560, cmd response 0x900, card status 0xc00
[  247.718523] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.726271] mmcblk1: error -5 transferring data, sector 161640, nr 2560, cmd response 0x900, card status 0xc00
[  247.741284] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.749147] mmcblk1: error -5 transferring data, sector 164200, nr 664, cmd response 0x900, card status 0xc00
[  247.759734] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.767547] mmcblk1: error -5 transferring data, sector 164872, nr 2560, cmd response 0x900, card status 0xc00
[  247.782583] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.790437] mmcblk1: error -5 transferring data, sector 167432, nr 2560, cmd response 0x900, card status 0xc00
[  247.805457] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.813339] mmcblk1: error -5 transferring data, sector 169992, nr 2560, cmd response 0x900, card status 0xc00
[  247.828347] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  247.836133] mmcblk1: error -5 transferring data, sector 172552, nr 2560, cmd response 0x900, card status 0xc00
[  248.281134] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.294035] mmcblk1: error -5 transferring data, sector 200712, nr 2560, cmd response 0x900, card status 0xc00
[  248.312596] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.322487] mmcblk1: error -5 transferring data, sector 203272, nr 2560, cmd response 0x900, card status 0xc00
[  248.342588] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.350611] mmcblk1: error -5 transferring data, sector 205832, nr 2560, cmd response 0x900, card status 0xc00
[  248.372085] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.381027] mmcblk1: error -5 transferring data, sector 208392, nr 2560, cmd response 0x900, card status 0xc00
[  248.399188] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.407030] mmcblk1: error -5 transferring data, sector 210952, nr 2560, cmd response 0x900, card status 0xc00
[  248.425259] mmcblk1: error -84 transferring data, sector 213512, nr 2560, cmd response 0x900, card status 0x0
[  248.442571] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.452771] mmcblk1: error -5 transferring data, sector 216072, nr 2560, cmd response 0x900, card status 0xc00
[  248.471450] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.483177] mmcblk1: error -5 transferring data, sector 218632, nr 2560, cmd response 0x900, card status 0xc00
[  248.503363] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.511176] mmcblk1: error -5 transferring data, sector 221192, nr 2560, cmd response 0x900, card status 0xc00
[  248.533105] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.542185] mmcblk1: error -5 transferring data, sector 223752, nr 2560, cmd response 0x900, card status 0xc00
[  248.559351] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.567253] mmcblk1: error -5 transferring data, sector 226312, nr 2560, cmd response 0x900, card status 0xc00
[  248.585256] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.594221] mmcblk1: error -5 transferring data, sector 228872, nr 2560, cmd response 0x900, card status 0xc00
[  248.611491] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.620411] mmcblk1: error -5 transferring data, sector 231432, nr 2560, cmd response 0x900, card status 0xc00
[  248.636703] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.646209] mmcblk1: error -5 transferring data, sector 233992, nr 2560, cmd response 0x900, card status 0xc00
[  248.672197] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.680053] mmcblk1: error -5 transferring data, sector 236552, nr 2128, cmd response 0x900, card status 0xc00
[  248.701442] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.709274] mmcblk1: error -5 transferring data, sector 238680, nr 2560, cmd response 0x900, card status 0xc00
[  248.729575] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.737334] mmcblk1: error -5 transferring data, sector 241240, nr 2560, cmd response 0x900, card status 0xc00
[  248.755085] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.764156] mmcblk1: error -5 transferring data, sector 243800, nr 2560, cmd response 0x900, card status 0xc00
[  248.780823] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.788828] mmcblk1: error -5 transferring data, sector 246360, nr 2560, cmd response 0x900, card status 0xc00
[  248.805307] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.813344] mmcblk1: error -5 transferring data, sector 248920, nr 2560, cmd response 0x900, card status 0xc00
done
Writing superblocks and filesystem accounting information: [  248.830257] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.838216] mmcblk1: error -5 transferring data, sector 251480, nr 2560, cmd response 0x900, card status 0xc00
[  248.853511] omap_hsmmc 480b4000.mmc: ADMA err: ST_FDS, erroneous desc at 0x00000000
[  248.861327] mmcblk1: error -5 transferring data, sector 254040, nr 2560, cmd response 0x900, card status 0xc00
[  251.478434] VFS: Dirty inode writeback failed for block device mmcblk1p2 (err=-5).
done

Part Number: AM5728

Tool/software: Linux

We made two custom boards based on AM5728 . We developed software for it using linux SDK 03.02 and able to boot and test our application software on it. It is working fine on our first board .We are now testing the same software on our second custom board but experiencing inconsistency in booting. It gets stuck after executing MLO. KIndly suggest the area to look into for debugging it.

bootlog:

U-Boot SPL 2016.05 (Jan 03 2019 - 09:34:14)
DRA752-GP ES2.0
Trying to boot from MMC1
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img

Part Number: BEAGLEBK

Tool/software: Linux

I'm using beaglebone balck,running debian 9.1. When I start beaglebone, it will shows a serias errors as bellow:

Starting kernel ...

[    0.000797] clocksource_probe: no matching clocksources found
[    2.081576] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[    2.262704] ti_emif_sram 4c000000.emif: Unable to get sram pool for ocmcram
[    2.280958] omap_voltage_late_init: Voltage driver support not added
[    2.292324] PM: Cannot get wkup_m3_ipc handle
[    2.355945] cpu cpu0: _of_add_opp_table_v2: Failed to add OPP, -17
[    2.362741] cpu: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:0, -17
[    2.371336] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed
[    2.683575] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed
[   18.556861] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed

Debian GNU/Linux 9 beaglebone ttyS0

BeagleBoard.org Debian Image 2017-09-21

Support/FAQ: elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

beaglebone login: [   22.036636] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed
[   22.118824] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed
[   22.485769] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed
[   22.516665] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed
[   23.074407] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed
[   23.110488] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed
[   24.788364] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed
[   24.861187] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed
[   27.947970] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed
[   27.976843] PM: am33xx_prepare_push_sram_idle: EMIF function copy failed

Why shows "PM: am33xx_prepare_push_sram_idle: EMIF function copy failed" and how to resolve this problem?

Thanks.

Part Number: AM5718

Tool/software: Linux

Hi everyone, 

On our custom am5718 board, we have HDMI connected as attached image. If we remove the ADV7611 and ADV7393 from our HDMI path, we are able to run ksmcube application and is running without issue. But with the above chips included, we are not  seeing anything on the diplay. Using modetest command, it is listing the diplay details. we have added adv7393 and ADV7604(for supporting ADV7611) in our menuconfig and both are detected properly in linux as verified from the Linux boot prints. Someone pls help us with this issue?  Should i modify anything on the default configuratuion in drivers given or same default configuration will work?

Linux Version : linux-4.14.67+gitAUTOINC+d315a9bb00-gd315a9bb00

Regards,

Noufal P

Part Number: DRA80M

Customer would like to know when the issues list in the errata revision 1 will be fix?

Part Number: TCI6638K2K

Tool/software: Linux

I would like to process packets from XGMII ports in linux user space, can anyone tell me where I can find the linux user space driver for XGMII ports? Appreciated your kindly help,

Part Number: TDA2SX

Tool/software: Linux

Hello all,

                            We are working on a custom board based on tda2sx.We are trying to interface tlv320aic34 to mcasp4 and mcasp7.We made the pinmux and other configuration on the device tree.While booting we are getting this error and mcasp realted inititialization is crashing.

clock: dpll_abe_ck failed transition to 'locked'
clock: dpll_abe_ck failed transition to 'locked'

                               We did some investigation and noticed that mcasp uses dpll_abe clk.On further investiagtion we found that dpll_abe is generated from sysclk2.In our custom board sysclk2 crystal osc is not mounted.How I can make dpll_abe use sysclk1 instead?Which files should i modify?

SDK version:3.07

Regards,

Murugan S

Part Number: 66AK2H14

Tool/software: TI-RTOS

Dear TI Team,

I am using pdk_k2hk_4_0_12 example PA_emacExample_K2HC66BiosExampleProject  with code composer studio V8.

I am using CPSW_LOOPBACK_NONE. I connect EVM with my laptop and receiving UDP Packets on Wireshark successfully after this example try to receive the same packet and compare the packet. I am using  Colasoft packet builder to send packet to EVM but it dose not receive any packet. 

I just swap the EMAC addresses of the receive packet letting remaining  packet same.

Please tell me if it is the switch that is not letting the packet into RxQueue in case I build packet with wrong EMAC address of IP address.

Best Regards,

Umer Qureshi

Part Number: BEAGLEBK

Tool/software: Linux

We use make a develop board, based on BeagleBone Black's hardware. We add a aic3106. We have problem on configure aic3106 node in devicetree.

Our aic3106 node configuration is similiar to am335x evm:

&i2c1{
    pinctrl-names = "default";
    pinctrl-0 = <&myi2c1_pins_default>;
    status = "okay";

    clock-frequency = <100000>;

    tlv320aic3106: tlv320aic3106@1b {
            #sound-dai-cells = <0>;
            compatible = "ti,tlv320aic3106";
            reg = <0x1b>;
            status = "okay";
    };
};

But at linux startup, it print these:

[   22.325608] 1-001b supply IOVDD not found, using dummy regulator
[   22.325700] 1-001b supply DVDD not found, using dummy regulator
[   22.325767] 1-001b supply AVDD not found, using dummy regulator
[   22.325829] 1-001b supply DRVDD not found, using dummy regulator
[   22.684430] tda998x 0-0070: found TDA19988
[   22.694103] tilcdc 4830e000.lcdc: bound 0-0070 (ops tda998x_ops [tda998x])
[   22.694551] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   22.694566] [drm] No driver support for vblank timestamp query.
[   22.695065] tilcdc 4830e000.lcdc: No connectors reported connected with modes
[   22.695095] [drm] Cannot find any crtc or sizes - going 1024x768
[   22.910334] Console: switching to colour frame buffer device 128x48
[   23.050278] tilcdc 4830e000.lcdc: fb0:  frame buffer device
[   23.050327] [drm] Initialized tilcdc 1.0.0 20121205 on minor 0
[   23.063003] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20
[   24.736640] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[   24.872303] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[   25.599729] asoc-simple-card sound: tlv320aic3x-hifi <-> 4803c000.mcasp mapping ok

As it shows, linux didnot get the right configuration of these :

IOVDD
DVDD
AVDD
DRVDD

Because I didnot know how to configure these.As in am335x evm's devicetree, it configure like these:

tlv320aic3106: tlv320aic3106@1b {
    #sound-dai-cells = <0>;
    compatible = "ti,tlv320aic3106";
    reg = <0x1b>;
    status = "okay";

    /* Regulators */
    AVDD-supply = <&vaux2_reg>;
    IOVDD-supply = <&vaux2_reg>;
    DRVDD-supply = <&vaux2_reg>;
    DVDD-supply = <&vbat>;
};

vaux2_reg: regulator@10 {
    regulator-always-on;
};

vbat: fixedregulator0 {
    compatible = "regulator-fixed";
    regulator-name = "vbat";
    regulator-min-microvolt = <5000000>;
    regulator-max-microvolt = <5000000>;
    regulator-boot-on;
};

 I've idea about regulator configuration in beaglebone with aic3106, How to configure regulators in devicetree?

Thanks.

Part Number: TMS320C6657

Tool/software: TI-RTOS

We are using the C6657 chip in our custom board. Our application written in C++ as to be run on both cores. each one of the cores is is running seperatly with no connection to the other core.

The code (for both cores) are running from the external DDR memory. My questions are regrding the heap and stack for each core.

1) II would like to create a two custom heaps mem for each core using HeapMem.Create. How do I call new and delete on these custom heaps?. Memory_alloc is good for buffers (sized in bytes) but i need to allocate and free complex objects. these objects types are defines as C++ classes.
In other words I would like to do:
MyClass* p = new MyClass; Were the a allocating is done from the proper custom heap mem.

2) Regarding the stack, I would like that each of the core will have is own stack memory. How to set these stack objects in the cfg file?

all the heaps and stacks memory regions should be placed in the DDR memory as well.

Thanks you

Eyal

Part Number: TMS320C6678

Hi,

I see that on the 6678 EVB, 312.5Mhz is used as SGMII clk.

I would like to use 250Mhz in a new design,

HW changes:  Bootconfig bits 9-8 SerDes Clock Mult need to change to  '01' instead of '10'.

Q: Do I also need to change the  Kernel? SGMII_SERDES_CGFPLL(MPY) ?

Q: Any other changes?

Q: Can you confirm 250Mhz was tested\used and works OK?

Q: Is the 312.5Mhz preferred in any way? 

Regards,

Amir 

Part Number: AM5726

Hi,

Do we have any Sitara which supports SDXC of SD I/F ? If we don't have, do we have a plan to support it on future device ?

I know that SDHC is already supported. How about SDXC ?

Thanks and regards,
Hideaki

Part Number: AM3358

Hi,

The customer met the same question as this post https://e2e.ti.com/support/processors/f/791/t/663379 . Please help follow.

도구 / 소프트웨어 :수필곡 스튜디오

nice to meet you.
I tried the TMS320F28335 after building it in CCS3.3.
I am debugging with a malfunction.

After building from CCS3.3 to development board
I want to check if the OUT file is properly inserted on the target board.

Can I save the OUT file on the development board to the PC?

I would like to know if there is such a feature in CCS 3.3.

Tool/software: Linux

Hi

I use "PROCESSOR_SDK_VISION_03_07_00_00"and, I wanted to build a new usecase.

I could read and show image by opencv and did the same things by draw2d.c.

I followed VisionSDK_UserGuide_BuildSystem.pdf to build usecase.

But I did't know what function or program could do that things.

Q1：Is any document for building new-usecase, or about read and show ?

Q2：Could someone show a brief process for this case ?

Part Number: TMS320C6748

hi,
    now, our board replace DDR by EMIFA SDRAM(0x4000 0000 0x5FFF FFFF 512M).
    so we have some problems:
        1.write image to flash by uart: normally,we use sfh_OMAPL138.exe .but then find that
    this way separate in two parts:trasmit image to DDR,copy image from DDR to flash.how about EMIFA SDRAM?
        2.if system can bootup by  copy flash image to EMIFA SDRAM? normally,compiler use XXX.cmd ,can see:
            MEMORY
        {
          DRAM        org=0xC0000000 len=0x04000000 /* SDRAM */
          L2RAM       org=0x11800000 len=0x00040000 /* DSP L2RAM */  
          SHARED_RAM  org=0x80000000 len=0x00020000 /* DDR for program */
          AEMIF       org=0x60000000 len=0x02000000 /* AEMIF CS2 region */
          AEMIF_CS3   org=0x62000000 len=0x02000000 /* AEMIF CS3 region */
        }
        can we add EMIFA SDRAM by this?:
        {
            AEMIF_CS0    org=0x40000000 len=0x04000000 /* EMIFA SDRAM */
        }

please reply as soon as prossble,  thank you very mush!

Part Number: PROCESSOR-SDK-AM57X

Tool/software: Linux

I want to test jailhouse(http://software-dl.ti.com/processor-sdk-linux/esd/docs/05_00_00_15/linux/Foundational_Components_Virtualization.html