This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LP-AM243: Profinet stack for ALX package release date

Part Number: LP-AM243
Other Parts Discussed in Thread: AM2434, DP83869, UNIFLASH,

Tool/software:

Hello,

I'd like to ask if there are any news about release date for profinet stack for ALX package. According to my information it should be released at the end of march. Is this date still valid or should we expect any delay?

Best regrads,

Jan

  • Hi Jan,

    We will have an internal discussion and soon provide info on the release date for profinet stack for ALX package.

    Regards,
    Laxman

  • Hello Laxman,

    Thank you for your reply, I will look forward to this information.

    Best regrads,

    Jan

  • Hi Jan,

    Unfortunately, we were not able to release the AM243x ALX package to the latest Industrial Communication SDK release. As we observed few bugs, after updating to the latest baseline. However we will provide a patch drop to you on top of the latest baseline once all issues are resolved. We will also be including the ALX package support in the next release.

    Thank you for your patience,

    Best Regards,

    Laxman

  • Hello Laxman,

    On the AM243x ALX package, I'm also trying to find the profinet stack.

    You mentioned that the most recent version of the Industrial Communication SDK, 09.02.00.24 (March 30, 2025), does not include AM243x ALX.

    Am I correct?

    I would greatly appreciate it if you could send me the patch file for the AM243x ALX package's Profinet stack.



    Regards,

    Chockalingam

  • Hi Chockalingam,

    We are looking to close out few issues and complete the testing. We will discuss this internally and get back to you soon.

    Best Regards,
    Laxman

  • Hi Laxman, 

    Any input on the above patch file for AM243x. We are awaiting for your reply on when we could expect the release. 

  • Hi Aswathrangaraj,

    We are currently looking into the issues observed in the AM243x-LP with PROFINET application. We would suggest to wait for the official release which will include the AM243x ALX package support for PROFINET. This will be released during middle of May.

    Best Regards,
    Laxman

  • Hi Laxman,

    Could you please update me on the PROFINET stack release status for ALX? Has the issue been fixed?

    Regards,

    Chockalingam N

  • Hi Laxman,

    Am waiting for your response?

    Regards,

    Chockalingam

  • Hi Laxman, 

    We're facing an urgent situation regarding our client's need for the AM243x ALX package to implement the Profinet IRT protocol. This requires us to make an immediate decision.

    Given the urgency, we need to discuss providing third-party Profinet IRT stack support for the AM243x ALX package if the TI Profinet stack is experiencing technical delays.

    To provide some background, our colleague Santosh received an initial patch file from you about three months ago. We flashed the binary file, which was included in the package, onto the AM2434 LP.

    However, we've encountered an issue: the shared Profinet stack package does not contain any GSDML files. While we found GSDML files within the Industrial SDK and imported them into the PRONETA software environment for basic device testing, PRONETA failed to identify any Profinet devices when we connected the LP to the PC.

    Could you please urgently provide the correct GSDML file for testing if the SDK's GSDML file is not compatible with the shared stack patch file?

    We hope you understand the critical nature of this situation and look forward to your immediate response and support.

    Regards,

    Chockalingam N

  • Hi Chockalingam,

    The patch which we shared with Santosh is originally based on top of Industrial Communications SDK 09.02.00.15. Kindly ensure that the patch is applied on top of this version of SDK. 

    Could you please urgently provide the correct GSDML file for testing if the SDK's GSDML file is not compatible with the shared stack patch file

    The GSDML used is same for AM243x ALV and ALX package.

    Regards,
    Laxman

  • Hi Laxman,

    Thank you for your response.

    The GSDML used is same for AM243x ALV and ALX package.

    All we have to do is flash the binary image file that is part of the shared package. It flashed successfully. Next, we return to OSPI mode.

    After that, we connected our device to the PC, copied the SDK GSDML files to the Proneta GSD folder, and ran a device scan.

    We checked the network devices and chose the proper network adapter. Our devices are not recognized by it.

    Please take the same steps on your end and let me know if you encounter any issues.

    The patch which we shared with Santosh is originally based on top of Industrial Communications SDK 09.02.00.15. Kindly ensure that the patch is applied on top of this version of SDK. 

    We followed the read-me instructions found in the folder.

    Below is the error that we have. even when the library path to the project file was included. Please provide a suggestion for this.

    Regards,

    Chockalingam N

  • Hi Chockalingam,

    Regarding the build failures, this is caused due to not copying all the libraries to the CCS project path(Default location: C:\Users\<username>\<ccs_workspace_name>\profinet_device_demo_xip_am243x-lp_r5fss0-0_freertos_ti-arm-clang) . This additional workaround is required and is mentioned in the 2nd step of the readMe file.

    "2. Copy all libraries present in path: ({ind_comms_sdk_am243x_09_02_00_15_path}\source\industrial_comms\profinet_device\stack\lib) to the CCS project path."

    Could you make copy the libraries and try the build?

    Regards,

    Laxman

  • Hi Laxman,

    Thanks for the information.

    After I implemented the extra workaround, the project is now created error-free and has produced both.hs.fs and.xip images.

    As stated in the readme, the.out binary will not work properly because of an app component that is present in Flash.

    Therefore, I used UART to flash both images. After that, return to OSPI mode.

    The following prints appears in the terminal window.

    Is it okay? The CUST_PHY_dp83869.c code mentions PHY values to print, but I'm not seeing any prints in the terminal.

    I then tried to find our device in testing tools such as PRONETA (Siemens) and Profinet device monitor (Port-Command line tool).

    Our device is not recognized by it. The image file may not load properly, I believe. Additionally, I added a debug log to print the PHY values.

    I flashed the image files and repeated the process, but the terminal still showed same prints.



    Please confirm what prints we would get in the terminal after flashing the default patch file to AM2434LP without making any changes.

    Regards,

    Chockalingam

  • Hi Chockalingam,

    I have tried with the patch shared and see that the build is working fine after copying the patch to SDK 09.02.00.15. If the flashing is successful you will see these logs in the UART console.

    We could try to rule out any board related issues. Could you flash these binaries within the drive link using bootloader within the SDK and check whether you are able to detect the console logs?
     

    Drive Link: https://tidrive.ext.ti.com/u/3VD-DW9Q_kXPUP4U/0f67655e-644e-47a5-bb35-bd658cbd71a6?l 
    Access Code: 14xT!2PA

    Regards,
    Laxman

  • Hi Laxman, 
    The following prints appear in the terminal after I flashed the shared binary file using the bootloader SDK 09.02.00.15.
    The default_sbl_ospi cfg commands below, I copied the shared binaries into this location.
    # First point to sbl_uart_uniflash binary, which function's as a server to flash one or more files
    --flash-writer=sbl_prebuilt/am243x-lp/sbl_uart_uniflash.release.hs_fs.tiimage

    # Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

    # Program the OSPI PHY tuning attack vector
    --operation=flash-phy-tuning-data

    # When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
    --file=sbl_prebuilt/am243x-lp/sbl_ospi.release.hs_fs.tiimage --operation=flash --flash-offset=0x0

    # When sending application image, make sure to flash at offset 0x80000 (default) or to whatever offset your bootloader is configured for
    --file=sbl_prebuilt/am243x-lp/profinet_device_demo_xip_am243x-lp_r5fss0-0_freertos_ti-arm-clang.appimage.hs_fs --operation=flash --flash-offset=0x80000

    # send the XIP image for this application, no need to specify flash offset since flash offset is specified within the image itself
    --file=sbl_prebuilt/am243x-lp/profinet_device_demo_xip_am243x-lp_r5fss0-0_freertos_ti-arm-clang.appimage_xip --operation=flash-xip
    The execution of those commands is successful.
    Regards,
    Chockalingam
  • Hi Chockalingam,

    Looks like the complete UART log is not printed for the initialization sequence. Could you let me know which revision of AM243x-LP board are you using?

    Regards,

    Laxman 

  • Hi,

    I'm now utilizing PCB # PROC109A version of LP-AM243.

    Regards,

    Chockalingam

  • Hi Laxman,

    Today I tried with another hardware of LP-AM243x, PCB # PROC109E3 version and flashed the shared binary file using the bootloader SDK 09.02.00.15 the following prints am getting in the terminal.

    Prior to parsing default_sbl_ospi.cfg, I'm parsing default_sbl_null.cfg. Both are running successfully, but our expected prints are not appearing in the terminal.

    Regards,

    Chockalingam 

  • Hi Chockalingam,

    I would recommend to test with only PROC101A as this is the latest version of board and all the tests have been done on this board.
    As mentioned in the documentation shared with the patch, the power cycle of the device fails few times occasionally. Do you observe the issue even after multiple power resets of the device? If you have other AM243x-LP PROC101A. would it be possible to test this on different board?

    I will also test with multiple boards and check whether this issue is reproducible.

    Regards,

    Laxman

  • Hi Laxman,

    Are you referring to the most recent PROC101A board version for the AM64x/AM243x GP EVM PCB?

    For our project right now, we're using the AM2434_ALX package SoC. Is that a proper HS device? Therefore, we used the ALX package's Launchpad LP-AM243. There are only two variations that we have right now

    1.PROC109A

    2.PROC109E3

    Would you kindly confirm that the provided patch file is compatible with this?

    Regards,

    Chockalingam

  • Hi Chockalingam,

    Apologies for the confusion, I mean PROC109A board revision for AM243x-LP.

    Regards,
    Laxman

  • Hi Laxman,

    Thank you for the confirmation.

    During the board's reset, I don't even notice any power failures. Unfortunately, we don't currently have any additional LP-AM243x_PROC109A hardware.

    Have you attempted to replicate the problem on your end using different hardware?

    Regards,

    Chockalingam 

  • Hi Chockalingam,

    I have tested the binary on four AM243x LP. Two of them with model PROC109A and two of them with model PROC109E3. I see that on one of the PROC109E3 board, the intialization sequence does fail. 

    However with the PROFINET application on 11.01 baseline, I see that all the initialization steps are executed correctly on the PROC109E3 board. I am sharing another patch which includes all necessary binaries and flashing images for your testing.
    This SDK is not yet out for release and we will provide an update once this is available for public.

    Kindly run the test after following the instructions mentioned in the readMe and let us know if you face any issues.

    Drive Link: https://tidrive.ext.ti.com/u/-gFP-kgBT7XoAU_j/010e39df-89aa-4a05-a207-a369dafbff3a?l

    Access Code: Y2D2cy]U

    Regards,

    Laxman

  • Hi Laxman,

    Following the instructions in the readme, I tried your shared binaries on two AM243x-LP that we have on hand. Two of these are PROC109A and PROC109E3. Both boards are giving me different outputs, which I have included for your reference.

    1.Board - PROC109E3 - Terminal Prints

    2.Board - PROC109A - Terminal prints

    Regards,

    Chockalingam

  • Hi Chockalingam,

    The application initialization is successful in the PROC109A board based on the UART logs shared. However looks like on PROC109E3 board the issues are still observed. We would recommend to continue your testing with PROC109A board as this is the latest board version.

    Do you observe the PRONETA tool detecting the device?

    For PLC communication you can use the GSDML file from our latest Industrial Communications SDK.

    Regards,

    Laxman

  • Hi Laxman,

    We copied the most recent GSDML file from the Ind. Comm.SDK to the PRONETA tool so that we could test with our device. We also enabled the SNMP and UDP ports on our PC as instructed in the documentation. Other than that, is it necessary to set up our PC to a static IP address or something? since I can't see our device in it.

    Is there any static IP set up on our Lp-Am243x profinet slave device?

    Please give me some advice on this.

    Regards,

    Chockalingam

  • Hi Chockalingam,

    To detect the device in PRONETA, you do not need to load the GSDML in the tool. You can select the Network Analysis option and the topology should be directly visible. No need for any special configurations for IP address is required.

    Is there any static IP set up on our Lp-Am243x profinet slave device?

    By default there is no static IP address set to the device. Normally the PLC or PRONETA tool is used to set the IP address of the device.

    Do you have any other PROFINET device or PLC to check whether the tool is configured correctly?

    Regards,

    Laxman

  • Hi Laxman,

    After reconfiguring and removing the GSD from the tool background, the PRONETA tool was able to recognize our PROC109A device.

    Could you share the project patch file for the most recent binary files that were shared? With the help of the patch file, we will be able to continue developing.

    I sincerely appreciate your assistance throughout.

    Regards,

    Chockalingam

  • Hi Chockalingam,

    We are running few sanity tests on the application and will share the patch early next week after confirming the status.

    Best Regards,

    Laxman

  • Hi Laxman,

    I hope you're completing the patch application test successfully.

    Would you kindly provide us with the most recent patch file? For us, it will be really helpful.

    Thank you in advance.

    Regards,

    Chockalingam

  • Hi Chockalingam,

    Apologies for the delay in response, I have shared the package with PROFINET support on ALX package over email. Kindly confirm whether you have received the package

    Regards,

    Laxman  

  • Hi Laxman,

    The patch file was received. Thank you for sharing.

    Regards,
    Chockalingam 

  • Hi Chockalingam,

    Thank you for the confirmation. We will be closing this thread now. Kindly let us know if you face any other issues.

    Regards,

    Laxman