Quantcast
Channel: Processors forum - Recent Threads
Viewing all 17527 articles
Browse latest View live
↧

Linux: Some questions about TDA2eg's video hardware codec

July 22, 2019, 9:57 pm
$
0
0

Tool/software: Linux

Dear all:

(1) It seems to the TDA2eg supports the H.264 when we checked the spec of TDA2ex-17 document. Does the TDA2eg use the 2D accelerator "GC320" as the video hardware codec ?

(2) According to the question (1), how can we use the hardware codec for TI's Linux platform if there is a video codec built-in ? Is there any driver or library included in TI's Linux pakcage ?

(3) Could you please give me the suggestion about the software if we want to deel with the video streaming in TDA2eg fo Linux OS ? How about the "vlc" or "mplayer" ? Could both of them use the TI's hardware codec for video acceleration ?

thanks ~

↧
Search

TCI6638K2K: TCI6638K2K

July 22, 2019, 10:08 pm
$
0
0

Part Number: TCI6638K2K

Hello,

We are using TCI6638K2K in one of the enodeB design.

It is required to use CPTS output as reference input to clock generator to generate 1PPS output signal.

The clock generator used is "disciplined Oscillator from Vectron". When a PPS -in is applied to The clock generator once locked with input generates high on the Lock signal and also PPS out.

The issue we are observing is, The clock generator is not locking with CPTS input, so it is not generating 1PPS output.

We have checked with Grandmaster PPS out fed to the clock generator. It is OK, the lock signal is going high, and also the 1PPS is generated the output of clock module.

The CPTS register values are given below,

Please find the register dump of cpts

[  231.577197] idver = 4e8a0105
[  231.580170] control = 5
[  231.582706] refclk = 0
[  231.585154] ts_push = 0
[  231.587694] ts_load_val = 0
[  231.587695] ts_load_en = 0
[  231.587697] ts_comp_val = a4b7b2fc
[  231.587698] ts_comp_length = 2ee0
[  231.587700] intstat_raw = 0
[  231.587701] intstat_masked = 0
[  231.587702] int_enable = 1
[  231.587703] event_pop = 0
[  231.587705] event_low = 85768b74
[  231.587706] event_high = 0
[  231.587707] event_high2 = 0

Pls let us know if we are missing something.

We have to solve this issue ASAP.

Kindly advice whether it is possible to use CPTS output as input to Clock module to generate 1PPS output signal.

Regards,

Sumathi

↧
↧

Linux/DRA756: dra756 custom board: The DCAN device does not work properly

July 22, 2019, 10:27 pm
$
0
0

Part Number: DRA756

Tool/software: Linux

Hi,

i have a problem with dcan module, the problem is that the Data can only be sent successfully in loopback mode.

No data can be received except data that is self-sending in loop mode.

the following code is the pin configuration of device tree.

	dcan1_pins_ds: pinmux_dcan1_pins_ds {
		pinctrl-single,pins = <
			DRA7XX_CORE_IOPAD(0x37d4, PIN_INPUT | MUX_MODE15) 	/* (Errata i893) dcan1_rx.dcan1_rx */
			DRA7XX_CORE_IOPAD(0x37d0, PIN_OUTPUT | MUX_MODE0) 	/* dcan1_tx.dcan1_tx */
		>;
	};

	dcan2_pins_ds: pinmux_dcan2_pins_ds {
		pinctrl-single,pins = <
			DRA7XX_CORE_IOPAD(0x37bc, PIN_INPUT | MUX_MODE15) 	/* (Errata i893) spi1_cs3.dcan2_rx */
			DRA7XX_CORE_IOPAD(0x37b8, PIN_OUTPUT | MUX_MODE4) 	/* spi1_cs2.dcan2_tx */
		>;
	};

following log tells what i did>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

root@dra7xx-evm:~# ./setup_can_bus.sh 0
[  103.055836] c_can_platform 4ae3c000.can can0: setting BTR=0504 BRPE=0000
2: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 10
    link/can  promiscuity 0 
    can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0 
	  bitrate 500000 sample-point 0.875 
	  tq 250 prop-seg 3 phase-seg1 3 phase-seg2 1 sjw 1
	  c_can: tseg1 2..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp-inc 1
	  clock 20000000numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 
root@dra7xx-evm:~# 
root@dra7xx-evm:~# ifconfig
can0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          UP RUNNING NOARP  MTU:16  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:87 

eth0      Link encap:Ethernet  HWaddr 38:0B:3C:40:EA:44  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:84 

eth1      Link encap:Ethernet  HWaddr 38:0B:3C:40:EA:45  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1%763612/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:162 errors:0 dropped:0 overruns:0 frame:0
          TX packets:162 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:12300 (12.0 KiB)  TX bytes:12300 (12.0 KiB)

root@dra7xx-evm:~# cansend can0 123#1122334455
root@dra7xx-evm:~# ifconfig
can0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          UP RUNNING NOARP  MTU:16  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:87 

eth0      Link encap:Ethernet  HWaddr 38:0B:3C:40:EA:44  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:84 

eth1      Link encap:Ethernet  HWaddr 38:0B:3C:40:EA:45  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1%763612/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:162 errors:0 dropped:0 overruns:0 frame:0
          TX packets:162 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:12300 (12.0 KiB)  TX bytes:12300 (12.0 KiB)

root@dra7xx-evm:~# cat setup_can_bus.sh 
#!/bin/sh

#modprobe can
#modprobe can-dev
#modprobe can-raw
#modprobe mcp251x
ip link set can"$1" down
ip link set can"$1" type can bitrate 500000
ip link set can"$1" up
ip -details link show can0
root@dra7xx-evm:~# ip -details link show can0
2: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 10
    link/can  promiscuity 0 
    can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0 
	  bitrate 500000 sample-point 0.875 
	  tq 250 prop-seg 3 phase-seg1 3 phase-seg2 1 sjw 1
	  c_can: tseg1 2..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp-inc 1
	  clock 20000000numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 
root@dra7xx-evm:~# can
can-calc-bit-timing  candump              cangen               canlogserver         cansend              
canbusload           canfdtest            cangw                canplayer            cansniffer           
root@dra7xx-evm:~# can
can-calc-bit-timing  candump              cangen               canlogserver         cansend              
canbusload           canfdtest            cangw                canplayer            cansniffer           
root@dra7xx-evm:~# can   ip -details link show can0
2: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 10
    link/can  promiscuity 0 
    can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0 
	  bitrate 500000 sample-point 0.875 
	  tq 250 prop-seg 3 phase-seg1 3 phase-seg2 1 sjw 1
	  c_can: tseg1 2..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp-inc 1
	  clock 20000000numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 

==============================================================
I also noticed the comment of Errata code in device tree. If it causes the module to not work properly. what should i do？ or where can I refer to sample code?

Thank you so much.
↧

Linux/AM5726: Debugging with OpenMP

July 22, 2019, 10:44 pm
$
0
0

Part Number: AM5726

Tool/software: Linux

Hi All,

As you know if we want to compile an OpenMP application, it is not directly compiled to directly to executable or binary. Some intermediate codes having .int.c extension are generated and then compiled to binary. Unfortunately while debugging OpenMP application we cannot go over the OpenMP code we have written but we need to go over the intermediate, generated code makes our lives miserable. I would like to ask if there is a way / method / tool to debug OpenMP applications without deeping dive into the intermediate code. I appreciate if you can help me regarding the issue.

Kind Regards,

Mustafa

↧

Linux/AM3358: ‘No Signal’ on LCD screen using Beagle Bone Black and HDMI

July 22, 2019, 11:13 pm
$
0
0

Part Number: AM3358

Tool/software: Linux

Hi,

The customer add panel in DTS and ‘No Signal’ on LCD screen.

SDK:ti-processor-sdk-linux-am335x-evm-05.03.00.07

rootfs:tisdk-rootfs-image-am335x-evm

HDMI LCD:1024*600

Modification in am335x-boneblack-common.dtsi:

LCDC select “crossed”

enable video-ports = <0x234501>; 

Add panel

↧
↧

JESD BASED Radio interface through IQNet2 interface to K2L

July 22, 2019, 11:18 pm
$
0
0

Part Number: XEVMK2LX

Hello All,

 I am very new in this field , I need to interface radio using JESD through IQNet2 to K2L. Please guide me,how to start ?

↧

Linux/AM5728: am5728 evm board does not recognize dlp modules

July 22, 2019, 11:28 pm
$
0
0

Part Number: AM5728

Tool/software: Linux

Connect dlp4500 module with am5728 evm board, write test function directly to verify that dlp4500 module can be recognized, fail to call hid_open (0x04510x6401, null) or hid_enumerate (0x04551, 0x6401). Is there no dlp driver code on the am5728 evm board? Where can I find the driver code for dlp4500, thank you!

↧

RTOS/PROCESSOR-SDK-AM437X: AM437x TI RTOS NIMU TCP/IP server/client example

July 22, 2019, 11:58 pm
$
0
0

Part Number: PROCESSOR-SDK-AM437X

Tool/software: TI-RTOS

HI,

I am using AM437x based custom board, CCSv6 IDE and RTOS SDK 3.01.00.06. I have taken the "NIMU_BasicExample_idkAM437x_armExampleproject" as reference, with this example I am able to ping the giga bit ethernet port on my custom board. Now I want to implement socket programming kindly provide the TCP/IP server/client example code for TI RTOS NDK.

Regards

Nagaraj G

↧
Search

Linux/AM5708: Using USB camera by gstream , problem with patch file usb_capture.txt

July 23, 2019, 12:27 am
$
0
0

Part Number: AM5708

Tool/software: Linux

Hello, my board process is AM570x and i'm using the sdk: ti-processor-sdk-linux-rt-am57xx-evm-04.03.00.05-Linux-x86, kernel version is 4.9.69

I have run the following gstream pipeline and I also get the Internal data flow error.

The pipeline get from (http://downloads.ti.com/processor-sdk-linux/esd/docs/04_03_00_05/linux/Foundational_Components.html#processor-sdk-linux-multimedia) is like this:

gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \
format=(string)YUY2, width=(int)1280, height=(int)720' ! vpe num-input-buffers=8 ! queue ! kmssink

I also see the thread (https://e2e.ti.com/support/processors/f/791/p/523614/2023362#pi316653=2), and I know I need to manually apply the patch file usb_capture.txt as the kernel version may be different .

I do as above, but when I manually modify the file /drivers/media/usb/uvc/uvc_queue.c mentioned by the patch file, I find that the patch file isn't  suitable for kernel4.x, the patch file is suitable for kernel 3.x.

The follwing pictures give a detailed explanation.

Changes mentioned by path file usb_capture.txt:


The diff of file /drivers/media/usb/uvc/uvc_queue.c in Kernel 3.x and kernel 4.x:

 


Obviously, the patch file can't be applied to kernel v4.9, and I don't know how to modify the kernel code.

Will anyone could give me some advice if he knows how to modify the kernel code.

Thanks & Regard

Luo Wei

 

↧
↧

CCS/AM5728: PRU cycle counter issue

July 23, 2019, 12:36 am
$
0
0

Part Number: AM5728

Tool/software: Code Composer Studio

Hello .I am using pru cycle counter . I enable the counter by

PRU0_CTRL.CONTROL_bit.COUNTER_ENABLE=0x1;

and when CYCLECOUNT reaches its maxmum value(0xFFFF FFFF)

COUNTER_ENABLE will automatically set to 0 .

which is correct as the TRM said.But even if I reset COUNTER_ENABLE to 1, CYCLECOUNT set to 0, the CYCLECOUT won't count any more(remains 0 forever). I wanna know why .Thanks ahead.

↧

Linux/TDA2SX: DP83867 : Link is up,but unable to ping

July 23, 2019, 1:15 am
$
0
0

Part Number: TDA2SX

Tool/software: Linux

Hello all,

                       We are working on a custom board based on tda2sx.We are using dp83867 in RGMII mode.The driver is registering the phy.I am able to assigne i.p address.I have connected the board to a PC and the link was up.But I am not able to ping to the PC.

DTS config:

&mac {
        status = "okay";

};

&davinci_mdio {

       compatible = "ti,cpsw-mdio", "ti,davinci_mdio";
       status = "okay";

        dp83867_0: ethernet-phy@8 {
                reg = <8>;
                ti,rx-internal-delay = <DP83867_RGMIIDCTL_2_25_NS>;
                ti,tx-internal-delay = <DP83867_RGMIIDCTL_250_PS>;
                ti,fifo-depth = <DP83867_PHYCR_FIFO_DEPTH_8_B_NIB>;
ti,min-output-impedance;
                ti,dp83867-rxctrl-strap-quirk;
        };

};


&cpsw_emac0 {
        status = "okay";
        phy_id = <&davinci_mdio>, <8>;
        phy-mode = "rgmii-id";
/*      dual_emac_res_vlan = <1>;*/
};

Boot log related to phy:

libphy: 48485000.mdio: probed
davinci_mdio 48485000.mdio: phy[8]: device 48485000.mdio:08, driver TI DP83867
cpsw 48484000.ethernet: No slave[1] phy_id, phy-handle, or fixed-link property
net eth0: phy found : id is : 0x2000a231

ifconfig eth0 :

eth0      Link encap:Ethernet  HWaddr B0:7E:11:3E:7B:EC  
          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::b27e:11ff:fe3e:7bec%3068936984/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:673 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:60610 (59.1 KiB)
          Interrupt:105

ethtool eth0:

Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 10Mb/s
        Duplex:Full
        Port: MII
        PHYAD: 8
        Transceiver: external
        Auto-negotiation: off
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000000 (0)
                               
        Link detected: yes

 ethtool -S  eth0 :                                                                                                        
NIC statistics:
     Good Rx Frames: 0
     Broadcast Rx Frames: 0
     Multicast Rx Frames: 0
     Pause Rx Frames: 0
     Rx CRC Errors: 0
     Rx Align/Code Errors: 0
     Oversize Rx Frames: 0
     Rx Jabbers: 0
     Undersize (Short) Rx Frames: 0
     Rx Fragments: 0
     Rx Octets: 0
     Good Tx Frames: 0
     Broadcast Tx Frames: 0
     Multicast Tx Frames: 0
     Pause Tx Frames: 0
     Deferred Tx Frames: 0
     Collisions: 0
     Single Collision Tx Frames: 0
     Multiple Collision Tx Frames: 0
     Excessive Collisions: 0
     Late Collisions: 0
     Tx Underrun: 0
     Carrier Sense Errors: 119
     Tx Octets: 0
     Rx + Tx 64 Octet Frames: 0
     Rx + Tx 65-127 Octet Frames: 0
     Rx + Tx 128-255 Octet Frames: 0
     Rx + Tx 256-511 Octet Frames: 0
     Rx + Tx 512-1023 Octet Frames: 0
     Rx + Tx 1024-Up Octet Frames: 0
     Net Octets: 833
     Rx Start of Frame Overruns: 0
     Rx Middle of Frame Overruns: 0
     Rx DMA Overruns: 0
     Rx DMA chan: head_enqueue: 2
     Rx DMA chan: tail_enqueue: 254
     Rx DMA chan: pad_enqueue: 0
     Rx DMA chan: misqueued: 0
     Rx DMA chan: desc_alloc_fail: 0
     Rx DMA chan: pad_alloc_fail: 0
     Rx DMA chan: runt_receive_buf: 0
     Rx DMA chan: runt_transmit_buf: 0
     Rx DMA chan: empty_dequeue: 0
     Rx DMA chan: busy_dequeue: 0
     Rx DMA chan: good_dequeue: 1
     Rx DMA chan: requeue: 1
     Rx DMA chan: teardown_dequeue: 127
     Tx DMA chan: head_enqueue: 671
     Tx DMA chan: tail_enqueue: 2
     Tx DMA chan: pad_enqueue: 0
     Tx DMA chan: misqueued: 2
     Tx DMA chan: desc_alloc_fail: 0
     Tx DMA chan: pad_alloc_fail: 0
     Tx DMA chan: runt_receive_buf: 0
     Tx DMA chan: runt_transmit_buf: 512
     Tx DMA chan: empty_dequeue: 672
     Tx DMA chan: busy_dequeue: 0
     Tx DMA chan: good_dequeue: 673
     Tx DMA chan: requeue: 0
     Tx DMA chan: teardown_dequeue: 0

When board is connected to PC(192.168.1.52):

 cpsw 48484000.ethernet eth0: Link is Up - 10Mbps/Full- flow control off

I have set autonegg off on both sides and set speed to 10Mbps

                                       We are using a mini50 connector the board side.What could be the issue?Does cross connection/straight connection  has anything to do with this?

Regards,

Murugan S

↧

Compiler/TDA2E: PROCESSOR_SDK_RADAR_03_07_00_00 Compilation error

July 23, 2019, 1:36 am
$
0
0

Part Number: TDA2E

Tool/software: TI C/C++ Compiler

Hello

We are currently using the TDA2 SDK version number 03_07_00_00 (downloaded from TI PROCESSOR_SDK_RADAR_03_07_00_00.exe).

I have followed the steps mentioned in the VisionSDK_UserGuide_TDA2xx.pdf section 2 (system requirements). My compilation works on windows environment.

After doing the above step I try to compile the project tda2xx_cascade_bios_radar by using the following steps (i put this in one batch file)

1) Go to the folder C:\PROCESSOR_SDK_RADAR_03_07_00_00\vision_sdk\build

2) Make a batch file compile.bat with following lines

set PATH=C:\PROCESSOR_SDK_RADAR_03_07_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core;%PATH%
set MAKEAPPNAME=apps
set MAKECONFIG=tda2xx_cascade_bios_radar


gmake -s -j8 depend >proto.txt
gmake -s -j8

After about half an hour later i get following warning message on my console

which i guess is not important and can be ignored for TDA2 Radar SDK compilation

"C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/apps/configs/autorules_footer_cfg.mk:67: ipc_PATH does not exist! () "

The console logs detailing what is the error i am facing

"

C:\PROCESSOR_SDK_RADAR_03_07_00_00\vision_sdk\build>Compile.bat

C:\PROCESSOR_SDK_RADAR_03_07_00_00\vision_sdk\build>set PATH=C:\PROCESSOR_SDK_RADAR_03_07_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core;C:\PROCESSOR_SDK_RADAR_03_07_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core;C:\PROCESSOR_SDK_RADAR_03_07_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core;C:\PROCESSOR_SDK_RADAR_03_07_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core;C:\PROCESSOR_SDK_RADAR_03_07_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core;C:\PROCESSOR_SDK_RADAR_03_07_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core;C:\Anaconda2;C:\Anaconda2\Library\mingw-w64\bin;C:\Anaconda2\Library\usr\bin;C:\Anaconda2\Library\bin;C:\Anaconda2\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Gemalto\Access Client\v5\;C:\Program Files (x86)\Gemalto\Access Client\v5\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Sennheiser\SoftphoneSDK\;C:\Program Files\MATLAB\R2018a\bin;C:\Program Files\Git\cmd;C:\Strawberry\c\bin;C:\Strawberry\perl\site\bin;C:\Strawberry\perl\bin;C:\Program Files\TortoiseGit\bin;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\dotnet\;C:\PROCESSOR_SDK_RADAR_03_07_00_00\ti_components\cg_tools\windows\gcc-arm-none-eabi-4_9-2015q3\bin;C:\Users\djoshi\AppData\Local\Microsoft\WindowsApps;C:\Users\djoshi\AppData\Local\Programs\Microsoft VS Code\bin;D:\Todo Backup\bin\x64\

C:\PROCESSOR_SDK_RADAR_03_07_00_00\vision_sdk\build>set MAKEAPPNAME=apps

C:\PROCESSOR_SDK_RADAR_03_07_00_00\vision_sdk\build>set MAKECONFIG=tda2xx_cascade_bios_radar

C:\PROCESSOR_SDK_RADAR_03_07_00_00\vision_sdk\build>gmake -s -j8 depend 1>proto.txt
C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/apps/configs/autorules_footer_cfg.mk:67: ipc_PATH does not exist! ()
C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/apps/configs/autorules_footer_cfg.mk:67: ipc_PATH does not exist! ()
/cygdrive/c/PROCESSOR_SDK_RADAR_03_07_00_00/ti_components/os_tools/windows/xdctools_3_32_01_22_core/bin/mkdir: cannot create directory `C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/links_fw/include/config': File exists
/cygdrive/c/PROCESSOR_SDK_RADAR_03_07_00_00/ti_components/os_tools/windows/xdctools_3_32_01_22_core/bin/mkdir: cannot create directory `C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/links_fw/include/config/apps': File exists
/cygdrive/c/PROCESSOR_SDK_RADAR_03_07_00_00/ti_components/os_tools/windows/xdctools_3_32_01_22_core/bin/mkdir: cannot create directory `C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/links_fw/include/config/apps/tda2xx_cascade_bios_radar': File exists
C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/apps/configs/autorules_footer_cfg.mk:67: ipc_PATH does not exist! ()
C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/apps/configs/autorules_footer_cfg.mk:67: ipc_PATH does not exist! ()
C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/apps/configs/autorules_footer_cfg.mk:67: ipc_PATH does not exist! ()
C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/apps/configs/autorules_footer_cfg.mk:67: ipc_PATH does not exist! ()
C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/apps/configs/autorules_footer_cfg.mk:67: ipc_PATH does not exist! ()
C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/apps/configs/autorules_footer_cfg.mk:67: ipc_PATH does not exist! ()
C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/apps/configs/autorules_footer_cfg.mk:67: ipc_PATH does not exist! ()
MAKEFILE.MK:33: warning: overriding commands for target `apps'
MAKEFILE.MK:33: warning: ignoring old commands for target `apps'
MAKEFILE.MK:56: warning: overriding commands for target `apps_eve1'
MAKEFILE.MK:56: warning: ignoring old commands for target `apps_eve1'
MAKEFILE.MK:67: warning: overriding commands for target `apps_eve2'
MAKEFILE.MK:67: warning: ignoring old commands for target `apps_eve2'
MAKEFILE.MK:78: warning: overriding commands for target `apps_eve3'
MAKEFILE.MK:78: warning: ignoring old commands for target `apps_eve3'
MAKEFILE.MK:89: warning: overriding commands for target `apps_eve4'
MAKEFILE.MK:89: warning: ignoring old commands for target `apps_eve4'
MAKEFILE.MK:105: warning: overriding commands for target `apps_ipu1_1'
MAKEFILE.MK:105: warning: ignoring old commands for target `apps_ipu1_1'
MAKEFILE.MK:116: warning: overriding commands for target `apps_dsp1'
MAKEFILE.MK:116: warning: ignoring old commands for target `apps_dsp1'
MAKEFILE.MK:151: warning: overriding commands for target `apps_ipu1_0'
MAKEFILE.MK:151: warning: ignoring old commands for target `apps_ipu1_0'
MAKEFILE.MK:168: warning: overriding commands for target `libs'
MAKEFILE.MK:168: warning: ignoring old commands for target `libs'
MAKEFILE.MK:171: warning: overriding commands for target `clean_files'
MAKEFILE.MK:171: warning: ignoring old commands for target `clean_files'
MAKEFILE.MK:184: warning: overriding commands for target `clean'
MAKEFILE.MK:184: warning: ignoring old commands for target `clean'
MAKEFILE.MK:267: warning: overriding commands for target `depend'
MAKEFILE.MK:267: warning: ignoring old commands for target `depend'
MAKEFILE.MK:274: warning: overriding commands for target `header'
MAKEFILE.MK:274: warning: ignoring old commands for target `header'
MAKEFILE.MK:279: warning: overriding commands for target `footer'
MAKEFILE.MK:279: warning: ignoring old commands for target `footer'
MAKEFILE.MK:285: warning: overriding commands for target `all'
MAKEFILE.MK:285: warning: ignoring old commands for target `all'
MAKEFILE.MK:33: warning: overriding commands for target `apps'
MAKEFILE.MK:33: warning: ignoring old commands for target `apps'
MAKEFILE.MK:56: warning: overriding commands for target `apps_eve1'
MAKEFILE.MK:56: warning: ignoring old commands for target `apps_eve1'
MAKEFILE.MK:67: warning: overriding commands for target `apps_eve2'
MAKEFILE.MK:67: warning: ignoring old commands for target `apps_eve2'
MAKEFILE.MK:78: warning: overriding commands for target `apps_eve3'
MAKEFILE.MK:78: warning: ignoring old commands for target `apps_eve3'
MAKEFILE.MK:89: warning: overriding commands for target `apps_eve4'
MAKEFILE.MK:89: warning: ignoring old commands for target `apps_eve4'
MAKEFILE.MK:105: warning: overriding commands for target `apps_ipu1_1'
MAKEFILE.MK:105: warning: ignoring old commands for target `apps_ipu1_1'
MAKEFILE.MK:116: warning: overriding commands for target `apps_dsp1'
MAKEFILE.MK:116: warning: ignoring old commands for target `apps_dsp1'
MAKEFILE.MK:151: warning: overriding commands for target `apps_ipu1_0'
MAKEFILE.MK:151: warning: ignoring old commands for target `apps_ipu1_0'
MAKEFILE.MK:168: warning: overriding commands for target `libs'
MAKEFILE.MK:168: warning: ignoring old commands for target `libs'
MAKEFILE.MK:171: warning: overriding commands for target `clean_files'
MAKEFILE.MK:171: warning: ignoring old commands for target `clean_files'
MAKEFILE.MK:184: warning: overriding commands for target `clean'
MAKEFILE.MK:184: warning: ignoring old commands for target `clean'
MAKEFILE.MK:267: warning: overriding commands for target `depend'
MAKEFILE.MK:267: warning: ignoring old commands for target `depend'
MAKEFILE.MK:274: warning: overriding commands for target `header'
MAKEFILE.MK:274: warning: ignoring old commands for target `header'
MAKEFILE.MK:279: warning: overriding commands for target `footer'
MAKEFILE.MK:279: warning: ignoring old commands for target `footer'
MAKEFILE.MK:285: warning: overriding commands for target `all'
MAKEFILE.MK:285: warning: ignoring old commands for target `all'
MAKEFILE.MK:33: warning: overriding commands for target `apps'
MAKEFILE.MK:33: warning: ignoring old commands for target `apps'
MAKEFILE.MK:56: warning: overriding commands for target `apps_eve1'
MAKEFILE.MK:56: warning: ignoring old commands for target `apps_eve1'
MAKEFILE.MK:67: warning: overriding commands for target `apps_eve2'
MAKEFILE.MK:67: warning: ignoring old commands for target `apps_eve2'
MAKEFILE.MK:78: warning: overriding commands for target `apps_eve3'
MAKEFILE.MK:78: warning: ignoring old commands for target `apps_eve3'
MAKEFILE.MK:89: warning: overriding commands for target `apps_eve4'
MAKEFILE.MK:89: warning: ignoring old commands for target `apps_eve4'
MAKEFILE.MK:105: warning: overriding commands for target `apps_ipu1_1'
MAKEFILE.MK:105: warning: ignoring old commands for target `apps_ipu1_1'
MAKEFILE.MK:116: warning: overriding commands for target `apps_dsp1'
MAKEFILE.MK:116: warning: ignoring old commands for target `apps_dsp1'
MAKEFILE.MK:151: warning: overriding commands for target `apps_ipu1_0'
MAKEFILE.MK:151: warning: ignoring old commands for target `apps_ipu1_0'
MAKEFILE.MK:168: warning: overriding commands for target `libs'
MAKEFILE.MK:168: warning: ignoring old commands for target `libs'
MAKEFILE.MK:171: warning: overriding commands for target `clean_files'
MAKEFILE.MK:171: warning: ignoring old commands for target `clean_files'
MAKEFILE.MK:184: warning: overriding commands for target `clean'
MAKEFILE.MK:184: warning: ignoring old commands for target `clean'
MAKEFILE.MK:267: warning: overriding commands for target `depend'
MAKEFILE.MK:267: warning: ignoring old commands for target `depend'
MAKEFILE.MK:274: warning: overriding commands for target `header'
MAKEFILE.MK:274: warning: ignoring old commands for target `header'
MAKEFILE.MK:279: warning: overriding commands for target `footer'
MAKEFILE.MK:279: warning: ignoring old commands for target `footer'
MAKEFILE.MK:285: warning: overriding commands for target `all'
MAKEFILE.MK:285: warning: ignoring old commands for target `all'
MAKEFILE.MK:33: warning: overriding commands for target `apps'
MAKEFILE.MK:33: warning: ignoring old commands for target `apps'
MAKEFILE.MK:56: warning: overriding commands for target `apps_eve1'
MAKEFILE.MK:56: warning: ignoring old commands for target `apps_eve1'
MAKEFILE.MK:67: warning: overriding commands for target `apps_eve2'
MAKEFILE.MK:67: warning: ignoring old commands for target `apps_eve2'
MAKEFILE.MK:78: warning: overriding commands for target `apps_eve3'
MAKEFILE.MK:78: warning: ignoring old commands for target `apps_eve3'
MAKEFILE.MK:89: warning: overriding commands for target `apps_eve4'
MAKEFILE.MK:89: warning: ignoring old commands for target `apps_eve4'
MAKEFILE.MK:105: warning: overriding commands for target `apps_ipu1_1'
MAKEFILE.MK:105: warning: ignoring old commands for target `apps_ipu1_1'
MAKEFILE.MK:116: warning: overriding commands for target `apps_dsp1'
MAKEFILE.MK:116: warning: ignoring old commands for target `apps_dsp1'
MAKEFILE.MK:151: warning: overriding commands for target `apps_ipu1_0'
MAKEFILE.MK:151: warning: ignoring old commands for target `apps_ipu1_0'
MAKEFILE.MK:168: warning: overriding commands for target `libs'
MAKEFILE.MK:168: warning: ignoring old commands for target `libs'
MAKEFILE.MK:171: warning: overriding commands for target `clean_files'
MAKEFILE.MK:171: warning: ignoring old commands for target `clean_files'
MAKEFILE.MK:184: warning: overriding commands for target `clean'
MAKEFILE.MK:184: warning: ignoring old commands for target `clean'
MAKEFILE.MK:267: warning: overriding commands for target `depend'
MAKEFILE.MK:267: warning: ignoring old commands for target `depend'
MAKEFILE.MK:274: warning: overriding commands for target `header'
MAKEFILE.MK:274: warning: ignoring old commands for target `header'
MAKEFILE.MK:279: warning: overriding commands for target `footer'
MAKEFILE.MK:279: warning: ignoring old commands for target `footer'
MAKEFILE.MK:285: warning: overriding commands for target `all'
MAKEFILE.MK:285: warning: ignoring old commands for target `all'
MAKEFILE.MK:33: warning: overriding commands for target `apps'
MAKEFILE.MK:33: warning: ignoring old commands for target `apps'
MAKEFILE.MK:56: warning: overriding commands for target `apps_eve1'
MAKEFILE.MK:56: warning: ignoring old commands for target `apps_eve1'
MAKEFILE.MK:67: warning: overriding commands for target `apps_eve2'
MAKEFILE.MK:67: warning: ignoring old commands for target `apps_eve2'
MAKEFILE.MK:78: warning: overriding commands for target `apps_eve3'
MAKEFILE.MK:78: warning: ignoring old commands for target `apps_eve3'
MAKEFILE.MK:89: warning: overriding commands for target `apps_eve4'
MAKEFILE.MK:89: warning: ignoring old commands for target `apps_eve4'
MAKEFILE.MK:105: warning: overriding commands for target `apps_ipu1_1'
MAKEFILE.MK:105: warning: ignoring old commands for target `apps_ipu1_1'
MAKEFILE.MK:116: warning: overriding commands for target `apps_dsp1'
MAKEFILE.MK:116: warning: ignoring old commands for target `apps_dsp1'
MAKEFILE.MK:151: warning: overriding commands for target `apps_ipu1_0'
MAKEFILE.MK:151: warning: ignoring old commands for target `apps_ipu1_0'
MAKEFILE.MK:168: warning: overriding commands for target `libs'
MAKEFILE.MK:168: warning: ignoring old commands for target `libs'
MAKEFILE.MK:171: warning: overriding commands for target `clean_files'
MAKEFILE.MK:171: warning: ignoring old commands for target `clean_files'
MAKEFILE.MK:184: warning: overriding commands for target `clean'
MAKEFILE.MK:184: warning: ignoring old commands for target `clean'
MAKEFILE.MK:267: warning: overriding commands for target `depend'
MAKEFILE.MK:267: warning: ignoring old commands for target `depend'
MAKEFILE.MK:274: warning: overriding commands for target `header'
MAKEFILE.MK:274: warning: ignoring old commands for target `header'
MAKEFILE.MK:279: warning: overriding commands for target `footer'
MAKEFILE.MK:279: warning: ignoring old commands for target `footer'
MAKEFILE.MK:285: warning: overriding commands for target `all'
MAKEFILE.MK:285: warning: ignoring old commands for target `all'
MAKEFILE.MK:33: warning: overriding commands for target `apps'
MAKEFILE.MK:33: warning: ignoring old commands for target `apps'
MAKEFILE.MK:56: warning: overriding commands for target `apps_eve1'
MAKEFILE.MK:56: warning: ignoring old commands for target `apps_eve1'
MAKEFILE.MK:67: warning: overriding commands for target `apps_eve2'
MAKEFILE.MK:67: warning: ignoring old commands for target `apps_eve2'
MAKEFILE.MK:78: warning: overriding commands for target `apps_eve3'
MAKEFILE.MK:78: warning: ignoring old commands for target `apps_eve3'
MAKEFILE.MK:89: warning: overriding commands for target `apps_eve4'
MAKEFILE.MK:89: warning: ignoring old commands for target `apps_eve4'
MAKEFILE.MK:105: warning: overriding commands for target `apps_ipu1_1'
MAKEFILE.MK:105: warning: ignoring old commands for target `apps_ipu1_1'
MAKEFILE.MK:116: warning: overriding commands for target `apps_dsp1'
MAKEFILE.MK:116: warning: ignoring old commands for target `apps_dsp1'
MAKEFILE.MK:151: warning: overriding commands for target `apps_ipu1_0'
MAKEFILE.MK:151: warning: ignoring old commands for target `apps_ipu1_0'
MAKEFILE.MK:168: warning: overriding commands for target `libs'
MAKEFILE.MK:168: warning: ignoring old commands for target `libs'
MAKEFILE.MK:171: warning: overriding commands for target `clean_files'
MAKEFILE.MK:171: warning: ignoring old commands for target `clean_files'
MAKEFILE.MK:184: warning: overriding commands for target `clean'
MAKEFILE.MK:184: warning: ignoring old commands for target `clean'
MAKEFILE.MK:267: warning: overriding commands for target `depend'
MAKEFILE.MK:267: warning: ignoring old commands for target `depend'
MAKEFILE.MK:274: warning: overriding commands for target `header'
MAKEFILE.MK:274: warning: ignoring old commands for target `header'
MAKEFILE.MK:279: warning: overriding commands for target `footer'
MAKEFILE.MK:279: warning: ignoring old commands for target `footer'
MAKEFILE.MK:285: warning: overriding commands for target `all'
MAKEFILE.MK:285: warning: ignoring old commands for target `all'
gmake[3]: *** No rule to make target `;'. Stop.
gmake[2]: *** [depend] Error 2
gmake[1]: *** [links_fw_depend] Error 2
gmake: *** [depend] Error 2

C:\PROCESSOR_SDK_RADAR_03_07_00_00\vision_sdk\build>gmake -s -j8
C:/PROCESSOR_SDK_RADAR_03_07_00_00/vision_sdk/apps/configs/autorules_footer_cfg.mk:67: ipc_PATH does not exist! ()
gmake[5]: *** No rule to make target `;'. Stop.
gmake[4]: *** [links_common_algorithm] Error 2
gmake[3]: *** [libs] Error 2
gmake[2]: *** [links_fw_libs] Error 2
gmake[1]: *** [apps] Error 2
gmake: *** [vision_sdk] Error 2

"

Also Attached is the logs of Proto.txt( Generated in this step (gmake -s -j8 depend >proto.txt) 

Is it possibel can someone tell me whats happening here. I tried this step on various windows machine and everywhere i struck up in this step.

Br

Deepak Joshi

Proto.txt

(Please visit the site to view this file)

↧

Linux/TDA2EVM5777: HDMI display 6-channel camera data

July 23, 2019, 2:05 am
$
0
0

Part Number: TDA2EVM5777

Tool/software: Linux

Hi，

   The usecas I use is 4CH VIP LVDS capture + SGX MOSAIC + DISPLAY,

   gChains_usecaseCfg.numLvdsCh = 6; pObj->vidSensorPrm.numLvdsCh = 6; prms->renderType = SGXFRMCPY_RENDER_TYPE_3x3;

 HDMI does not have an image output display, how should I set it to display 6 video images correctly?

↧
↧

TMS320C5535: I2S Reinit

July 23, 2019, 2:30 am
$
0
0

Part Number: TMS320C5535

Hello,

we are using i2s with dma in slave mode and want to switch i2s clocks and data sources during runtime. So I thought it would be best to reinit the i2s and the dma channels after switching the i2s sources. Now I saw in sprufp4a.pdf that the i2s shift registers are not emptied when the peripheral is reinitialized. I hope that the i2s peripheral automatically resyncs to the new WCLK and BCLK so that no permanent corrupt data ocurs. Is that right?

The reinit procedure with csl is the following:

Stop i2s

DMA_stop()

I2s_setup()

DMA_reset()

DMA_config()

DMA_start()

Start i2s

Thanks in advance

Marc

↧

Linux/PROCESSOR-SDK-AM57X: Packet storm with unknown MAC address

July 23, 2019, 2:37 am
$
0
0

Part Number: PROCESSOR-SDK-AM57X

Tool/software: Linux

Hi,

We are having an issue with packet storms on the phyCORE AM57x in the following scenario:

The AM57x is in dual emac mode.

eth0 and eth1 are bonded and tagged with VLANs 3329 and 3330, and the bond itself is also tagged with an additional VLAN 3331.

The used kernel is 4.4.32-phy1, patched with only git.kernel.org/.../cpsw.c

What happens:
In situations where a MAC is unknown and flooded to the connected devices, the AM57x end device creates a packet storm of ICMP echo requests.

TCP dump logs from an end device, where 10.254.31.12 is the IP of SERVER:

13:39:35.259440 IP 10.254.31.12 > 10.254.31.222: ICMP echo request, id 31372, seq 1, length 64
13:39:35.259507 IP 10.254.31.12 > 10.254.31.222: ICMP echo request, id 31372, seq 1, length 64
13:39:35.259574 IP 10.254.31.12 > 10.254.31.222: ICMP echo request, id 31372, seq 1, length 64
13:39:35.259641 IP 10.254.31.12 > 10.254.31.222: ICMP echo request, id 31372, seq 1, length 64
13:39:35.259707 IP 10.254.31.12 > 10.254.31.222: ICMP echo request, id 31372, seq 1, length 64

Additionally, the location of SERVER (7a42-0afe-1f49) hops between ports hundreds of times.

Switch Logs:

MAC address 7a42-0afe-1f49 in VLAN 3331 has moved from port GE1/0/19 to port GE1/0/20 for 808 times.
MAC address 7a42-0afe-1f49 in VLAN 3331 has moved from port GE1/0/19 to port GE1/0/22 for 795 times.
MAC address 7a42-0afe-1f49 in VLAN 3331 has moved from port GE1/0/22 to port GE1/0/19 for 790 times.
MAC address 7a42-0afe-1f49 in VLAN 3331 has moved from port GE1/0/20 to port GE1/0/22 for 780 times.


Steps to Reproduce:
1. On Server, manually add an arp entry for an IP address and MAC address that both do not exist on the network

arp -s 10.254.31.222 7a:42:0a:fe:1f:de

2. From Server, ping the newly added IP address

ping 10.254.31.222

ARP table on Server contains new entry, where macvlandata0 is tagged with VLAN 3331:

Address                  HWtype  HWaddress           Flags Mask            Iface
10.254.31.222        ether       7a:42:0a:fe:1f:de   CM                    macvlandata0

This issue does not seem to occur with no VLAN on top of the bond itself.

Below is a network diagram should it be helpful. I have also attached our network configuration.

I am not sure if this issue is somehow related to 

(Please visit the site to view this file)

Thank you in advance for your assistance,

Richard Roth

MAC address 7a42-0afe-1f49 in VLAN 3331 has moved from port GE1/0/19 to port GE1/0/20 for 808 times.
MAC address 7a42-0afe-1f49 in VLAN 3331 has moved from port GE1/0/19 to port GE1/0/22 for 795 times.
MAC address 7a42-0afe-1f49 in VLAN 3331 has moved from port GE1/0/22 to port GE1/0/19 for 790 times.
MAC address 7a42-0afe-1f49 in VLAN 3331 has moved from port GE1/0/20 to port GE1/0/22 for 780 times.

↧
Search

AM3358: Boot Rom Error Checking done by OCMC

July 23, 2019, 2:56 am
$
0
0

Part Number: AM3358

Hi,

I was wondering for the AM3358 what takes care of the error checking for boot rom?

Is it the on chip memory controller?

For Instance a system on the boot ROM to prevent single bit flip from resulting in an unbootable system?

In this case could fall under a parity check, however in technical reference manual section 7.2 OCMC-RAM

It states Parity is not supported under unsupported features, is there any other part of the processor that takes care of this?

↧

RTOS/TMS320C6748: ti.sysbios.family.c64p.Exception: line 256

July 23, 2019, 2:57 am
$
0
0

Part Number: TMS320C6748

Tool/software: TI-RTOS

Hi,

The customer transplanted demo USB_DEV_MSC in PDK into his own application prj. USB_DEV_MSC and his project have been independently tested successfully independently. And the integrated project can be built successfully. But when load to board error occurred as below:

He monitor that exception error by ROV. This is screenshort.

Could you please help analyze from ROV screenshot?

 

↧
↧

Compiler/TMS320C6678: Different behavior with/without printf

July 23, 2019, 3:01 am
$
0
0

Part Number: TMS320C6678

Tool/software: TI C/C++ Compiler

Hi there,

following two situation lead to different behavior and it is crucial to me to know why:

1.) Code includes a printf statement:

#pragma DATA_SECTION(selfId, ".local_data")
Uint32 selfId;
void main(void) {
    selfId = CSL_chipReadReg(CSL_CHIP_DNUM);
    printf("selfId = %d\n", selfId);
    config_cache(selfId);

....

2.) Code does not include a print statement:

#pragma DATA_SECTION(selfId, ".local_data")
Uint32 selfId;
void main(void) {
    selfId = CSL_chipReadReg(CSL_CHIP_DNUM);
    config_cache(selfId);

....

In both cases .local_data maps to L2SRAM with L2SRAM defined in platform package as: {name: "L2SRAM",base: 0x00800000,len: 0x00080000,space: "code/data",access: "RWX" }. The same image is uploaded to each core.

Function config_cache asserts that selfId is between 0 and 7. I am getting different results depending on whether I include the printf statement or not:

- For situation 1 (with printf), things work fine, except that I am getting an error like "Invalid CIO command (11) in the CIO buffer at address (0xC02C248) was not recognized. Please check the device and program memory maps.". I guess that is due to the fact that several cores print at once.

- For situation 2 (without printf), the code fails with an assertion error. Function config_cache seems to see some random values

Please help. Thank you very much.

↧

AM3358-EP: over-driving one of the pins on the AM3358-EP

July 23, 2019, 3:10 am
$
0
0

Part Number: AM3358-EP

need to understand what the risks of overdriving the pin are in the short term.

We haven’t seen any failures related to this in any of the devices we are testing at the moment.

We intend to modify the design to remove the over-stress but we are unable to do that on the boards which are currently built and under-going test

 

The pin is question is the OSC0_IN (XTALIN

 

The table below is an extract from the datasheet which indicates that there is a level of overshoot tolerance.

 

The oscillator portion of the AM3358 is powered from 1.8V, given a max input from the above of 18.+0.3V = 2.1V

 

In circuit we are driving the OSC0_IN pin from a 3.3V logic device through a 22R source resistor. The output of the logic device is seen to be at approximately 2.9V and with the 2.1V maximum input at the AM3358 this implies we may be providing up to 36mA of current into that pin for ~50% of the clock period.

↧

Linux/AM5728: A weird problem happened when migrant the correct device tree file in linux_pdk5.3 to 6.0

July 23, 2019, 3:31 am
$
0
0

Part Number: AM5728

Tool/software: Linux

I have noticed that the new pdk for am5728 had published. And when I migrant the devicetree from 5.3 to 6.0, there is a weird prolemm like follows:

DTC     arch/arm/boot/dts/am57xx-cr-v2a.dtb
arch/arm/boot/dts/am57xx-cr-v2a.dtb: Warning (graph_endpoint): /ocp/i2c@4807c000/ar0135@10/port/endpoint: graph connection to node '/ocp/vip@0x48970000/ports/port@1' is not bidirectional
arch/arm/boot/dts/am57xx-cr-v2a.dtb: Warning (graph_endpoint): /ocp/vip@0x48970000/ports/port@1/endpoint: graph connection to node '/ocp/i2c@4807c000/ar0135@10/port/endpoint' is not bidirectional

And it has no problem on pdk5.3. The context of the warning is these:

&i2c5{
	status = "okay";
	ar0135@10{
    		compatible = "onsemi,ar0135";

			port{
				camera:endpoint{
		    				remote-endpoint = <&vin2a>;
							bus-width	=	<8>;	//8 for RAW8
							data-shift 	= 	<0>;	//0
		    				hsync-active= 	<1>; 	//0/1 for LOW/HIGH respectively
		    				vsync-active= 	<1>; 	//0/1 for LOW/HIGH respectively
		    				pclk-sample = 	<0>;  	//rising (1) or falling (0)
				};
    		};
	};


};


	
&vin2a{
	status = "okay";

	endpoint{
			slave-mode;
     		//remote-endpoint = <&camera>;
	};
};

Can you tell me why? And how can I solve it?

↧
Viewing all 17527 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>