Part Number: TMDXIDK57X-LCD

Hello every one,

I have an AM5728 IDK and a camera, my final goal is to capture an image and do some processing using imglib in ti-rtos, but for now, I'm just trying to run ti example on my IDK. These were my steps to run the VPS loopback example:

I compiled the loopback example successfully and there is a file, named vps_examples_loopback_a15_0_release.xa15fg  in C:\ti\pdk_am57xx_1_0_15\packages\ti\binary\vps_examples_loopback\bin\idkAM572x  directory. this is my camera (that I can't see 2659 label on it! that's why I put its picture here):

I have an empty microSD Card in fat32 format in my IDK. after I lunch my *.xa15fg file on my IDK, it gives me this:

and it stops there. then I tried to use *.xa15fg file provided by lding ,here , and it gives me this:

LOOPBACK_APP: Sample Application - STARTS !!!
*** VPDMA Firmware Loading... ***
VPDMA Firmware Address = 0xa0011fc0
VPDMA Load Address     = 0x4897d004
VPDMA Firmware Version = 0x4d0001b8
VPDMA List Busy Status = 0x00000000
*** VPDMA Firmware Load Success ***

*** VPDMA Firmware Loading... ***
VPDMA Firmware Address = 0xa0011fc0
VPDMA Load Address     = 0x4899d004
VPDMA Firmware Version = 0x4d0001b8
VPDMA List Busy Status = 0x00000000
*** VPDMA Firmware Load Success ***

*** VPDMA Firmware Loading... ***
VPDMA Firmware Address = 0xa0011fc0
VPDMA Load Address     = 0x489bd004
VPDMA Firmware Version = 0x4d0001b8
VPDMA List Busy Status = 0x00000000
*** VPDMA Firmware Load Success ***

*** VPDMA Firmware Loading... ***
VPDMA Firmware Address = 0xa0011fc0
VPDMA Load Address     = 0x489dd004
VPDMA Firmware Version = 0x4d0001b8
VPDMA List Busy Status = 0x00000000
*** VPDMA Firmware Load Success ***


 Build time            : [10:29:27 Jun 19 2019]
 FVID2 Version         : [FVID_02_01_00_01]
 BSP Version           : [PDK_01_10_00_xx]
 Platform              : [EVM]
 SOC                   : [AM572X]
 SOC Revision          : [ES2.0]
 FT Revision           : [12]
 Package               : [UNKNOWN]
 Core                  : [A15]
 Board Detected        : [AM57XX IDK EVM]
 EEPROM Base Board Name: [AM572IDK]
 Base Board Revision   : [UNKNOWN]
 Daughter Card Revision: [REV A]

LOOPBACK_APP: LpbkApp_init() - DONE !!!

--------------------------------------
Select test to run as per below table:
--------------------------------------

  0: OV1063x            -> VIP1_S0_PORTA (1280x720@30FPS)  -> BGR888      -> DSS Video1 -> DPI1 LCD
  1: OV1063x            -> VIP1_S0_PORTA (1280x720@30FPS)  -> ARGB32_8888 -> DSS Video1 -> DPI1 LCD
  2: OV1063x            -> VIP1_S0_PORTA (1280x720@30FPS)  -> YUV420SP    -> DSS Video1 -> DPI1 LCD
  3: OV1063x            -> VIP1_S0_PORTA (1280x720@30FPS)  -> DSS Video1 -> DPI1 LCD
  4: LI OV1063x         -> VIP1_S0_PORTA (1280x720@30FPS)  -> DSS Video1 -> DPI1 LCD
  5: SII9127            -> VIP1_S0_PORTA (1280x720@30FPS)  -> DSS Video1 -> DPI1 LCD
  6: SII9127            -> VIP1_S0_PORTA (1920x1080@60FPS) -> DSS Video1 -> DPI1 LCD
  7: ADV7611            -> VIP1_S0_PORTA (1920x1080@60FPS) -> DSS Video1 -> DPI1 LCD
  8: MULDESCAM1_OV1063x -> VIP1_S0_PORTA (1280x720@30FPS)  -> DSS Video1 -> DPI1 LCD
  9: MULDESCAM2_OV1063x -> VIP1_S1_PORTA (1280x720@30FPS)  -> DSS Video1 -> DPI1 LCD
 10: MULDESCAM3_OV1063x -> VIP2_S0_PORTA (1280x720@30FPS)  -> DSS Video1 -> DPI1 LCD
 11: MULDESCAM4_OV1063x -> VIP3_S0_PORTA (1280x720@30FPS)  -> DSS Video1 -> DPI1 LCD
 12: MULDESCAM5_OV1063x -> VIP2_S1_PORTB (1280x720@30FPS)  -> DSS Video1 -> DPI1 LCD
 13: MULDESCAM6_OV1063x -> VIP3_S1_PORTA (1280x720@30FPS)  -> DSS Video1 -> DPI1 LCD
 14: MULDESCAM1to4 -> VIP -> DSS Video1 -> DPI1 LCD
 15: MULDESCAM1to6      -> VIP                             -> DSS Video1 -> DPI1 LCD
 16: MULDESCAM1to4      -> VIP                             -> DSS Video1 -> DPI1 HDMI 1920x1080@60FPS
 17: MULDESCAM1(GW4200_IMX290@24FPS)      -> VIP           -> DSS Video1 -> DPI1 HDMI 1920x1080@60FPS
 18: MULDESCAM1to6      -> VIP                             -> DSS Video1 -> DPI1 HDMI 1920x1080@60FPS
 19: TVP5158            -> VIP1_S0_PORTA (PAL)             -> DSS Video1 -> DPI1 LCD
 20: OV1063x            -> VIP1_S0_PORTA (1280x720@30FPS)  -> DSS Video1 -> DPI1 HDMI 1920x1080@60FPS
 21: Virtio:               VIP1_S0_PORTA                   -> DSS Video1 -> DPI1 @ D1 (720x480), YUYV422I
 22: OV2659            -> VIP2_S1_PORTB (1280x720@30FPS)  -> YUYV422      -> DSS Video1 -> DPI1 LCD
 23: OV1063x            -> VIP2_S0_PORTA (1280x720@30FPS)  -> YUYV422      -> DSS Video1 -> DPI1 LCD
 24: Auto Run

100: EXIT

Enter Test to Run (in UART console):
22
22
LOOPBACK_APP: CAPT HANDLES 1: DISP HANDLES 1: MODE 0004 : RUN COUNT 30: OUTPUT:0 !!
saveRaw(0, 0x81700000, "D:\\loopbackOption22Inst7Ch0Str0_uyvy422_prog_packed_1920_1080.tigf", 6220800, 32, false);
LOOPBACK_APP: VIP 7: VID SENSOR 1210 (0x30): 9090:0000:9090
LOOPBACK_APP: Capture create complete!!
Display Create Status: VENC Standard: CUSTOM, Width: 1920, Height: 1200
Display Create Status: Minimum Number of Buffers to Prime: 1
LOOPBACK_APP: Display create complete!!
LOOPBACK_APP: Starting loopback ... !!!
LOOPBACK_APP: Loopback in progress ... DO NOT HALT !!!
LOOPBACK_APP: Stopping loopback ... DONE !!!

 Execution Statistics
 ====================

 Execution time    : 50.998 s
 Total field Count : 0 (0 fields/sec)
 Avg CPU Load      : 0 %

 Capture Instance 7 Statistics
 ==============================
 Capture Inst 7 Status: Number of request queued  : 6
 Capture Inst 7 Status: Number of request dequeued: 0
 Capture Inst 7 Status: Overflow Count            : 0

    CH    |     Q      DQ     Total   Top     Bot    Total  Top    Bot   Min/Max     Min/Max   Dropped  Repeat   Fid   Desc
 (I/S/CH) |   Count   Count  Fields  Fields  Fields   FPS   FPS    FPS    Width       Height   Frames   Frames  Repeat Error
 ---------------------------------------------------------------------------------------------------------------------------
  07.0.00 |       6       0       0       0       0      0     0     0     0/0         0/0           0       0       0     0

 Display Instance 0 Statistics
 ==============================
 Display Inst 0 Status: Number of request queued  : 1
 Display Inst 0 Status: Number of request dequeued: 0
 Display Inst 0 Status: Displayed frame count     : 1798
 Display Inst 0 Status: Frame repeat count        : 1798

 Dispaly Controller Error Status
 ==============================
 LCD1 SyncLost count          : 0
 LCD2 SyncLost2 count         : 0
 LCD3 SyncLost3 count         : 0
 TV SyncLost count            : 0
 OCP Error count              : 0


LOOPBACK_APP: Display delete complete!!
LOOPBACK_APP: Capture delete complete!!

 69679: LOAD: CPU: 1%, HWI: 0%, SWI:0%

which seems to be correct, but I can't see anything on my LCD, the moment I press 22, my LCD blinks once, but nothing appears on it. Does any one have any idea?

P.S: I don't know whether the example stores the images on the sd card or not, but when I exit the sd card, it's still empty.

B.R,

Alex.

Part Number: TDA2EXEVM

Can you give me some reference about how to modify  ssdJacintoNetV2 network  in caffe-jacinto to achieve road lines detection?

Part Number: TMS320C6678

Hi,

Some contradictions regarding the pull level for:

1. DDRRESET (#E11) same as DDR control 39.2Ohm to 0.75V VTT or 4.7K to VCC1V5?

2. DDRSLRATE0\1 (#G27, #H27) pull to VCC1V8 or VCC1V5?

Amir

Part Number: 66AK2G12

Hello,

Could you lease clarify what is the main purpose of having option to have an internal Pull up/down on DQS lines.

We are working on DDR3 validation on our prototypes and based on measurements seems that when on-die pull up/downs are active timing margins are affected.

I used to see that DQS lines are "tri-state" (high impedance on both ends) when neither side is transmitting.

Thank you.

Regards

Juraj 

Part Number: OMAP-L138

Hi team,

My customer is testing OMAP-L138 456MHz version. Before OMAP-L138, they used C6746 and the PMIC TPS650061. For OMAP-L138 456MHz version, they want to keep using TPS650061 PMIC. So we need to confirm below 2 points with you. Thanks.

1. What power rail does OMAP-L138 456MHz version need? TPS650061 can output 1.2V/1.8V/3.3V. Can TPS650061 power rail be suitable for OMAP-L138 456MHz version? It seems in below document, it said 456MHz version CVDD, RVDD need to be 1.3V. Can you help check?

http://www.ti.com.cn/cn/lit/ug/slvu733/slvu733.pdf

2. What’s the power rail current consumption of OMAP-L138 456MHz version? Can  TPS650061 3.3V@300mA, 1.8V@300mA, 1.2V@1A current capacity satisfy 456MHz version power consumption?

Best regard,

Wayne

Part Number: PROCESSOR-SDK-AM57X

Tool/software: Code Composer Studio

Hello

I am using AM5728 CPU for development TI-RTOS application.

Sometimes my firmware doesn't load correctly and processor crashes or freezes on startup.

My working environment: Ubuntu 16.04.6 LTS x64, CCS 8.1.0, TI-RTOS SDK 06.00.

With regards,
Alex

Part Number: TMS320C6414T

For SPI port as a slave, in any mode, the data sheet defines the Dx valid delay from Clock as:

12P + 2.8 min, and 20P + 17 max

For this parameter definition, are the constant terms (2.8, 17) dependent on temperature and die variations only? If not what are the dependencies?

For this parameter definition, are the "P" terms (12P , 20P), this variation seems to be a function of DSP timing with the SPI port, is this variation ( 2 - 20) seen for all SPI configurations? Or is it tighter in some configurations

As an alternative to CPU DMIPS to do the following, does TI have non-CPU performance benchmarks for the following algorithms? 

• Object/lane detection

• Road boundary detection

• Free space detection      

John 

Part Number: PROCESSOR-SDK-AM437X

Working with a custom board, based on the sk-evm.  I noticed the following error messages and can't figure out what is up:

0.486123] pinctrl-single 44e10800.pinmux: pin PIN110 already requested by 44e10800.pinmux; cannot claim for gpios
[ 0.496720] pinctrl-single 44e10800.pinmux: pin-110 (gpios) status -22
[ 0.503344] pinctrl-single 44e10800.pinmux: could not request pin 110 (PIN110) from group gpio_pins_default on device pinctrl-single
[ 0.515437] omap_gpio gpios: Error applying setting, reverse things back

Earlier I saw a message like this and found a pin wrongly assigned to another use.  In this case I can't figure out what is going on.   I assumed that PIN110 was gpio3_14  which is assigned to an led that is operational.  I removed this pin from the DTS and still see the issue.  I am beginning to think that that was a wild goose chase.

Does anyone have any pointers on how to diagnose?  

(I am submitting this generic question on behalf of a customer)

Which displays or monitors are supported via Display Port (DP)?

From a TI colleague, I hear that the driver for (1) Linux and the driver for (2) TI RTOS is different, so display support may differ.

Can someone inform me of the manufacturer and the model number of the display?

If you are reading this, using the TI DRA829 EVM and a DP-supported monitor, won't you please update the thread with your display manufacturer and model #?

Thank you,

Jason

(I am asking this question on behalf of a customer)

I am unable to create an SD card using pre-built images provided with the TI Linux release
Command used as instructed in Linux SD card creation guide document section 1.1.1.2.

sudo ./bin/mksdboot.sh --device /dev/sdb --sdk /home/myname/ti-processor-sdk-linux-automotive-j7-evm-06_00_00_00 

I get the following errors:

cp: cannot stat '/home/myname/ti-processor-sdk-linux-automotive-j7-evm-06_00_00_00/board-support/prebuilt-images/MLO': No such file or directory

ERROR: executing cp /home/myname/ti-processor-sdk-linux-automotive-j7-evm-06_00_00_00/board-support/prebuilt-images/MLO /tmp/sdk/24337/boot/

Can anyone suggest a solution?

Part Number: TDA2EVM5777

Dear sir,

I also met this problem.

I have tried the methods mentioned in the discussions, except using git bash.

Is there any way to fix it without using git bash?

VSDK ver. :  03_07_00_00

OS: windows 7

Thank you,

Gary

Part Number: AM3352

     I make a am335x board , boot start by spiflash.
     now i wang to connect emmc by mmc1, so i amend uboot code
     first step: mmc dev 1
     second step :mmcinfo   

      now system crash first step

i amend mux.c

static struct module_pin_mux mmc1_pin_mux[] = {

        {OFFSET(gpmc_ad11), (MODE(2) | RXACTIVE | PULLUP_EN)},        /* MMC1_DAT3 */
        {OFFSET(gpmc_ad10), (MODE(2) | RXACTIVE | PULLUP_EN)},        /* MMC1_DAT2 */
        {OFFSET(gpmc_ad9), (MODE(2) | RXACTIVE | PULLUP_EN)},        /* MMC1_DAT1 */
        {OFFSET(gpmc_ad8), (MODE(2) | RXACTIVE | PULLUP_EN)},        /* MMC1_DAT0 */
        {OFFSET(gpmc_csn1), (MODE(2) | RXACTIVE | PULLUP_EN)},        /* MMC1_CLK */
        {OFFSET(gpmc_csn2), (MODE(2) | RXACTIVE | PULLUP_EN)},        /* MMC1_CMD */
        {OFFSET(gpmc_csn0), (MODE(7) | RXACTIVE | PULLUP_EN)},        /* MMC1_WP */
        {OFFSET(gpmc_advn_ale), (MODE(7) | RXACTIVE | PULLUP_EN)},        /* MMC1_CD */
        {OFFSET(mcasp0_aclkx), (MODE(6) | RXACTIVE| PULLUP_EN)},
        {-1},
};（warning! there  is GPMC_AD8-9-10-11）

configure_module_pin_mux(mmc1_pin_mux);

 i found system crash at mmc_init_setup()      ,    crash when to read regist......
static int mmc_init_setup(struct mmc *mmc)
{
        struct hsmmc *mmc_base = (struct hsmmc *)mmc->priv;
        unsigned int reg_val;
        unsigned int dsor;
        ulong start;
        mmc_board_init(mmc);
            writel(readl(&mmc_base->sysconfig) | MMC_SOFTRESET,
                &mmc_base->sysconfig);
        start = get_timer(0);
        while ((readl(&mmc_base->sysstatus) & RESETDONE) == 0) {
                if (get_timer(0) - start > MAX_RETRY_MS) {
                        printf("%s: timedout waiting for cc2!\n", __func__);
                        return TIMEOUT;
                }
        }。。。。。。。

。。。。。。。。。。。。

ti-sdk-am335x-evm-06.00.00.00-Linux-x86-Install.bin

Dear TI experts,

Referring to http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_Kernel_Drivers.html#pcie-end-point

I  modified below DTS files. But I unable to enable pcie EP mode.

vim arch/arm/boot/dts/dra7-evm-common.dtsi
vim arch/arm/boot/dts/dra72-evm-common.dtsi
vim arch/arm/boot/dts/am572x-idk-common.dtsi
vim arch/arm64/boot/dts/ti/k3-am654-pcie-usb3.dtso
vim arch/arm64/boot/dts/ti/k3-am654-pcie-usb2.dtso
vim arch/arm/boot/dts/dra7.dtsi
vim arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi:

Boot log:

[ 0.701033] pinctrl-single 4a003400.pinmux: 282 pins at pa fc003400 size 1128
[ 0.704478] dra7-pcie 51000000.pcie: Linked as a consumer to phy-4a094000.pciephy.3
[ 0.704844] OF: PCI: host bridge /ocp/axi@0/pcie@51000000 ranges:
[ 0.704882] OF: PCI: IO 0x20003000..0x20012fff -> 0x00000000
[ 0.704905] OF: PCI: MEM 0x20013000..0x2fffffff -> 0x20013000
[ 1.705203] dra7-pcie 51000000.pcie: phy link never came up
[ 1.705342] dra7-pcie 51000000.pcie: PCI host bridge to bus 0000:00
[ 1.705356] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 1.705368] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
[ 1.705380] pci_bus 0000:00: root bus resource [mem 0x20013000-0x2fffffff]
[ 1.705696] PCI: bus0: Fast back to back transfers disabled
[ 1.705786] PCI: bus1: Fast back to back transfers enabled
[ 1.705825] pci 0000:00:00.0: BAR 0: assigned [mem 0x20100000-0x201fffff 64bit]
[ 1.705844] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[ 1.706167] pcieport 0000:00:00.0: Signaling PME with IRQ 174
[ 1.706291] pcieport 0000:00:00.0: AER enabled with IRQ 174

There is no pcie_epc
am57xevm:/ # ls /sys/class/pci_epc/
am57xevm:/ #

Thanks in advance!

B.R.

Part Number: AM5728

Customer trying to verifying status of PCIe link-up between AM57x EVM and PCIe NIC Card 

Could you verify which message should they use check to see the PCIe Gen 2 link status ?

1. Just running “lspci” command, can they verify the PCIe Gen 2 link-up status ?

1. Using lspci -vvv do they verify check “LinkCap” or “LinkCtl2” status as way to confirm link status?

Part Number: TMS320C5504

Hi,

Can you please mention the maximum junction temperature supported by TMS320C5504 IC. I can see from the datasheet only the maximum case temperature.

Regards,

Dixit

Hello,

we are struggeling to add a UART driver to our project. here are some basic information:

- the project is based on the PRU-ICSS-Profinet_Slave_01.00.03.04 sample application on the AM335x ICE Board V2.

- we want to use the UART which is connected to the DB9 connector (the same which is used for PROFIBUS slave in other projects)

- we don't want to change the standard IO Uart from 0 to 1, because we don't need printf on the RS485, we want to implement a different protocol.

- I have searched for the UART samples, but they all are showing how to use the standard I/O driver.

is there any documentation or sample code how to add an UART to the application ? it seems that the UARTs are already added in the config file, but it seems that the project
was not based on Starterware (there is no Board_Init function in main), so the standard sample code is not working.

the UART should use the DMA because the frames can be longer. but a first hint how to start would be great.

Thank's in advance,

Dirk

Part Number: TMDSCSK8127

I work with TMDSCSK8127board

Using DM8127 IPNC RDK Release (v3.9.1)

I load to NAND the MLO, u-boot.img, uImage, dm8127-csk.dtb, ubifs_csk_DM8127_FULL_FEATURE.bin from

 /ipnc_rdk-3.9.1/Source/ipnc_rdk/binaries/DM8127 folder

Load from NAND and kernel cannot start:

U-Boot SPL 2016.05 (Aug 05 2019 - 14:46:32)

Trying to boot from NAND


U-Boot 2016.05 (Aug 05 2019 - 14:46:32 +0300)

I2C:   ready
DRAM:  1 GiB
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0
Net:   cpsw
Hit any key to stop autoboot:  0
Booting from nand ...

NAND read: device 0 offset 0x440000, size 0x600000
 6291456 bytes read: OK

NAND read: device 0 offset 0xca40000, size 0x40000
 262144 bytes read: OK
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-4.4.12
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2666984 Bytes = 2.5 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
   Booting using the fdt blob at 0x80f80000
   Loading Kernel Image ... OK
   Loading Device Tree to 8146e000, end 8147f5d1 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.12 (root@gleb-System-Product-Name) (gcc version 5.3.1 20160113 (Linaro 9
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: DM8127 CSK
[    0.000000] bootconsole [earlycon0] enabled
[    0.000000] omap_barrier_reserve_memblock():Reserving DRAM area @ addr = 0x84e00000          size = 1s
[    0.000000] cma: Reserved 24 MiB at 0x83400000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] TI81XX: Map 0x84e00000 to 0xfe500000 for dram barrier
[    0.000000] TI81XX: Map 0x40300000 to 0xfe600000 for sram barrier

U-Boot SPL 2016.05 (Aug 05 2019 - 14:46:32)
Trying to boot from NAND


U-Boot 2016.05 (Aug 05 2019 - 14:46:32 +0300)

I2C:   ready
DRAM:  1 GiB
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0
Net:   cpsw
Hit any key to stop autoboot:  0
Booting from nand ...

NAND read: device 0 offset 0x440000, size 0x600000
 6291456 bytes read: OK

NAND read: device 0 offset 0xca40000, size 0x40000
 262144 bytes read: OK
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-4.4.12
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2666984 Bytes = 2.5 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
   Booting using the fdt blob at 0x80f80000
   Loading Kernel Image ... OK
   Loading Device Tree to 8146e000, end 8147f5d1 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.12 (root@gleb-System-Product-Name) (gcc version 5.3.1 20160113 (Linaro 9
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: DM8127 CSK
[    0.000000] bootconsole [earlycon0] enabled
[    0.000000] omap_barrier_reserve_memblock():Reserving DRAM area @ addr = 0x84e00000          size = 1s
[    0.000000] cma: Reserved 24 MiB at 0x83400000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] TI81XX: Map 0x84e00000 to 0xfe500000 for dram barrier
[    0.000000] TI81XX: Map 0x40300000 to 0xfe600000 for sram barrier

U-Boot SPL 2016.05 (Aug 05 2019 - 14:46:32)
Trying to boot from NAND


U-Boot 2016.05 (Aug 05 2019 - 14:46:32 +0300)

I2C:   ready
DRAM:  1 GiB
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0
Net:   cpsw
Hit any key to stop autoboot:  2

What can i do with this problem?

There is u-boot config:

DM8127-CSK# printenv
arch=arm
baudrate=115200
board=dm8127
board_name=dm8127
bootargs=console=ttyS0,115200n8 cmemk.phys_start=0x85000000 cmemk.phys_end=0x89000000 cmemk.allowOverlap1
bootcmd=csk_ff_init 1;run nandboot
bootdelay=3
bootfile=uImage
console=ttyS0,115200n8
cpu=armv7
ethact=cpsw
ethaddr=d4:f5:13:99:2e:54
fdt_high=0x81480000
fdtaddr=0x80F80000
fdtcontroladdr=bfe4cdb8
fdtfile=dm8127-csk.dtb
importbootenv=echo Importing environment from mmc ...; env import -t $loadaddr $filesize
ipaddr=192.168.1.68
loadaddr=0x80200000
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
loaddtbimage=fatload mmc ${mmcdev} ${fdtaddr} ${fdtfile}
loadramdisk=fatload mmc ${mmcdev} ${rdaddr} ramdisk.gz
loaduimage=ext2load mmc ${mmcdev}:2 ${loadaddr} ${bootfile}
loaduimagefat=fatload mmc ${mmcdev} ${loadaddr} ${bootfile}
mem=80M
mmcargs=setenv bootargs console=${console} root=${mmcroot} mem=${mem} vram=${vram} ${optargs}
mmcboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};echo Booting from m;
mmcdev=0
mmcroot=/dev/mmcblk0p2 rw
mtddevname=NAND.SPL
mtddevnum=0
mtdids=nand0=nand.0
mtdparts=mtdparts=nand.0:128k(NAND.SPL),4m(NAND.u-boot),128k(NAND.u-boot-env),6m(NAND.kernel),192m(NAND.)
nandargs=setenv bootargs console=${console} ${optargs} mem=${mem} vram=${vram} root=${nandroot} rootfsty}
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} NAND.kernel; nand read ${fdtadd}
nandroot=ubi0:rootfs rw ubi.mtd=NAND.file-system,2048
nandrootfstype=ubifs rootwait=1
optargs=cmemk.phys_start=0x85000000 cmemk.phys_end=0x89000000 cmemk.allowOverlap=1 notifyk.vpssm3_sva=0xk
partition=nand0,0
ramargs=setenv bootargs console=${console} ${optargs} root=${ramroot} rootfstype=${ramrootfstype}
ramboot=echo Booting from ramdisk ...; run ramargs; bootm ${loadaddr}
ramroot=/dev/ram0 rw ramdisk_size=65536 initrd=${rdaddr},64M
ramrootfstype=ext2
rdaddr=0x81000000
serverip=192.168.1.30
soc=am33xx
stderr=serial
stdin=serial
stdout=serial
vendor=ti
ver=U-Boot 2016.05 (Aug 05 2019 - 14:46:32 +0300)
vram=4M

Environment size: 2535/131068 bytes

Part Number: PROCESSOR-SDK-AM57X

Tool/software: Code Composer Studio

1. When using opengl to develop 3D projects, however, gpu does not support opencl, so I need to carry out a lot of calculations (about 80M floating point Numbers), and then transfer each calculation result to gpu, which consumes a lot of CPU resources to calculate and transfer data to gpu. Therefore, I plan to use DSP for calculation and transfer the calculation result to gpu. Can DSP and A15 or DSP and gpu use DMA to transfer data?
2. How efficient is the communication between DSP and A15 through opencl?Does heavy handling of big data consume CPU?

3. Am5728 has dual DSP, can you control different DSP to do different work? For example, DSP1 carries out opencl transportation, DSP2 runs Big Data Ipc, or DSP2 also USES opencl to carry out calculation of another project

Part Number: AMIC110

Hi,

I want to use the NDK TCP/IP stack for the EoE(EtherCAT) communication. I did not find any way of using EoE with the NDK stack in the documents.

Can you guide me on how to use the NDK stack for EoE communication?