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.

AM6548: How to use PRU_ICSSG Ethernet in U-Boot

Part Number: AM6548

Our customer wants to use the PRU_ICSSG Ethernet in U-Boot.

They are using the Processor SDK Linux 08.00.00.04 and have loaded the firmware using RemoteProc with the following documents, the PRU_ICSSG Ethernet in U-Boot works via port 0 of ICSSG2 on EVM with SR1.0, but not on EVM with SR2.0.

software-dl.ti.com/.../UG-Network.html
software-dl.ti.com/.../UG-RemoteProc.html

=> rproc init
=> rproc list
0 - Name:'r5f@41000000' type:'internal memory mapped' supports: load start stop reset
1 - Name:'r5f@41400000' type:'internal memory mapped' supports: load start stop reset
2 - Name:'pru0_0' type:'internal memory mapped' supports: load start stop
3 - Name:'rtu0_0' type:'internal memory mapped' supports: load start stop
4 - Name:'tx_pru0_0' type:'internal memory mapped' supports: load start stop
5 - Name:'pru0_1' type:'internal memory mapped' supports: load start stop
6 - Name:'rtu0_1' type:'internal memory mapped' supports: load start stop
7 - Name:'tx_pru0_1' type:'internal memory mapped' supports: load start stop
8 - Name:'pru1_0' type:'internal memory mapped' supports: load start stop
9 - Name:'rtu1_0' type:'internal memory mapped' supports: load start stop
10 - Name:'tx_pru1_0' type:'internal memory mapped' supports: load start stop
11 - Name:'pru1_1' type:'internal memory mapped' supports: load start stop
12 - Name:'rtu1_1' type:'internal memory mapped' supports: load start stop
13 - Name:'tx_pru1_1' type:'internal memory mapped' supports: load start stop
14 - Name:'pru2_0' type:'internal memory mapped' supports: load start stop
15 - Name:'rtu2_0' type:'internal memory mapped' supports: load start stop
16 - Name:'tx_pru2_0' type:'internal memory mapped' supports: load start stop
17 - Name:'pru2_1' type:'internal memory mapped' supports: load start stop
18 - Name:'rtu2_1' type:'internal memory mapped' supports: load start stop
19 - Name:'tx_pru2_1' type:'internal memory mapped' supports: load start stop
=>

=> fatload mmc 1:1 0x80000000 ti-pruss/am65x-sr2-pru0-prueth-fw.elf
36316 bytes read in 3 ms (11.5 MiB/s)
=> rproc load 14 0x80000000 8ddc
Load Remote Processor 14 with data@addr=0x80000000 36316 bytes: Success!
=> fatload mmc 1:1 0x80000000 ti-pruss/am65x-sr2-rtu0-prueth-fw.elf
29944 bytes read in 4 ms (7.1 MiB/s)
=> rproc load 15 0x80000000 74f8
Load Remote Processor 15 with data@addr=0x80000000 29944 bytes: Success!
=> fatload mmc 1:1 0x80000000 ti-pruss/am65x-sr2-txpru0-prueth-fw.elf
35916 bytes read in 4 ms (8.6 MiB/s)
=> rproc load 16 0x80000000 8c4c
Load Remote Processor 16 with data@addr=0x80000000 35916 bytes: Success!
=> rproc start 14
=> rproc start 15
=> rproc start 16
=> env set ethact icssg2-eth
=> ping 192.168.10.50
prueth icssg2-eth: RX dma flow id bad, expected 0, actual 2
link up on port 0, speed 1000, full duplex
Using icssg2-eth device

ARP Retry count exceeded; starting again
ping failed; host 192.168.10.50 is not alive
=>

The documentation for network boot seems to support only SR1.0.

As enumerated by the "rproc list" the remotecore for port 0 of ICSSG2 should be 14, 15, 16.

For SR2.0 the firmware should use the following.

For Port 0:
"ti-pruss/am65x-sr2-pru0-prueth-fw.elf",
"ti-pruss/am65x-sr2-rtu0-prueth-fw.elf",
"ti-pruss/am65x-sr2-txpru0-prueth-fw.elf",

For Port 1:
"ti-pruss/am65x-sr2-pru1-prueth-fw.elf",
"ti-pruss/am65x-sr2-rtu1-prueth-fw.elf",
"ti-pruss/am65x-sr2-txpru1-prueth-fw.elf";

What is the address to which each firmware is loaded?

What are the other differences between SR2.0 and SR1.0 for PRU_ICSSG Ethernet in U-Boot?

In other thread, the PRU_ICSSG Ethernet in U-Boot has been reported to fail, but has not been resolved.

e2e.ti.com/.../am6548-am6548-sr-2-x-pru-ethernet-in-u-boot-with-ti-sdk-8-0

Best regards,

Daisuke

  • Dear TI support team,

    Does the Processor SDK Linux 08.00.00.04 or latest SDK support the PRU_ICSSG Ethernet in U-Boot on EVM with SR2.0?

    If SR2.0 is supported, please answer the questions in my first post.

    Please give me an answer as soon as possible. Your prompt reply would be appreciated.

    Best regards,

    Daisuke

  • Dear TI support team,

    Has TI tested the PRU_ICSSG Ethernet in U-Boot on EVM with SR2.0?

    If it has been tested, please answer the questions in my first post.

    Please give me an answer as soon as possible. Your prompt reply would be appreciated.

    Best regards,

    Daisuke

  • Hello Daisuke,

    Apologies for the delayed response, and thank you for the pings. Let me check with the development team on whether these steps have been validated with AM65x SR2.0, and if so which releases have been validated. If I do not reply by the end of the week, please ping the thread again to make sure this request does not get lost.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your support. Our customer is waiting for your update.

    Please give me an answer as soon as possible. Your prompt reply would be appreciated.

    Best regards,

    Daisuke

  • Hello Daisuke,

    Thank you for the ping. I have not heard back yet. I reached out to the developers again, please ping the thread again if I have not replied within a couple of days.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your support. Our customer is waiting for your update.

    Please give me an answer as soon as possible. Your prompt reply would be appreciated.

    Best regards,

    Daisuke

  • Hello Daisuke,

    Ok, I heard back from the developers.

    The current SDK documentation is only applicable for SR1.0, and will not work for SR2.0. They are still working on putting together updated steps and validating whether the driver and firmware work as is, or if the driver and firmware need any updates.

    I am following up to get an idea of when we can expect another update from them. Is there a timeframe of need from the customer's side?

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your reply.

    Our customer needs to be supported for SR2.0 as soon as possible.

    Is there the plan to be supported for SR2.0 in the next release of the Processor SDK?

    If so, when is the next release scheduled for release?

    Best regards,

    Daisuke

  • Hello Daisuke,

    Understood. Please ping the thread if I do not have another response for you within the next couple of days.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your support. Our customer is waiting for your update.

    Please give me an answer as soon as possible. Your prompt reply would be appreciated.

    Best regards,

    Daisuke

  • Hello Daisuke-san,

    The developers said they would have another update for us next week.

    At this point in time, I am unclear on whether PRU Ethernet in Uboot is supported for AM65x SR2.0, and we just need different steps to enable it, or whether PRU Ethernet in Uboot is not actually supported for AM65x SR2.0 on the latest release.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your support.

    We will wait for another update which may be provided next week.

    Please give me an answer as soon as possible. Your prompt reply would be appreciated.

    Best regards,

    Daisuke

  • Hi Nick-san,

    Thank you for your support. Our customer is waiting for your update.

    Please give me an answer as soon as possible. Your prompt reply would be appreciated.

    Best regards,

    Daisuke

  • Hello Daisuke-san,

    Apologies for the delayed response, thank you for continuing to ping the thread. Uboot PRU Networking does seem to be broken for AM65x SR2.0 on Linux SDK 8.2. From my checkin with the developers last week:

    1) The documentation about loading the PRU firmware does not apply to AM65x SR2.0, since the TX_PRUs were not included. They have rewritten the documentation for the next SDK release.

    2) Something seems to be broken in the driver/firmware, even with updated documentation steps. The developers are still debugging and looking for a fix.

    I will ask for another update later this week. Please ping me if I do not have another response by the end of the week.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your support. Our customer is waiting for your update.

    Please give me an answer as soon as possible. Your prompt reply would be appreciated.

    Best regards,

    Daisuke

  • Hello Daisuke-san,

    Apologies for the delayed response. The engineer who was debugging this is no longer with TI. I am trying to get a status update from the manager.

    I think this is a safe message for the customer: "It does not look like PRU Ethernet in Uboot is supported for AM65x SR2.0 in SDK 8.2. We are still debugging to understand the behavior and how to fix it in a future release".

    Thank you for your patience on pinging the thread consistently to make sure this doesn't slip through the cracks. Please ping the thread again if I don't have another update for you by next week.

    Regards,

    Nick

  • Hello Daisuke-san,

    The debugging effort for AM65x PRU Ethernet in Uboot will be picked up by one of our engineers who is returning to work sometime in August. The effort is being prioritized, but it will require dedicated debug. At this point in time, I cannot promise a specific fix date. I have filed a ticket LCPD-28436 to track the issue.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your support.

    Could you let me know when the debugging effort have been started and a fix date has been scheduled?

    Our customer is concerned that the issue affects not only U-Boot but also Linux. The issue will also affect Linux if it needs a firmware update to be fixed.

    Best regards,

    Daisuke

  • Hello Daisuke-san,

    I am asking whether the team anticipates that this would also affect Linux functionality, but as far as I am aware PRU Ethernet was tested and validated during Linux runtime on AM65x SR2.0. Is the customer seeing any Linux runtime behavior that seems concerning?

    To set expectations: I will be on vacation for the last 3 weeks of August. Depending on when the developer returns from their vacation, we may not be able to comment on fix date until early September.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your reply.

    Is the customer seeing any Linux runtime behavior that seems concerning?

    No, because you mentioned that something in the firmware may possibly be broken, our customer is concerned that the issue also affects Linux.

    Our customer will wait for your update.
    Please give me an answer as soon as possible. Your prompt reply would be appreciated.

    Best regards,

    Daisuke

  • Hello Daisuke-san,

    I am checking to see if there is any additional information the manager can give us before the developer returns in August. Feel free to ping the thread if I have not provided an update by the middle of next week.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your support. Our customer is waiting for your update.

    Please give me an answer as soon as possible. Your prompt reply would be appreciated.

    Best regards,

    Daisuke

  • Hello Daisuke-san,

    No updates yet. I pinged the manager again.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your support. Our customer is waiting for your update.

    Please give me an answer as soon as possible. Your prompt reply would be appreciated.

    Best regards,

    Daisuke

  • Hello Daisuke-san,

    PRU Ethernet was validated on AM65x SR2.0 during Linux runtime. Further updates will have to wait until the developer returns from vacation and is able to start looking at the issue.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your reply.

    I would appreciate it if you could let me know as soon as looking at the issue is started.

    Best regards,

    Daisuke

  • Hello Daisuke-san,

    I am leaving for vacation, and will return at the end of August. There are no updates at this point, the developer has not had time to make much progress on this issue. We will look at it, and I will provide another update for you in September once I have returned.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for letting me know the current status.

    I would appreciate it if you could let me know as soon as looking at the issue is started.

    Have a good vacation!

    Best regards,

    Daisuke

  • Hello Daisuke-san,

    The development team has accepted the issue, but as far as I am aware they have not started testing. I am double checking on the expected timeframe for when they provide a fix.

    Regards,

    Nick

  • Hello Daisuke-san,

    Ok, the developers have replicated your observations. They are still working on finding a fix. The plan is to have PRU Ethernet working in uboot on AM65x for the next AM65x Linux SDK release, which is scheduled for sometime February / March 2023.

    Regards,

    Nick

  • Hi Nick-san,

    Thank you for your support.

    I would appreciate it if you could let me know as soon as there is an update.

    Best regards,

    Daisuke

  • Hello Daisuke-san,

    I have added a note to the bug report asking the developer to let me know when they start working on this issue. When they ping me, I will unlock this thread (if it has been longer than a month) and provide you with an update.

    Regards,

    Nick