Part Number: TMS320C6678

Hello Champs,

Do we have 3-port Gbe switch example for reference?

Customer wanted to know how to configure send data from DSP1 SGMII1 to DSP1 SGMII0 or vice versa.


Thanks.
Rgds
Shine

Part Number: TDA2PXEVM

Tool/software: TI C/C++ Compiler

We have a usecase running in IPU, we are using IPU, A15, DSP and EVE cores for different algorithms in the usecase.

We are observing that at one of the file_open call in IPU, the system gets hung. We suspect some task got crashed. We tried debugging(using JTAG) to find out, in which core which task is getting crashed. But we are not getting proper reason for the freeze.

Could you please provide some pointers to debug such problems?

We tried to analyse tasks/process state through ROV but we are not able to find the tasks state.

Part Number: TDA2PXEVM

Hello,

 What should  we do for applying  HDMI capture and HDMI display with  vip_single_cam_framecopy_sgx_display from apps\src\hlos\adas\src\usecases?  We use Linux(A15)+Bios(IPU) based on visionSDK 03_05.

And we try to modify  gChains_usecaseCfg.displayType = CHAINS_DISPLAY_TYPE_HDMI_1080P & gChains_usecaseCfg.captureSrc = CHAINS_CAPTURE_SRC_HDMI_1080P, but it will fail. Is there any configure we have to do?

Thanks

Terence

Part Number: TDA2P-ABZ

hi 

I am using TIDL framework in VSDK, The chian works well now. But the issue is the latency from the output of TIDL_PrePro( IPU1-0) to IPC_IN_0 (in EVE) is quite long, even almost 100ms.

The chain is like this ALG_TIDLPREPROC -> IPC_OUT_4 -> IPC_IN_0 -> ALG_TIDL.

I would like to know why the IPC_IN_0 is not shcheduled in time？Seem like the IPC_IN_0 get scheduled after the ALG_TIDL finished in EVE.

How can i sove this issue?

See the log below:

[IPU1-0]     97.211675 s:  ### CPU [IPU1-0], LinkID [ 54],
[IPU1-0]     97.211736 s: 
[IPU1-0]     97.211767 s:  [ ALG_TIDLPREPROC ] Link Statistics,
[IPU1-0]     97.211858 s:  ******************************
[IPU1-0]     97.211919 s: 
[IPU1-0]     97.211950 s:  Elapsed time       = 24812 msec
[IPU1-0]     97.212041 s: 
[IPU1-0]     97.212072 s:  New data Recv      =  11.56 fps
[IPU1-0]     97.212163 s: 
[IPU1-0]     97.212224 s:  Input Statistics,
[IPU1-0]     97.212285 s: 
[IPU1-0]     97.212316 s:  CH | In Recv | In Drop | In User Drop | In Process
[IPU1-0]     97.212377 s:     | FPS     | FPS     | FPS          | FPS       
[IPU1-0]     97.212468 s:  --------------------------------------------------
[IPU1-0]     97.212560 s:   0 |  11.56      0. 0      0. 0          11.56
[IPU1-0]     97.212682 s:  chId:  0 | inBufRecvCount: 287 |inBufDropCount: 0 |inBufUserDropCount: 0 |inBufProcessCount: 287
[IPU1-0]     97.212834 s: 
[IPU1-0]     97.212865 s:  Output Statistics,
[IPU1-0]     97.212926 s: 
[IPU1-0]     97.212956 s:  CH | Out | Out     | Out Drop | Out User Drop
[IPU1-0]     97.213017 s:     | ID  | FPS     | FPS      | FPS          
[IPU1-0]     97.213109 s:  ---------------------------------------------
[IPU1-0]     97.213200 s:   0 |  0     11.56     0. 0      0. 0
[IPU1-0]     97.213322 s: 
[IPU1-0]     97.213353 s:  [ ALG_TIDLPREPROC ] LATENCY,
[IPU1-0]     97.213444 s:  ********************
[IPU1-0]     97.213505 s:  Local Link Latency     : Avg =     67 us, Min =     30 us, Max =    579 us,
[IPU1-0]     97.213597 s:  Source to Link Latency : Avg =  52477 us, Min =  48404 us, Max =  59355 us,
[IPU1-0]     97.213719 s: 
[IPU1-0]     97.213749 s:  realtime =      0 us
[IPU1-0]     97.213810 s:  avgtime  =      0 us
[IPU1-0]     97.213871 s:  totalCnt =      0  
[IPU1-0]     97.214024 s: 
[IPU1-0]     97.214054 s:  ### CPU [IPU1-0], LinkID [  4],
[IPU1-0]     97.214176 s: 
[IPU1-0]     97.214207 s:  [ IPC_OUT_4 ] Link Statistics,
[IPU1-0]     97.214268 s:  ******************************
[IPU1-0]     97.214329 s: 
[IPU1-0]     97.214390 s:  Elapsed time       = 24710 msec
[IPU1-0]     97.214451 s: 
[IPU1-0]     97.214481 s:  New data Recv      =   5.78 fps
[IPU1-0]     97.214573 s:  Release data Recv  =   5.70 fps
[IPU1-0]     97.214634 s:  Driver/Notify Cb   = 105.70 fps
[IPU1-0]     97.214725 s: 
[IPU1-0]     97.214756 s:  Input Statistics,
[IPU1-0]     97.214817 s: 
[IPU1-0]     97.214847 s:  CH | In Recv | In Drop | In User Drop | In Process
[IPU1-0]     97.214908 s:     | FPS     | FPS     | FPS          | FPS       
[IPU1-0]     97.215000 s:  --------------------------------------------------
[IPU1-0]     97.215091 s:   0 |   5.78      0. 0      0. 0           5.78
[IPU1-0]     97.215457 s:  chId:  0 | inBufRecvCount: 143 |inBufDropCount: 0 |inBufUserDropCount: 0 |inBufProcessCount: 143
[IPU1-0]     97.215610 s: 
[IPU1-0]     97.215640 s:  Output Statistics,
[IPU1-0]     97.215701 s: 
[IPU1-0]     97.215732 s:  CH | Out | Out     | Out Drop | Out User Drop
[IPU1-0]     97.215823 s:     | ID  | FPS     | FPS      | FPS          
[IPU1-0]     97.215884 s:  ---------------------------------------------
[IPU1-0]     97.215945 s:   0 |  0      5.78     0. 0      0. 0
[IPU1-0]     97.216067 s: 
[IPU1-0]     97.216159 s:  [ IPC_OUT_4 ] LATENCY,
[IPU1-0]     97.216220 s:  ********************
[IPU1-0]     97.216281 s:  Local Link Latency     : Avg =      6 us, Min =      0 us, Max =     61 us,
[IPU1-0]     97.216403 s:  Source to Link Latency : Avg =  51741 us, Min =  48709 us, Max =  55847 us,
[IPU1-0]     97.216525 s: 
[IPU1-0]     97.216555 s:  realtime =      0 us
[IPU1-0]     97.216616 s:  avgtime  =      0 us
[IPU1-0]     97.216677 s:  totalCnt =      0  
[IPU1-0]     97.716281 s: 
[IPU1-0]     97.716342 s:  ### CPU [  EVE2], LinkID [ 10],
[IPU1-0]     97.716433 s: 
[IPU1-0]     97.716464 s:  [ IPC_IN_0 ] Link Statistics,
[IPU1-0]     97.716525 s:  ******************************
[IPU1-0]     97.716616 s: 
[IPU1-0]     97.716647 s:  Elapsed time       = 25211 msec
[IPU1-0]     97.716708 s: 
[IPU1-0]     97.716769 s:  Get Full Buf Cb    =   4.95 fps
[IPU1-0]     97.716830 s:  Put Empty Buf Cb   =   5.71 fps
[IPU1-0]     97.716921 s:  Driver/Notify Cb   =   5.75 fps
[IPU1-0]     97.717013 s: 
[IPU1-0]     97.717043 s:  Input Statistics,
[IPU1-0]     97.717104 s: 
[IPU1-0]     97.717165 s:  CH | In Recv | In Drop | In User Drop | In Process
[IPU1-0]     97.717257 s:     | FPS     | FPS     | FPS          | FPS       
[IPU1-0]     97.717348 s:  --------------------------------------------------
[IPU1-0]     97.717440 s:   0 |   5.75      0. 0      0. 0           5.75
[IPU1-0]     97.717653 s:  chId:  0 | inBufRecvCount: 145 |inBufDropCount: 0 |inBufUserDropCount: 0 |inBufProcessCount: 145
[IPU1-0]     97.717775 s: 
[IPU1-0]     97.717836 s:  Output Statistics,
[IPU1-0]     97.717897 s: 
[IPU1-0]     97.717928 s:  CH | Out | Out     | Out Drop | Out User Drop
[IPU1-0]     97.717989 s:     | ID  | FPS     | FPS      | FPS          
[IPU1-0]     97.718080 s:  ---------------------------------------------
[IPU1-0]     97.718172 s:   0 |  0      5.75     0. 0      0. 0
[IPU1-0]     97.718324 s: 
[IPU1-0]     97.718355 s:  [ IPC_IN_0 ] LATENCY,
[IPU1-0]     97.718416 s:  ********************
[IPU1-0]     97.718477 s:  Local Link Latency     : Avg =     28 us, Min =      0 us, Max =     61 us,
[IPU1-0]     97.718599 s:  Source to Link Latency : Avg = 148056 us, Min =  52065 us, Max = 252242 us,
[IPU1-0]     97.718690 s: 
[IPU1-0]     97.718751 s:  realtime =      0 us
[IPU1-0]     97.718812 s:  avgtime  =      0 us
[IPU1-0]     97.718873 s:  totalCnt =      0  
[IPU1-0]     97.719026 s: 
[IPU1-0]     97.719056 s:  ### CPU [  EVE2], LinkID [ 54],
[IPU1-0]     97.719178 s: 
[IPU1-0]     97.719239 s:  [ ALG_TIDL ] Link Statistics,
[IPU1-0]     97.719300 s:  ******************************
[IPU1-0]     97.719361 s: 
[IPU1-0]     97.719422 s:  Elapsed time       = 25214 msec
[IPU1-0]     97.719483 s: 
[IPU1-0]     97.719514 s:  New data Recv      =   4.95 fps
[IPU1-0]     97.719605 s: 
[IPU1-0]     97.719636 s:  Input Statistics,
[IPU1-0]     97.719697 s: 
[IPU1-0]     97.719727 s:  CH | In Recv | In Drop | In User Drop | In Process
[IPU1-0]     97.719819 s:     | FPS     | FPS     | FPS          | FPS       
[IPU1-0]     97.719880 s:  --------------------------------------------------
[IPU1-0]     97.719971 s:   0 |   0.79      0. 0      0. 0           4.91
[IPU1-0]     97.720093 s:  chId:  0 | inBufRecvCount: 20 |inBufDropCount: 0 |inBufUserDropCount: 0 |inBufProcessCount: 124
[IPU1-0]     97.720520 s: 
[IPU1-0]     97.720581 s:  Output Statistics,
[IPU1-0]     97.720642 s: 
[IPU1-0]     97.720673 s:  CH | Out | Out     | Out Drop | Out User Drop
[IPU1-0]     97.720764 s:     | ID  | FPS     | FPS      | FPS          
[IPU1-0]     97.720825 s:  ---------------------------------------------
[IPU1-0]     97.720917 s:   0 |  0      4.91     0. 0      0. 0
[IPU1-0]     97.721039 s: 
[IPU1-0]     97.721069 s:  [ ALG_TIDL ] LATENCY,
[IPU1-0]     97.721191 s:  ********************
[IPU1-0]     97.721252 s:  Local Link Latency     : Avg = 201308 us, Min = 199781 us, Max = 203563 us,
[IPU1-0]     97.721374 s:  Source to Link Latency : Avg = 335289 us, Min = 252455 us, Max = 425029 us,
[IPU1-0]     97.721496 s: 
[IPU1-0]     97.721527 s:  realtime =      0 us
[IPU1-0]     97.721588 s:  avgtime  =      0 us
[IPU1-0]     97.721649 s:  totalCnt =      0  
[IPU1-0]     97.721801 s: 
[IPU1-0]     97.721832 s:  ### CPU [  EVE2], LinkID [  0],
[IPU1-0]     97.721893 s: 
[IPU1-0]     97.721954 s:  [ IPC_OUT_0 ] Link Statistics,
[IPU1-0]     97.722015 s:  ******************************
[IPU1-0]     97.722076 s: 
[IPU1-0]     97.722442 s:  Elapsed time       = 25015 msec
[IPU1-0]     97.722625 s: 
[IPU1-0]     97.722686 s:  New data Recv      =   4.95 fps
[IPU1-0]     97.722747 s:  Release data Recv  =   4.91 fps
[IPU1-0]     97.722839 s:  Driver/Notify Cb   =  14.95 fps
[IPU1-0]     97.722930 s: 
[IPU1-0]     97.722961 s:  Input Statistics,
[IPU1-0]     97.723022 s: 
[IPU1-0]     97.723052 s:  CH | In Recv | In Drop | In User Drop | In Process
[IPU1-0]     97.723571 s:     | FPS     | FPS     | FPS          | FPS       
[IPU1-0]     97.723662 s:  --------------------------------------------------
[IPU1-0]     97.723754 s:   0 |   4.95      0. 0      0. 0           4.95
[IPU1-0]     97.723876 s:  chId:  0 | inBufRecvCount: 124 |inBufDropCount: 0 |inBufUserDropCount: 0 |inBufProcessCount: 124
[IPU1-0]     97.724028 s: 
[IPU1-0]     97.724059 s:  Output Statistics,
[IPU1-0]     97.724120 s: 
[IPU1-0]     97.724211 s:  CH | Out | Out     | Out Drop | Out User Drop
[IPU1-0]     97.724303 s:     | ID  | FPS     | FPS      | FPS          
[IPU1-0]     97.724364 s:  ---------------------------------------------
[IPU1-0]     97.724455 s:   0 |  0      4.95     0. 0      0. 0
[IPU1-0]     97.724547 s: 
[IPU1-0]     97.724608 s:  [ IPC_OUT_0 ] LATENCY,
[IPU1-0]     97.724669 s:  ********************
[IPU1-0]     97.724730 s:  Local Link Latency     : Avg =     18 us, Min =      0 us, Max =     92 us,
[IPU1-0]     97.724821 s:  Source to Link Latency : Avg = 335992 us, Min = 253035 us, Max = 425913 us,
[IPU1-0]     97.724943 s: 
[IPU1-0]     97.724974 s:  realtime =      0 us
[IPU1-0]     97.725035 s:  avgtime  =      0 us
[IPU1-0]     97.725096 s:  totalCnt =      0  

Part Number: TMS320C6747

Tool/software: TI C/C++ Compiler

Hello Mr. Rahul

I examined your information and decided to retry with ccsv4. It is also a platform error. Do you need to set memory map and other settings? At this time, we will send a summary of ccsv4 installation settings, platform errors, and memory. Can you tell me how to set up ccsv4?

Best Regards

Suzuki

Part Number: AMIC110

Part Number: TDA3MV

Tool/software: TI-RTOS

Dear Champs,

My customer would like to understand the details how 3D SRV can be implemented on DSP of TDA3 and what is the difference between DSP implementation and GPU's.

Could you please provide details what is the view point in the TDA3 3D SRV? is it same as 'virtual camera point'?

When 'view turn around' is implemented, does intermediate images used in this view turn around can be generated using LUT table in each view points?

My customer normally requires hundreds views to implement 3D SRV, and want to know how it can be implemented on TDA3 and how much memory size will be required.

When I checked marketing slides, I found 9 view point implementation case and 21 view point implementation.

When view point was increased, what is the benefit with this many view points?

I found about 1.3MBytes is required for 1 view point in the VisionSDK datasheet, but I found 32MB required for 9 view point and 64MB required for 21 view points.

Then, the actual size of 21 view points case should be 32MB(9 view points) + 1.3MB x 12 view points = 47.6MB, right?

And, my customer also wants to implement auto calibration and want to know if there is an additional resource to implement this auto calibration(online calibration).

in this case, is it possible to extract 'Motion' like 'Optical Flow' from 4ch input videos at run-time?

If so, could you please provide details how this Motion can be implemented and its processing time and how many motion can be extracted?

Thanks and Best Regards,

SI.

Part Number: AM4376

Hi,

We are in advanced stage of our product development. As of now our system (based on the AM4376 EVM SK) is booting from SD card and we want to change it to network boot.

We are well aware that current TI RTOS tools and bootloader does not support network boot, but we have already have our own solution.

But here is the big issue: We we set the boot option resistors on the system board to support network boot, It looks like the network of our SW (Based on TI RTOS drives) is not working properly any more. It looks like we can receive packets, but we can not send packets. (we used wireshark to monitor trafic and no packet is sent). This has nothing to do with the network boot, as even if we load our software using the debugger and Code Composer, we have the same issue. On a board that is not configured to network boot, the software works fine using same debugging procedure.

It is not a hardware issue, as the ROM bootloader does send BOOTP and TFTP packets. But when we start our TI RTOS software, packets are not sent (link is detected fine, and incomming packets are fine as well). As said, on a board without network boot option, everything works fine.

My question, is it possible that the ROM bootloader when set to network boot, places the EMAC system in a state that TI RTOS can not work with, or does not support? We have dumped all CPSW registers on startup on both boards to compare, we have found some minor changes, but even if we set them back to be the same, the problem persists. Is there anything else we can do to track the issue?

Thank you!

shai

Part Number: AM5728

HI,

I am trying to build and run an example code that involves IPC between M4 and A15 on AM5728. So far I managed to run the "ex02_messageq" example and got the right output (according to Processor SDK RTOS guide).

Now I'd like to proceed and move onto some more 'complex' examples (blinking an LED using M4). I ended up in the following section in the SDK RTOS guide:

http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_how_to_guides.html#adding-ipc-to-an-existing-ti-rtos-application-on-slave-cores

1) The text refers to "GPIO_LedBlink_evmAM572x_c66xExampleProject" that is supposed to be located at "ti/pdk_am57xx_1_0_4/packages/MyExampleProjects". There is no such a folder in SDK RTOS 06_00_00_07.

2)  I found a folder named "led_blink" at "/home/fsi/ti/pdk_am57xx_1_0_15/packages/ti/drv/gpio/test". This looks like a replacement of the above-mentioned example. Am I right?

3) I tried running the "pdkProjectCreate.sh" script hoping I'd end up with a CCS project of the "led_blink" example code. The script fails because it's apparently searching for the obsolete folder structure ("packages/MyExampleProjects").

4) I tried setting up the built environment for PDK and then building the "led_blink" example using the makefile at "/home/fsi/ti/pdk_am57xx_1_0_15/packages/ti/drv/gpio/test/led_blink/makefile". This gives me the following error:

/home/fsi/ti/pdk_am57xx_1_0_15/packages/ti/build/makerules/common.mk:367: /home/fsi/ti/pdk_am57xx_1_0_15/packages/ti/build/makerules/rules_r5f.mk: No such file or directory
make: *** No rule to make target '/home/fsi/ti/pdk_am57xx_1_0_15/packages/ti/build/makerules/rules_r5f.mk'. Stop.

HOST: Ubuntu 16.04, 64 bit

TARGET: BeagleBoard X15, rev. B1

I appreciate any help from you.

Thanks,

Filip

Part Number: AM3352

Hi,

I am using Pinmux configuration for a particular pin (gpio0_28) in DTS, I made it OUTPUT_PULLUP in MODE7 (gpio).

Then, when is issue poweroff command, the line still stays at HIGH / over 2.2V even after poweroff

For the same pin, if I configure that as gpio-leds in DTS, The line goes LOW after poweroff

Is this expected behavior ?

Also, I've noticed that when I use gpio-hog, I get around 3.3V at the gpio0_28 line

But, when configuring only pinmux in DTS, I get around 2.2V at the gpio0_28 line

FYI,

I am using custom AM3352 based board.

DTS has the following entries,

AM33XX_IOPAD(0x928, PIN_OUTPUT_PULLUP | MUX_MODE7) /* (K17) mii1_txd0.gpio0[28] */

&gpio0 {
        gpio-28{
                gpio-hog;
                gpios = <28 GPIO_ACTIVE_HIGH>;
                output-high;
                line-name = "gpio-28";
        };
};

Part Number: AM5728

Hello,

I having some issues with a custom video encoding application and wanted to know if there's a sample application which incorporates h264/h265 video encoding as part of PSDK 5_03 release.

Regards,

Nikhil

Part Number: PHYTC-3P-PHYCORE-AM65X

Hi,

Where can I find documentation on how to use and setup the TSN features of AM65x?

Kind regards,

Carl

Part Number: TDA2P-ACD

Dear All,

I have  some question about the performance of ssdJacintoNetV2 on TDA2P.

When using the trained model(ssdJacintonetV2 768x320), the performance works at 15 fps, but when I use the model I've learned by script, the performance drops to about 11 fps.

According to related deploy files, It look like the trained model has 5 heads, but the training model is 6.

So I tried that the heads reduce from 5 to 5.(refer attached deploy file)

but FPS is still 11.

Is the cause I thought wrong? How can I increase the fps to 15?

pls refer my development environment as below.

SDK3.6.0.0

caffe-jachinto 0.17

caffe-jacinto-model 0.17

bootmode : SD boot

// key changes based on train_image_object_detection.sh

model_name=ssdJacintoNetV2

resize_width=768
resize_height=320
crop_width=768
crop_height=320
use_difficult_gt=0
small_objs=1
ker_mbox_loc_conf=1

num_classes=4
chop_num_heads=1

use_batchnorm_mbox=1

attached file(deploy.prototxt:logfile) :   (Please visit the site to view this file)

Thank you.

BR,

Khethan

Part Number: AM5728

Tool/software: Code Composer Studio

Hi

I have generated the files using pinmux tool for the AM5728 as per the custom board design requirement.I am using CCS Version: 9.1.0.00010 .

Please guide me how to incorporate/load these files into the CCS.What is the right procedure?

Thanks in advance.

Part Number: AM5728

Hi

I have generated the files using pinmux tool for the AM5728 as per the custom board design requirement.I am using CCS Version: 9.1.0.00010 .

Please guide me how to incorporate/load these files into the CCS.What is the right procedure?

Thanks in advance.

Part Number: AM5728

Hi,

I used the EMIF_RegisterConfiguration.xlsm for the change in the DDR gel file of the AM5728.

Please guide me what all the changes to be done in the DDR GEL file.send me the screen shot if available.

Thanks

Part Number: 66AK2H14

Hi,

This question follows the answer given on the related post talking about DDR cacheability. Now I would like to show you another, strange difference between DDR cacheable and non-cacheable.

In fact, I keep the code of the related post but without using the verification function causing some cache issue (a priori), in my test I realized only write accesses from DSP to DDR cacheable and non cacheable, there is nothing in L1cache. All write command pass through write buffer.

Even code are expecting to have same results,  results are different, it is very stranged:

This figure has been obtained using -o3 option. In -off option, cacheable and non cacheable give same results:

The only difference, I saw between DDR cacheable and non cacheable is the number of access realized in the DDR memory controller:

opt : -o3

dbg : -oOff

C: DDR cacheable

NC : DDR non cacheable

If anyone could give me an explanation, it would really help me !!

Regards,

François

PS :  if you  need other information, tell me

Part Number: AM3359

Hi everyone,

I'm working on a Product based on the am3359 using dual ethernet via prueth. Both PHYs are TI DP83822, and they recognized correct and are working just fine in Linux.

There is only one problem: I'd like to configure the PHY LED, which requieres me to configure two registers of the PHY.

Is there any way to access the registers from Linux, or how can i write to them?

Thanks in advance,

Dave

Part Number: AM5728

Part Number: AM5728

Dear Sir,

Board---Custom AM5728 Board

We are designing Custom AM5728 Board purpose of HD video annotation using h.264 CODEC. Due to space constraints we are not able to put eMMC /SD card. Only we are using QSPI FLASH.

Based on this design booting from QSPI Flash will happens or not without using eMMC/SD Card.

Thanking  you,

Regards,

Ramachandra P C.

Part Number: AM5728

Hi teams,

I'm using AM572x IDK for logistics robots demo.

But the USB1 can not work.

I have already created an SD card and boost up the EVM successfully.

The problem is:

The terminal of AM572x IDK shows no serial is detected when I tried to connect another device to AM57x through USB1. 

Could you help me check if there is any problem with the USB port hardware?

Thanks!