Other Parts Discussed in Thread: SYSBIOS, TLK110,
Hello,
I have a problem with sdk update.
I have updated my sdk version:
- the previous one was sysbios_ind_sdk_2.1.1.2
- the new one is sysbios_ind_sdk_02.01.03.02 (dec 2016)
My application is running on a board with 8 cards.
Each card is equiped with an ARM3359.
All these cards are part of an Ethercat Network which is driven by a master Ethercat.
On each processor a same software is running. This software was built on the "ethercat slave "project model.
In this project, the EcatStack code use 2 tables to initialize the PRU: HostProc[] and FrameProc[]
These tables are given in the install directory: C:\ti\sysbios_ind_sdk_2.1.1.2\sdk\protocols\ethercat_slave\firmware\v1.0 for the previous sdk and C:\ti\sysbios_ind_sdk_02.01.03.02\sdk\protocols\ethercat_slave\firmware\v1.0 in the new sdk. These tables are differents fro one version to the other.
Everything is all right with previous sdk: when I start my Ethercat network I can see and reach all the ARM3359 slaves.
With the new sdk, when I start my Ethercat network, no slave are seen !!!!
So I try to debug this issue and I realise that if I keep the new sdk version and only replace the 2 tables, my Ethercat network is ok !
So my problem seems to come from PRU initialization....
Do you already notice this issue ?
Is there any newer sdk to update ?
I have a look on internet to getinformation on PRU and I saw that there was a recent version of PRU ICSS EtherCAT package which was provided in June. Do you know if this package could solve my problem ?
I had never use these manner to have a new version of Ethercat Protocol. Can you tell me if it is possible to integrate this patch on my sdk version ?
Thanks a lot for your help
Laurence