TMDSIDK437X: RTE tracer

Hi Drew,

Are you using the following versions of the dependence software package for building the RTE_Tracer_ARM_NDK as listed in the  TIDEP0064  document?

• RTOS Processor SDK 1.0.3 for AM437x IDK
• Industrial SDK 2.1.1.2
– SYS-BIOS (refer to Industrial SDK release notes)
– XDC-Tools (refer to Industrial SDK release notes)
• NDK 2.25.0.09 (refer to NDK release notes and NDK reference guide)

Regards,
Garrett

Hi Garrett,

I believe that I have all of the correct products and tools installed. Some are a later version as you can see in the screen shots below.

Is there are binary available for this tracer product so I don't have to build it?  We only want to use the tracer board as a tracer for SORTE development.

If not and we need to build it, here are the items installed:

From the features tab or the installed software tab on help:

am437x PDK 1.0.16

XDCtools IDE Tooling 3.55.2.22

XDCtools Embedded Runtime 3.55.2.22

Sys/BIOS Embedded Runtime 6.76.2.02

NDK 2.25.0.09

The file nimu_idk.cfg is excluded from the build when I import the project.

The error I get when I include nimu_idk.cfg is as follows:

When I exclude the file nimu_idk.cfg then I get the following errors:

What am I missing?

Thanks,

Drew

It doesent look like the screen shot worked: Below is a copy of the error warnings:

With nimu_idk.cfg excluded

Description    Resource    Path    Location    Type
Field 'baseAddr' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 430    Semantic Error
Field 'baseAddr' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 505    Semantic Error
Function 'PINMUXModuleConfig' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 895    Semantic Error
Symbol 'CHIPDB_MOD_ID_CPSW' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 895    Semantic Error
This project does not contain a buildable RTSC Configuration (.cfg) file. In order for it to build, this project must contain one RTSC Configuration file that is not excluded from build.    RTE_Tracer_ARM_NDK        RTE_Tracer_ARM_NDK    Problem
Type 'PRUICSS_HwAttrs' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 427    Semantic Error
Type 'PRUICSS_HwAttrs' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 502    Semantic Error
Product 'NDK' v2.24.3.35 is not currently installed. A compatible version 2.25.0.09 will be used.    RTE_Tracer_ARM_NDK        RTE_Tracer_ARM_NDK    Problem
Product 'SYS/BIOS' v6.45.1.29 is not currently installed. A compatible version 6.76.2.02 will be used.    RTE_Tracer_ARM_NDK        RTE_Tracer_ARM_NDK    Problem
Suggested parenthesis around expression 'temp32 & (1<<mdio_conf->addr0)'    main.c    /RTE_Tracer_ARM_NDK    line 513    Code Analysis Problem
This project was created using a version of compiler that is not currently installed - GNU_4.9.3:Linaro [ARM]. Another version of the compiler will be used during build - GNU_7.2.1:Linaro. See 'Help > Install New Software' and select 'Code Generation Tools Updates' to check if this compiler is available through a CCS update. Visit <a href="liveaction:OpenAppCenter">CCS App Center</a> to get the latest compiler support. Or <a href="software-dl.ti.com/.../a> and install the compiler, then register it with CCS through 'Preferences > CCS > Build > Compilers'.    RTE_Tracer_ARM_NDK        properties    Problem

With nimu_idk.cfg included:

Description    Resource    Path    Location    Type
Field 'baseAddr' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 430    Semantic Error
Field 'baseAddr' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 505    Semantic Error
Function 'PINMUXModuleConfig' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 895    Semantic Error
gmake: *** [build-1585926671] Error 2    RTE_Tracer_ARM_NDK             C/C++ Problem
gmake: Target 'all' not remade because of errors.    RTE_Tracer_ARM_NDK             C/C++ Problem
gmake[1]: *** [build-1585926671-inproc] Error 1    RTE_Tracer_ARM_NDK             C/C++ Problem
recipe for target 'build-1585926671-inproc' failed    subdir_rules.mk    /RTE_Tracer_ARM_NDK/Release    line 19    C/C++ Problem
recipe for target 'build-1585926671' failed    subdir_rules.mk    /RTE_Tracer_ARM_NDK/Release    line 16    C/C++ Problem
Symbol 'CHIPDB_MOD_ID_CPSW' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 895    Semantic Error
ti.sysbios.BIOS: incompatible assignment to kernelHeapSection : ".kernel_heap"    .xdchelp    /RTE_Tracer_ARM_NDK    line 926    C/C++ Problem
Type 'PRUICSS_HwAttrs' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 427    Semantic Error
Type 'PRUICSS_HwAttrs' could not be resolved    main.c    /RTE_Tracer_ARM_NDK    line 502    Semantic Error
Product 'NDK' v2.24.3.35 is not currently installed. A compatible version 2.25.0.09 will be used.    RTE_Tracer_ARM_NDK        RTE_Tracer_ARM_NDK    Problem
Product 'SYS/BIOS' v6.45.1.29 is not currently installed. A compatible version 6.76.2.02 will be used.    RTE_Tracer_ARM_NDK        RTE_Tracer_ARM_NDK    Problem
Suggested parenthesis around expression 'temp32 & (1<<mdio_conf->addr0)'    main.c    /RTE_Tracer_ARM_NDK    line 513    Code Analysis Problem
This project was created using a version of compiler that is not currently installed - GNU_4.9.3:Linaro [ARM]. Another version of the compiler will be used during build - GNU_7.2.1:Linaro. See 'Help > Install New Software' and select 'Code Generation Tools Updates' to check if this compiler is available through a CCS update. Visit <a href="liveaction:OpenAppCenter">CCS App Center</a> to get the latest compiler support. Or <a href="software-dl.ti.com/.../a> and install the compiler, then register it with CCS through 'Preferences > CCS > Build > Compilers'.    RTE_Tracer_ARM_NDK        properties    Problem

Drew,

It appears to be some software component compatibility issue. The tracer software was developed in 2016 whereas its dependence packages have evolved...

let me try to find a binary for you.

Regards,

Garrett

RTE_on_PRU_ICSS_ARM_appl.out

.out file attached.

Regards,
Garrett

Hi Garrett,

We were successful at uploading the .out file that you sent us to the TMDSIDK437x board. The program runs immediately after upload from CCS. We attach the SORTE master AM3359 device to the TAP. With the master outputting discovery packets, as veried by connecting it directly to a PC running Wireshark, we are not getting any output from the Gigibit port on the TAP. We are also not getting any output to the TeraTerm that is connectd to the USB / serial port.

Also we cannot upload the .out file unless the SD card is in the TAP device. I'm not sure if that is an indicator that something is wrong.

We have no way of knowing if the TAB is running properly.

We eventully want to put the .out file on the SD card so that it can boot up and run the TAP application without CCS. We tried to conver the .out file to a .bin file but got many errors. Will this be possible to boot the TAP from the SD card without the CCS attached?

Thanks,

Drew

Drew,

Do you follow the boot procedure described in the user guide to create _ti.bin? 

http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_Foundational_Components.html#am335x-am437x

Regards,

Garrett

Hi Garrett,

We have successfully created a app_ti.bin from the .out file that you sent us. I used a load image location of 0x80000000. We renamed it to "app" and loaded it on the SD card. We created a SD card with a FAT file systems that also had the bootloader named MLO. After inserting the SD canrd and powering up the board we pressed the reset button and got the following output from the TERA_TERM:

-----------------------

StarterWare Boot Loader

BOARDInit status [0x0]

SoC                   : [AM43XX]

Core                  : [A9]

Board Detected        : [IDKEVM]

Base Board Revision   : [UNKNOWN]

Daughter Card Revision: [UNKNOWN]

Copying application image from MMC/SD card to RAM

Jumping to StarterWare Application...

------------------------------

We then tried to use the tracer. I assume that the tracer should output any traffic that passes through it. So we used it to monitor some typical network traffic for some known good "non SORTE" devices. The tracer did not pass any data through, nor did it pass it up through the TAP connection to the computer running Wireshark.

What should we do next?

Thanks,

Drew

Hi Garrett,

Has there been any progress on our tracer problem? We are stalled with any progress on our project.

Thanks,

Drew

Hi Garrett,

It appears that there has not been any progress on solving the tracer problem.

We purchased TMDSIDK437X tracer board with the singular intention of using it as a tool to develop the SORTE protocol on the AM335x ICE board. We do not want to develop both the tracer tool and the product!

So either provide us with working software, instructions on how to make the software that you sent us work or provide us with product return instruction and refund our money.

We purchased this product assuming that you would provide us with support to get it working. That has not been the case and we are disappointed in your support.

Please reply to this post or we will take other avenues to return this product.

Drew

Hi Drew,

Sorry for the late response. I have been out of office on travel, but was able to reproduce the issue you described, and reached out to the reference design designer before I left. I have just followed up with him again, will update you if any feedback tomorrow.

I will be back in office Friday, and can find out the return policy if you can provide me the order info in the worst case the trace will not be working as you expect.

Regards,

Garrett

Hi Drew,

Please find the attached .out file built with RTE_Tracer_ARM_NDK project.

RTE_Tracer_ARM_NDK.out

And here is the tool set for building the project:

http://software-dl.ti.com/processor-sdk-rtos/esd/AM437X/03_00_00_04/index_FDS.html

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ndk/2_25_00_09/index_FDS.html

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/3_32_00_06/index_FDS.html

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/6_45_01_29/index_FDS.html

Regards,

Garrett

Hi Garrett,

Thank you for providing the .out file. We constructed the .bin file, placed it on the SD card and powered it up and it works fine. We are still working through the nuances of capturing SORTE packets. We are noticing that  Wireshark appears to miss some packets when we are in IOEX mode. I have slowed the IOEX period to 250us for these tests. This appears to be a Wireshark/host computer issue. We put a logic analyzer on the TX_EN of the tap board an no packets were skipped.

We can probably live with this. If you have any tips on increasing the performance of Wireshark, we would be thankful.

We have not yet tested data returning from the slave to the master, that is our next step.

Thank you for your support in this matter. Once we test the return data we can close this incident.

Thanks,

Drew