Part Number:PROCESSOR-SDK-AM335X

Tool/software: Linux

Hi,

question on the processor-sdk. we are rebuilding the sdk with some minor changes, got what we wanted but also found that i cannot connect to the BBB through the USB. the original kernel come with BBB i think it's a debian, i have no problem to connect the BBB through USB and ssh into it. but for the new build, i cannot, and i don't think the prebuild processor-sdk work neither. any one know anything about this?

thanks you!

-Yue

Part Number:TDA2EVM5777

Tool/software: TI-RTOS

Hi, 

I got a one question about detection output layer in TIDL Network (JDetNet).

In deploy.prototxt file, there is nms_param and keep_top_k in detection_output_param section.

Does it means detection output layer apply NMS and return the output buffer which is consists of top 20 detected objects?

Besides, could you let me know what is the meaning of keep_top_k? (top_k objects in order of high confidence? or just detected order)

Thanks & Regards,

Yoo.

Part Number:AM3358

Tool/software: Linux

I am trying to port Android in my micro SD card (16GB), however the same when used in Sitara couldn't be booted with Android. The following are the sequence of steps followed as per document -

Part Number:TDA2PXEVM

Tool/software: Linux

Dear,

I'd like to disperse the DSP1 load to DSP2.

My usecase is below.

If I test this with many person to detect pedestrian, the DSP1 load shows over 100%.

But, the DSP2 load shows about 20~25%.

<usecase>

IssCapture -> IssM2mIsp -> IssM2mSimcop -> Alg_ImagePreProcess (EVE2) -> Dup_capture -> Merge_alg

IssM2mIsp -> Alg_IssAewb

Dup_capture -> Alg_ImgPyramid -> Dup_imgPyramid -> Alg_FPCompute (EVE1) -> Alg_ObjectDetection (DSP1) -> Merge_objectDetect (DSP2)

Dup_imgPyramid -> Merge_objectDetect (DSP2) -> Sync_objectDetect (DSP2) -> Alg_ObjectClassification (DSP2) -> Merge_alg -> Sync_alg -> Alg_ObjectDraw -> Display_alg

Dup_imgPyramid -> Alg_LaneDetect (DSP2) -> Merge_alg

GrpxSrc -> Display_Grpx

I think that the Alg_ObjectDetection is bottleneck.

How can I disperse this DSP1 load to another DSP2?

BR,

Heechang

Part Number:PROCESSOR-SDK-AM65X

Tool/software: Linux

Hi,

I am trying to build  linux for AM65x using this steps.

In between I came across with this error.

ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_configure, the basehash value changed from f2d4cf59f0735e926389cdb33c1812f1 to b3d016ab35a13c6491b48827a3dcb468. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_compile, the basehash value changed from 992dfaaa1fed78ab75e1d63cdf83d713 to 5d5856cdadea75f4369b382d250fb28a. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_configure, the basehash value changed from f2d4cf59f0735e926389cdb33c1812f1 to b3d016ab35a13c6491b48827a3dcb468. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_compile, the basehash value changed from 992dfaaa1fed78ab75e1d63cdf83d713 to 5d5856cdadea75f4369b382d250fb28a. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_configure, the basehash value changed from f2d4cf59f0735e926389cdb33c1812f1 to b3d016ab35a13c6491b48827a3dcb468. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_compile, the basehash value changed from 992dfaaa1fed78ab75e1d63cdf83d713 to 5d5856cdadea75f4369b382d250fb28a. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_configure, the basehash value changed from f2d4cf59f0735e926389cdb33c1812f1 to b3d016ab35a13c6491b48827a3dcb468. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_compile, the basehash value changed from 992dfaaa1fed78ab75e1d63cdf83d713 to 5d5856cdadea75f4369b382d250fb28a. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_configure, the basehash value changed from f2d4cf59f0735e926389cdb33c1812f1 to b3d016ab35a13c6491b48827a3dcb468. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_compile, the basehash value changed from 992dfaaa1fed78ab75e1d63cdf83d713 to 5d5856cdadea75f4369b382d250fb28a. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_configure, the basehash value changed from f2d4cf59f0735e926389cdb33c1812f1 to b3d016ab35a13c6491b48827a3dcb468. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_compile, the basehash value changed from 992dfaaa1fed78ab75e1d63cdf83d713 to 5d5856cdadea75f4369b382d250fb28a. The metadata is not deterministic and this needs to be fixed.
ERROR: osal-rtos-01.00.00.14A-r0.0 do_configure: Taskhash mismatch 681e98f0f8facae9d7eabab0386a1b3d versus 1c7e520c1e69502029f8bfbc9749f1c9 for /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_configure
ERROR: Taskhash mismatch 681e98f0f8facae9d7eabab0386a1b3d versus 1c7e520c1e69502029f8bfbc9749f1c9 for /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_configure
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_configure, the basehash value changed from f2d4cf59f0735e926389cdb33c1812f1 to b3d016ab35a13c6491b48827a3dcb468. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /u/yocto/tisdk/sources/meta-ti/recipes-bsp/osal/osal-rtos_git.bb.do_compile, the basehash value changed from 992dfaaa1fed78ab75e1d63cdf83d713 to 5d5856cdadea75f4369b382d250fb28a. The metadata is not deterministic and this needs to be fixed.

I tried to resolve this error by using following commands

MACHINE=am65xx-evm bitbake ti-ipc-rtos osal-rtos -c cleanall

But still I am getting same error

Can you help me on this

Thanks and Regards,

Vishhnu

Part Number:AM5728

Tool/software: TI-RTOS

Hello!


Given:
There are EVM OMAPL138 and BeagleBoard X15 (am572x). I cannot find the firmware tools for am572x that OMAPL138 (AISgen_d800k008.exe) has. Are there tools for the BeagleBoard X15 (am572x)?

Part Number:AM6548

In AM6548 Ibis model, we have following model selector options available:

1. emmc_io_tx33ohm   33ohm DRIVER

2. emmc_io_tx66ohm   66ohm DRIVER                

3. emmc_io_tx100ohm  100ohm DRIVER

4. emmc_io_tx40ohm   40ohm DRIVER

How can we configure this in RTOS. What is the default setting available.

Regards,

Sushruta

50ohm DRIVER

Part Number:TMDXIDK5718

Part Number:PROCESSOR-SDK-AM57X

Hello,

We want to know whether PROCESSOR-SDK-ANDROID-AM57X could be certified with google.
For example, could you tell me that the combination of TMDSEVM572X and PROCESSOR-SDK-ANDROID-AM57X could be certified with google without any software change?
If the combination could be certified by google, please tell me the volume of modification to pass the certification.

Best Regards,
Nomo

Part Number:TMS320C6657

Hi,

we have a custom Board with a C6657-Processor that we want to boot DIRECTLY via SPI from a NAND-Flash. So no IBL, just the RBL.
The Mainquestion is: Is it possible to directly boot the C6657 RBL from a NAND-Flash connected via SPI?
Searching for a couple of days, so far I could only find examples booting from a NOR-Flash via SPI or booting from a NAND-Flash via EMIF.

This is our current Situation:

The Processor will initialize the SPI-Boot and get some Data from the NAND-Flash (Clocking for about 2 ms), but the Program in the Flash won't be executed properly.
We tried flashing the exact same Image to the NOR-Flash on the EVM-Board and the Processor executes it as expected (SPI is clocking for 123 ms). 

Our Bootpins are Configured as follows:

PIN -1:   1 (littleendian)
PIN 00:  0 (SPI)
PIN 01:  1 (SPI)
PIN 02:  1 (SPI)
PIN 03:  0 (Image-Offset)
PIN 04:  0 (Image-Offset)
PIN 05:  0 (Image-Offset)
PIN 06:  0 (Image-Offset)
PIN 07:  0 (CS0)
PIN 08:  1 (CS0)
PIN 09:  0 (16-bit Addresses)
PIN 10:  0 (4Pin SPI)
PIN 11:  0 (SPI-Mode 2)
PIN 12:  1 (SPI-Mode 2)

We are using this Flash: W25N01GVZEIG with 1Gbit Memory. The Flash is configured in continuous-Mode, so a single Read-Instruction will read the entire Image. In the Datasheet this mode is said to accomplish compatibility to their NOR-Flash Instructions.

The Image is created using these instructions http://au.tono.my/log/20140117-c6657-spi-boot.html and flashed to Page 0 from a C2000-Processor.

So the Questions would be 
 Is it possible to directly boot the C6657 RBL from a NAND-Flash connected via SPI?
and 
What exactly does Bootconfig-Pin 9 express? What are the 16/24Bit-Adresses? And where in the Flash-datasheet can I find this Value?
and
maybe how would one debug the RBL-Bootloader? How can I read the debug log messages stated in the RBL-sourcecode?

Thank you and regards
Oliver

Part Number:AM6548

Hi TI engineers

Today I learned a conception callde AMP(Asynchronous Multi-Processors) and SMP(Synchronous Multi-Processors)

and the SOC that I'am using is AM6548, it has two R5F and two A53.

I want to know that as for the two R5F, it's AMP or SMP?

Best Regards

Hope Chen

Part Number:TMS320C6678

Tool/software: Code Composer Studio

Hi

I'm testing PCIe interrupt for the PCIEXpress_Legacy_INTA.

MCSDK 2.1.2.6

CCS 8.3

Example project : C:\ti\pdk_C6678_1_1_2_6\packages\ti\drv\exampleProjects\PCIE_exampleProject

I added isr routine and setting(in cfg) in the PCIE_exampleProject

< Added cfg set-up and PCIe interrupt status(memory browser) >

As see abobe occure interrupt but not work ISR

The above experiment is intended to menual test incoming interrupts using RC mode in a PCIe example project with evmc6678.

A manual interrupt was generated and tested using 1 in the Raw Interrupt Status Register (0x21800180).

In the example provided, the Interrupt Enabled Status Register shows that an interrupt has occurred.
However, they did not jump to ISR.

Do you need any other settings?

Part Number:AM4376

Tool/software: TI-RTOS

Hello,

There are problems with outgoing packet in HSR mode when payload contains VLAN tag. 

SDK RTOS 5.03.00.07 is used. PRU-ICSS-HSR-PRP-DAN 01.00.04.02 is used.

Message to send (VLAN tag + GOOSE), 86 bytes:

81    00    80    00   88    B8    00    00    00    50    00    00    00    00    61    46   
80    07    67    6F    43    62    52    65    31    81    02    0B    B8    82    06    64   
61    74    53    65    74    83    04    67    6F    49    64    84    08    48    88    90   
C1    24    00    00    27    85    01    01    86    02    00    CD    87    01    00    88   
01    78    89    01    00    8A   01    03    AB    0C     A2    80    84    03    00    80   
00    83    01   00     00    00

Outgoing packet:

01    0C    CD    01    00    01    60    64    05    62    5E    F2    81    00    80    00
89    2F    00    5A    01    FD   81    00    80    00    88    B8    00    00    00    50
00    00    00    00    61    46    80    07    67    6F    43    62    52    65    31    81
02    0B    B8    82    06    64    61    74    53    65    74    83    04    67    6F    49
64    84    08    48    88    90    C1    24    00    00    27    85    01    01    86    02
00    CD    87    01    00    88    01    78    89    01    00    8A   01    03    AB    0C
A2    80    84    03    00    80    00    83

MAC's - black, added by PRU HSR firmware VLAN tag - red, HSR tag - blue, payload - green.

Problems:
1. Additional VLAN tag (red colored) has been added before HSR tag (blue colored), so there are two VLAN tag in packet (underscored). PRU HSR firmware on recieving side  does not accept such packets.

2. Last 4 bytes of payload (01 00 00 00) are not sent.

If payload does not contain VLAN tag outgoing packet is successfully accepted by recieving side.

PRU HSR firmware successfully accepts the following packets:
- MAC's + VLAN tag + HSR tag + payload (without VLAN tag)
- MAC's + HSR tag + VLAN tag + payload (without VLAN tag)
- MAC's + HSR tag + payload (without VLAN tag)

Thanks, Alexey.

Part Number:AM3352

Tool/software: Linux

Hi all,

My linux kernel is :linux-4.14.79+gitAUTOINC+bde58ab01e-gbde58ab01e

PROBLEM :hwclock is ok,date is error.

Why no printf info as below:

omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
omap_rtc: already running

My linux config about RTC as below:

CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_SYSTOHC_DEVICE="rtc0"
CONFIG_RTC_DEBUG=y
CONFIG_RTC_NVMEM=y

CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y

CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1307_HWMON=y

CONFIG_RTC_DRV_PALMAS=m
CONFIG_RTC_DRV_TPS6586X=m
CONFIG_RTC_DRV_TPS65910=m

CONFIG_RTC_I2C_AND_SPI=y

CONFIG_RTC_DRV_EFI=m

CONFIG_RTC_DRV_OMAP=y

CONFIG_DMADEVICES=y

My dts:

&rtc{

status=okay;

}

Best regards

Part Number:AM3358

Hello.

I have newly designed a custom board based on TMDXEVM3358 (AM3358 GP ?).

I removed unnecessary parts and changed DDR3 RAM.

The main parts are as blows.

1. MPU : AM3358BZCZ80 

2. RAM : MT41K512M8DA107AITP,  2ea,  

https://www.micron.com/products/dram/ddr3-sdram/part-catalog/mt41k512m8da-107-it

3. Flash : MT29F2G08ABAEAH4, 1ea

I applied MT41K512M8DA-107 as a DDR3 RAM instead  of MT41K512M8DA-125 in the  TMDXEVM3358.

I had been trying to interface DDR3 as explained in the tutorials below:

http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_Tuning_the_DDR3_Timings_on_BeagleBoneBlack

http://processors.wiki.ti.com/index.php/AM335x_EMIF_Configuration_tips

When I run the 'DDR3_slave_ratio_search_auto.out', I have always got 0x00 for console output. ( attached it blow)

And I had tried to modify the momory value between 0x80000000 and 0xBFFFFFFF, value didn't stick and kept changing.

I tried to change Ratio speed and register value, but it kept showing same result(0x00).

I would like to attach some files for your review.

1. GEL file

(Please visit the site to view this file)

2. Connection Log file by using above GEL file

(Please visit the site to view this file)

3. .AM335x_DDR_register_calc_tool.xls

(Please visit the site to view this file)

4. RatioSeed_AM335x_boards.xls

(Please visit the site to view this file)

5. DDR3_slave_ratio_search_screenShot

6. ddr analysis script Log

(Please visit the site to view this file)

I would like to ask you some questions as blows.

1.  Can I use micron MT41K512M8DA-107 ?

2. What should I check my board to clear this issue?

    => I have checked PCB Artwork and I didn't find any deviation for  the Datasheet 7.7.2 ~ .

    => Should I change the terminal resistor value as fit as my design?

         ( I use  47R and 49.9R for terminal resistor as same as reference sch on TMDXEVM3358. )

3. Do I make any mistakes for ration/resistor excel sheet?

  => I have changed a lot of times.... but same result.... only 0x00 

Thank you in advance.

Part Number:AM5728

Tool/software: TI-RTOS

Hello,

I discovered that the FATFS_Console_idkAM572x_armExampleProject of the SDK-RTOS-05.03.00.07 crashes when inserting or removing the microSD-Card. This happens when booting from the SD-Card directly as well when executing the demo from CCS and the XDS560 debugger.

The idkAM572x.ccxml:CIO output is:

[CortexA15_0] ti.sysbios.knl.Semaphore: line 300: assertion failure: A_badContext: bad calling context. Must be called from a Task.
xdc.runtime.Error.raise: terminating execution

The crash happens in the "AppGpioCallbackFxn"

Do you have a suggestion how to fix this?

Thanks a lot for your help,

Bernd Sprenger

Part Number:AM5718

Tool/software: TI-RTOS

I have custom board based on AM5718 and now developing custom bootloader and application based on TI-RTOS with video capture and HDMI display functionality using source code from pdk_am57xx_1_0_14.

I use idkAM571x board as a reference and debug platform. I have some troubles running VPS Loopback Example on idkAM571x board. Project was created using pdkProjectCreate.sh script and built with Code Composer Studio 8.3. When loading example with JTAG everything works just fine, I can see picture from camera on external mini-board on HDMI display.

But it hangs when booting from MicroSD card. I tried to use precompiled bootloader pdk_am57xx_1_0_14/packages/ti/boot/sbl/binary/idkAM571x/mmcsd/bin/MLO. This bootloader loads and runs app, but executions stucks in LpbkApp_init function with debug output "hal/src/vpshal_dssDispcOvly.c @ Line 2880: DSS Still in reset".

It seems that GEL files through JTAG setup something inside display subsystem of AM5718 which booloader does not do. Please tell me what can that be?

Regards.

Part Number:DRA76P

Hi,

We've designed a new PCB based on DRA76P. We only supply VDDSHV8 (MMC1) with 3V3 and not with dual supply as EVM does. Now, we're rewriting the DTS file, based on the files from the EVM. On the dra7.dtsi file, we've found something that seems to be the dual voltage supply for the MMC1 interface: 

pbias_regulator: pbias_regulator {
	compatible = "ti,pbias-dra7", "ti,pbias-omap";
	reg = <0xe00 0x4>;
	syscon = <&scm_conf>;
	pbias_mmc_reg: pbias_mmc_omap5 {
		regulator-name = "pbias_mmc_omap5";
		regulator-min-microvolt = <1800000>;
		regulator-max-microvolt = <3300000>;
	};
};

As we only need the 3V3, we should set regulator-min-microvolt = <3300000>, is't?

Regards,

Part Number:AM6548

Tool/software: Linux

Hi,

I have following queries related to V4L2 driver for CAL support.

• The Processor SDK for Linux does include the V4L2 drivers for CAL. However, the note in the same suggests them as not validated on AM65xx. More details on its validation status in AM65xx would be helpful.

• Does the Linux V4L2 driver for CAL (CSI-2 port) support splitting the incoming frames in different virtual channels of CSI port ?

• Does the driver support receiving 4 input frames, from different virtual channels, simultaneously ?

Thanks,

Suryaprakash Rao G

Part Number:DRA80XMEVM

Dear expert,

Customer are survey our DRA90XM in their automotive application.

For power solution, we don't have Q grade PMIC solution now.( as you can find in below E2E post)

http://e2e.ti.com/support/power-management/f/196/p/813678/3012733#3012733

Did you have suggested power solution with Q grade?

Here is my email address. We can have more discussion off-line. Thanks!

benkuo@ti.com

Regards,

Ben