Tool/software: Linux

AM4378: 4.14.79-rt47-LCKJ-PLC-4.0.0 #13 PREEMPT RT Tue Jul 9 12:47:20 CST 2019 armv7l GNU/Linux

[ 51.352186] usb 1-1: USB disconnect, device number 2
[ 55.156232] usb 1-1: new high-speed USB device number 3 using xhci-hcd
[ 55.343812] usb 1-1: New USB device found, idVendor=058f, idProduct=6387
[ 55.351182] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 55.358891] usb 1-1: Product: DataTraveler 2.0
[ 55.363593] usb 1-1: Manufacturer: Kingston
[ 55.368154] usb 1-1: SerialNumber: F6EFF7AA
[ 55.375598] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 55.388176] scsi host0: usb-storage 1-1:1.0
[ 56.408233] scsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 8.07 PQ: 0 ANSI: 4
[ 56.410698] sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
[ 56.410718] sd 0:0:0:0: [sda] 1 512-byte logical blocks: (512 B/512 B)
[ 56.410723] sd 0:0:0:0: [sda] 0-byte physical blocks
[ 56.411115] sd 0:0:0:0: [sda] Write Protect is off
[ 56.411524] sd 0:0:0:0: [sda] Asking for cache data failed
[ 56.411530] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 56.414049] sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
[ 56.486754] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 56.486765] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current]
[ 56.486770] sd 0:0:0:0: [sda] tag#0 ASC=0x14 ASCQ=0x0
[ 56.486781] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00
[ 56.486788] print_req_error: critical medium error, dev sda, sector 0
[ 56.574430] Buffer I/O error on dev sda, logical block 0, async page read
[ 56.656692] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 56.656702] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current]
[ 56.656708] sd 0:0:0:0: [sda] tag#0 ASC=0x14 ASCQ=0x0
[ 56.656717] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00
[ 56.656724] print_req_error: critical medium error, dev sda, sector 0
[ 56.692277] Buffer I/O error on dev sda, logical block 0, async page read
[ 56.699590] sda: unable to read partition table
[ 56.709629] sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
[ 56.710352] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 56.836745] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 56.836756] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current]
[ 56.836761] sd 0:0:0:0: [sda] tag#0 ASC=0x14 ASCQ=0x0
[ 56.836771] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00
[ 56.836779] print_req_error: critical medium error, dev sda, sector 0
[ 56.884952] FAT-fs (sda): unable to read boot sector
[ 60.405601] usb 1-1: USB disconnect, device number 3

Part Number:AM3352

Hi champs !

I'm following up the thread https://e2e.ti.com/support/processors/f/791/p/794448/2960719#2960719  on which we came out with the conclusion that AM3352 is suitable to show video 1920x1080 30fps 24bpp .

Following your suggestion I tested this on a BBB using Video found on the Internet ( almost MP4 ) .

Results are not so encuraging, MPU is overloaded because of  MP4 deconding and Color Spase conversion ( YUV to RGB )  , audio decoding  consume MIPS as well .

This is limiting the max peformances I personally achieved to 1280x720 24fps with audio glitches  with a MP4 video .

I'm using mplayer  on latest BBB image :

mplayer -ao alsa -vo fbdev2 -cache 8192 -zoom -x 1280 -y 720 1280.mp4

Of course I tested  different video with different coding, I tried as well to convert the video i a raw-rgb using :

ffmpeg -i input.ext -vcodec rawvideo -pix_fmt rgb24 -an output.rgb

but the output file is so big that needs Storage well larger than what suitable for the application.

QUESTIONS for you :

- Is there any suggested video format to be used to let AM3352 to smoothly play a video 1080p ? if yes can you support me converting the video I do have using ffmpeg ?

- if AM335x is not suitable because of decoding and color translation effort, what could be the best SITARA option then ?

Thank you,

Paolo

Tool/software: Linux

Hi,

     We are getting "unrecoverable ECC error" in kernel with 8-Bit ECC in both U-Boot and Kernel. We are using DRA71X board and SDK is 3.01. When i checked for the ECC values in OOB area in U-Boot, its coming out to be fine. Kindly help us asap.

thanks,

Harish.

Part Number:TDA2P-ACD

Tool/software: Linux

Vision SDK 03.06.00

A15 OS : Linux

I want to add new driver module(.ko) in Linux.

I added source code in kernel. and I modified Kconfig and Makefile.

After booing is completed, I can insert driver module(.ko) using insmod. 

But I want to probe it in booting time.

How do I can inser module in booting time?

Best Regards,

Jongyoun.

Part Number:AM6546

Tool/software: Linux

How are PRU pins  mapped to R30 and R31 registers ? 

Part Number:TMDSEVM6657

Tool/software: Code Composer Studio

Hi we are working on TMDSEVM6657LS. I have looked at http://processors.wiki.ti.com/index.php/File:C6657_directROM_Boot_example.zip example.

I need more information on RBL and the setup for ccs V9.1.0. we dont want to use the EEPROM  we want only nor flash boot. 

Thanks

Bhaskar  

Part Number:AM3352

Tool/software: Linux

Hi,

I'm using AM3352 based custom board and TI-SDK linux in my development. To configure the pins according to the custom hardware, we need to generate dtsi & dts files and finally dtb should be given as input to the kernel. As it is suggested in TI site, I had downloaded PinMux Tool (version: 4.0.1531) and trying to do the job. In the meantime, I've observed that the tool generates 4 output files:

1. am335x_pinmux.h

2. am335x_pinmux_data.c

3. devicetree.dtsi

4. PinmuxConfigSummary.csv

Among those, I could not find the dts file. Could you please help me how to generate the dts file? 

Looking forward for your quick reponse.

Regards,

Srikanth Vemula. 

Part Number:AM5718

Tool/software: Linux

Hii All,

We are working with a custom board of AM5718.While booting from SD card,u-boot works fine but Linux hangs after printing the followings,

mmc0: error -110 whilst initialising SD card
[    3.822058] mmc1: new DDR MMC card at address 0001
[    3.827212] mmcblk1: mmc1:0001 R1J57L 27.5 GiB
[    3.831950] mmcblk1boot0: mmc1:0001 R1J57L partition 1 16.0 MiB
[    3.838053] mmcblk1boot1: mmc1:0001 R1J57L partition 2 16.0 MiB
[    3.844255] mmcblk1rpmb: mmc1:0001 R1J57L partition 3 128 KiB
[    3.954611] mmc0: error -110 whilst initialising SD card
[    4.154963] mmc0: error -110 whilst initialising SD card
[    4.560969] [drm] Cannot find any crtc or sizes

NOTE :

=> mmc list
OMAP SD/MMC: 0
OMAP SD/MMC: 1 (eMMC)

(We want to boot from SD card only)

Can anybody please provide any solution for this ?

Thanks and regards

Arpita Jena

Part Number:AM3358

Tool/software: Linux

Hi all,

I want to evaluate a wifi-module with the BeagleBoneBlack. In my devicetree-overlay I want to use the mmc3-interface as sdio and the uart4-interface as uart.

I insert the overlay in the /boot/uEnv.txt . After start up I see that the mmc3-pins and uart4-pins configuered as wanted. (verified by the tool 'show-pins'). The major issue is that the interface mmc3 is not activated/assigned to the pins. By this during startup the BB doesn't check if a module is connected to the mmc3 pins.

///////////////////////////////////////////////////////////////////////////////////////

/dts-v1/;

/ {
    part-number = "BLST-MMC3";
    version = "00A0";
    compatible = "ti,beaglebone", "ti,beaglebone-black";
    exclusive-use = "P8.33", "P8.35","P9.13", "P9.11", "uart4", "P8.18" , "P8.12" , "P8.10" , "P8.11" , "P8.16" , "P8.15" , "mmc3", "P8.07";

    fragment@0 {
        target = <0xffffffff>;

        __overlay__ {
            /* uart4 */
            P8_33_pinmux {
                status = "disabled";
            };

            P8_35_pinmux {
                status = "disabled";
            };
            P9_13_pinmux {
                status = "disabled";
            };
            P9_11_pinmux {
                status = "disabled";
            };
            
            
            
            /* mmc3 */
            P8_18_pinmux {
                status = "disabled";
            };

            P8_12_pinmux {
                status = "disabled";
            };

            P8_10_pinmux {
                status = "disabled";
            };

            P8_11_pinmux {
                status = "disabled";
            };

            P8_16_pinmux {
                status = "disabled";
            };

            P8_15_pinmux {
                status = "disabled";
            };
            
            /* Reset */
            P8_07_pinmux {
                status = "disabled";
            };


        };
    };



    fragment@1 {
        target = <0xffffffff>;

        __overlay__ {
            
            pinmux_mmc3_pins {
                pinctrl-single,pins = <
                0x88 0x33   /*mmc2_cmd */
                0x8c 0x33   /*mmc2_clk */  
                0x30 0x33   /*mmc2_dat0*/
                0x34 0x33   /*mmc2_dat1*/
                0x38 0x33   /*mmc2_dat2*/
                0x3c 0x33   /*mmc2_dat3*/
                >;
                linux,phandle = <0x2>;  
                phandle = <0x2>;        
            };

            pinmux_uart4_pins_default {
                pinctrl-single,pins = <0x70 0x2e 0x74 0xe 0xd0 0xe 0xd4 0x26>;
                linux,phandle = <0x1>;
                phandle = <0x1>;     
            };

            
            pinmux_reset_pd_pin {
                pinctrl-single,pins = <0x90 0x7f>;
                linux,phandle = <0x3>;
                phandle = <0x3>;
            };

        };
    };


    fragment@3 {
        target = <0xffffffff>;

        __overlay__ {
            compatible = "ti,omap4-hsmmc";
            dmas = <0xffffffff 0xc 0x0 0x1 0xffffffff 0xd 0x0 0x2>;
            dma-names = "tx", "rx";
            status = "okay";
            vmmc-supply = <0x2>;
            bus-width = <0x4>;
            non-removable;
            /* enable-sdio-wakeup;*/
            cap-power-off-card;
            broken-cd;
            ti,needs-special-reset;
            /* ti,needs-special-hs-handling;*/
            ti,hwmods = "mmc3";
            /* keep-power-in-suspend; */
            pinctrl-names = "default";              
            pinctrl-0 = <0x2>;                

            #address-cells = <0x1>;
            #size-cells = <0x0>;   
            
            
            sd8xxx-wlan@2 {
                compatible =  "marvell,sd8xxx";
                reg = <0x2>;
                interrupt-parent = <0xffffffff>;
                interrupts = <0x1d 0x1>;
            };
            
        };
    };

    fragment@4 {
        target = <0xffffffff>;

        __overlay__ {
            pinctrl-names = "default";
            pinctrl-0 = <0x1>;
            status = "okay";
        };
    };

    fragment@5 {
        target = <0xffffffff>;

        __overlay__ {
            pinctrl-names = "gpio_pu";
            pinctrl-0 = <0x3>;
            status = "okay";
        };
    };




    __symbols__ {
        mmc3_pins = "/fragment@1/__overlay__/pinmux_mmc3_pins";
        uart4_pins_default = "/fragment@1/__overlay__/pinmux_uart4_pins_default";
        wlcore = "/fragment@3/__overlay__/wlcore@2";

        reset_pin_default = "/fragment@1/__overlay__/pinmux_reset_pd_pin";

    };

    __fixups__ {

        ocp = "/fragment@0:target:0";
        am33xx_pinmux = "/fragment@1:target:0";
        mmc3 = "/fragment@3:target:0";
        edma_xbar = "/fragment@3/__overlay__:dmas:0", "/fragment@3/__overlay__:dmas:16";
        uart4 = "/fragment@4:target:0";
        P8_07_gpio_pu_pin = "/fragment@5:target:0";
    };

    __local_fixups__ {

        fragment@3 {

            __overlay__ {
                pinctrl-0 = <0x0>;
                };
        };
        
        fragment@4 {

            __overlay__ {
                pinctrl-0 = <0x0>;
            };
        };

        fragment@5 {

            __overlay__ {
                pinctrl-0 = <0x0>;
            };
        };

    };
};

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

I insert the content of overlay-file. I use the kernel 4.14.71-ti-r80

Maybe somebody can give my a hint , how to solve the problem?

Thank you and best regards,

Enno

Part Number:TDA2EVM5777

Tool/software: Linux

Hi,

While using our VSDK use-cases on TDA2x EVM, we are finding sometimes that if some crash occurs on a remote core, we need to reboot the board entirely to recover back to working state.

Hence, can you please provide the procedure to

a) power off

b) power on

the remote cores from linux console in A15.

Additionally, is there also an option to change the remote core binaries/firmware without rebooting the device?

if yes, Can you also provide the steps to load binaries to remote core.

We are specifically looking forward to deal with IPU, EVE and DSP.

Thanks in advance,

Best Regards,

Ranjith Bhide.

Part Number:AM3352

Tool/software: TI-RTOS

hello!

    In our hardware design, EDMA events are triggered by GPIO interrupts to read FPGA data.

What configuration do I need for GPIO interrupts and EDMA triggers?

the PDK version is pdk_am335x_1_0_13,

Here are my GPIO Settings:

GPIODirModeSet(SOC_GPIO_0_REGS,20,GPIO_DIR_INPUT);
GPIOIntTypeSet(SOC_GPIO_0_REGS, 20, GPIO_INT_TYPE_RISE_EDGE);
GPIOPinIntEnable(SOC_GPIO_0_REGS, GPIO_INT_LINE_1, 0);

GPIODirModeSet(SOC_GPIO_0_REGS,19,GPIO_DIR_INPUT);
GPIOIntTypeSet(SOC_GPIO_0_REGS, 19, GPIO_INT_TYPE_RISE_EDGE);
GPIOPinIntEnable(SOC_GPIO_0_REGS, GPIO_INT_LINE_1, 0);

How can I set an interrupt callback function for this method of setting GPIO interrupts?

If sysbios hwi to implement, hwi id should be set?

/* ================ config hwi for GPIO,used for EDMA ================ */
var Hwi = xdc.useModule('ti.sysbios.hal.Hwi');
var hwiParams = new Hwi.Params;
hwiParams.arg = 5;
Program.global.hwi0 = Hwi.create(id, '&AppDMAInt0CallbackFxn', hwiParams);

In addition, I know how to call set the Trigger mode to Manual,

if I want to set the Trigger mode to Event, what configuration do I need to do with EDMA?

BR!

Part Number:AMIC110

Hello,

If i dont use EIP stack provided by Molex and use another Open source EIP stack (available free download).

Does TI AMIC110 EIP solution works?

Regards,

VR

Part Number:TMS320C6654

Hi,

This issue is relative to ".

In short, more than half of DSPs on our custom boards couldn't access to DDR3.

Our team are still investigating the cause of DDR accessing problem.

In that, we noticed that there is sure way to succeed to access DSP to DDR3.

That is the power restoring of DVDD15.

After correct power sequence and correct reset sequence, NG board couldn't be loaded by.gel.

From then, DVDD15 having turning to low once and turning to active, NG board could be loaded by.gel.

we didn't vary other power supplying and POR & RESETFULL remained released.

As a next step, I burned the FW to nor flash on the NG board and tried to execute spi boot from nor flash.

This case, after correct power sequence and correct reset sequence, DSP didn't start to read the FW from nor flash,

however restoring the DVDD15, DSP started to read the FW and booting was successful.

From above, I want to know the state of the DSP when DSP couldn't start spi boot.

I recognize that DVDD15 is used for I/O voltage, but it seems that this power holds a very important role as boot.

I already confirmed boot manual from TI, but details were not described as the DSP's behavior when DVDD15 is supplied.

What does it happen when DVDD15 firstly wakes up, and what's the state of DSP then ? waiting? hunging?

regards,

Part Number:TMS320C6678

Hi Team,

Please help me answer the follow question, thank you so much.

It is stated in the data sheet of your product TMS320C6678ACYPA, TMS320C6674ACYPA
22.4 GFLOP/Core for Floating Point @ 1.4 GHz
20 GFLOP/Core for Floating Point @ 1.25 GHz
etc. are values of single-precision?
If the answer is single-precision, what frequence value does double precision have?
When converting to the number of FLOPS per chip, is it better to multiple the CORE number?

Best Regards,
Tom.Liu

Part Number:TMS320C6678

Hi Team,

Please help me answer the follow question, thank you so much.

For product TMS320C6678ACYPA25 and TMS320C6674ACYPA,
would you like to tell us what NAND Flash memory you have used or recommended when using NAND FLASH?
NUMONIX's NAND512R3A2DZA6E, which was installed in your Evaluation Modules, has been discontinued.
We are considering MICROON's MT29F2G08ABAEAH4-IT: E as a candidate, can it be used?

Best Regards,
Tom.Liu

Part Number:AM3352

Tool/software: Linux

Hi.

  I tested SDK5.03 with the AM335 SK EVM + USB Camera.

  And the external USB Cameras will not work.

  May you tell me what's the exact V4L2 command sets to make the External USB Camera working?

Log  is here:

root@am335x-evm:~# [ 92.364476] usb 2-1: USB disconnect, device number 2
[ 94.134348] usb 2-1: new high-speed USB device number 3 using musb-hdrc
[ 94.330467] usb 2-1: New USB device found, idVendor=045e, idProduct=075d
[ 94.337301] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 94.349490] usb 2-1: Product: Microsoft?LifeCam Cinema(TM)
[ 94.363436] usb 2-1: Manufacturer: Microsoft
[ 94.386099] uvcvideo: Found UVC 1.00 device Microsoft?LifeCam Cinema(TM) (045e:075d)
[ 94.425792] uvcvideo 2-1:1.0: Entity type for entity Extension 5 was not initialized!
[ 94.433764] uvcvideo 2-1:1.0: Entity type for entity Processing 4 was not initialized!
[ 94.476600] uvcvideo 2-1:1.0: Entity type for entity Selector 3 was not initialized!
[ 94.499760] uvcvideo 2-1:1.0: Entity type for entity Camera 1 was not initialized!
[ 94.531096] input: Microsoft?LifeCam Cinema(TM): as /devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1/usb2/2-1/2-1:1.0/input/input3
[ 147.574793] NET: Registered protocol family 15
[ 150.221524] Initializing XFRM netlink socket

BR Rio

Hi

I need your help to provide measurements on MobileNet x.x for our Sitara product.

First i need our best competitive device vs IMX8.

Then I need MobileNet x.x figures together with power consumption.

Would be very good to understand the performance and power consumption depending on what part of Sitara that is used to do the MobileNet benchmark (CPU, GPU or DSP)

Regards

/Anders

Part Number:TDA2SX

Tool/software: Linux

Hi,

I am using TDA2xx EVM having multides setup with OV10635 camera. Currently Camera is configured to 720p (1280x720) and 30fps frame rate.

I want to capture data for 600x400 resolution at 30fps.

For this, i have changed 720p to 600x400 resolution as mentioned below :
* Configured registers settings to 600x400.
* Changed width:600 and height:400 in Capture-link and Chains_common file.
* Used lvds_vip_single_camera_sgx_display use-case and changed the resolution to 600x400 including sgx capture path.

The output for the above configuration is a distorted image.
The camera is capturing data along with green lines displayed at the front (Video Movements and picture are visible at the backside).

To confirm the above changes made, i have put log to capture single frame binary data after FVID2_DEQUE. But the image received is distorted here also.
please see the attachment.

Question :
Could you please let me know the issue ?
Can i configure 720p to 600x400 ?
Have i missed out something ? Could you please guide me on this.

best regards,

ARUNKUMAR

Part Number:DRA76P

Tool/software: Linux

hi all,

now i have the virtual drm patchs for kernel version 4.4, but the kernel version of j6entry evm board is 4.14.

it is the newest than 4.4, so drm change a lot, if i port the virtual drm patchs for kernel 4.4 to 4.14, it occured 

so much compile error!

so i want to know where can i get the newest virtual drm patchs for kernel 4.14?

best regards!

Part Number:TDA3XEVM

Tool/software: TI-RTOS

Hello.
For a long time i work with VSDK305 and after the release of VSDK307 I found MPEG4 Encode link in release notes, which is interesting for me. I want to add it to a current VSDK305 project, because moving the whole project to VSDK307 seems not worth it for now.
I have successfully added link to VSDK305 and created a usecase, but appimage with it crushes right at the moment of MPEG4 plugin initialization on DSP.
What should i change to make it start working? I added mem_segment_definition_512mb.xs from VSDK307 to VSDK305 , because i think that some kind of memory problem causes the crashes, but i didn't see any differences. Should I also add the ti-cgt-c6000_8.2.4 compiler from VSDK307 or smth else?