• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 465 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

pru support on am335x

noirtme
Prodigy 20 points

Other Parts Discussed in Thread: SYSBIOS

Hello,

as an embedded system developer and integrator, together with our customers we are interested in the industrial communication ability of the am335x. Just I see your am335x_sysbios_ind_sdk_1.0.0.4 supports the industrial protocols profibus-slave, powerlink-slave and ethercat-slave. But we also interested in the protocols for ProfiNET, EtherNet/IP and SerCOS III. Are there any of these protocols in progress or planed? Is it possible to give a timetable?

Reinhold

  • 0
    Intellectual 810 points

    As for PROFINET, I recently heard from TI that projected public release is Jan. 2013.  I don't know about SERCOS III.  As for EtherNet/IP, which "flavor" were you interested in?  Standard EIP doesn't require the PRU's, as it uses just regular TCP and UDP, so even the beaglebone would be a more than adequate EIP client or server (with the appropriate protocol stack, of course.)

    Darrin

  • 0 in reply to Darrin Hansen
    Prodigy 20 points

    Many thanks Darrin.

    I have some additional issues arround PRU on the am335x and hope you or any other member can give some information.

    The ind_sdk_1.0.04 DevKit is based on the OS SYSBIOS.

    What handles have to be done on the PRU-Firmware unsing other OS like QNX, Linux or WINCE?

    Are any changes on the interface of the PRU-Firmware necessary?

    Are any of the protocol stacks has been ported to the mentioned OS in the meantime?

    Are any documentation of the firmware interface for the various protocol stacks available and if so where can I get them?

    Reinhold

  • 0 in reply to noirtme
    Intellectual 810 points

    Reinhold -

    While all the example TI apps in the industrial SDK uses Sys/Bios for obvious reasons, I don't believe it would be an issue at all to port it to other RTOS's (you'd probably spend more time on the RTOS porting effort than the PRU integration as that is OS-agnostic).  I could be wrong, but I don't think any changes to the interface (API) would be required for such a scenario.

    As for Linux+PRU, etc., there have been some other posts to this newsgroup that have approached the topic, such as:

    http://e2e.ti.com/support/dsp/sitara_arm174_microprocessors/f/791/t/169164.aspx

    http://e2e.ti.com/support/dsp/sitara_arm174_microprocessors/f/791/p/183087/661367.aspx#661367

    The protocol stacks themselves would depend on the specific stack vendor you are interested in and the OS's they support (or, if they just provide source code then you would need to integrate the stack with your chosen OS).

    I'm not sure if there's any formal API documentation of the firmware interface: you might just need to look at the BSP code in a sample project (e.g. TIESCBSP.C) to figure it out.  At least I haven't seen anything better.

    Darrin