Hi,
I'm trying to use the gPTP stack for SJ1110 and S32G-VNP-RDB2, however, when I upload a configuration that includes the gPTP stack I get the following issue:
[ 4.342187] pfeng 46000000.pfe pfe2: Registered PTP HW clock successfully on EMAC2
[ 4.449138] sja1110 spi5.0: probing uc
[ 4.449321] sja1110 spi5.1: probing switch
[ 4.449662] sja1110 spi5.1: Could not get GPIO from device tree
[ 4.449681] sja1110 spi5.1: [sja1110_post_probe_upload_worker] Trying to initialize switch
[ 4.450669] sja1110 spi5.1: [sja1110_init_hw] loaded fw 'sja1110_switch.bin'
[ 4.450776] sja1110 spi5.1: [sja1110_pre_switch_upload] Found switch config of size 2276
[ 4.451122] sja1110 spi5.1: Uploading config...
[ 4.476515] sja1110 spi5.1: Successfully configured!
[ 4.476568] sja1110 spi5.0: [sja1110_post_probe_upload_worker] Trying to initialize uC
[ 4.482173] sja1110 spi5.0: [sja1110_init_hw] loaded fw 'sja1110_uc.bin'
[ 4.482191] sja1110 spi5.0: [sja1110_pre_uc_upload] Found firmware of size 98336
[ 4.482278] sja1110 spi5.0: [sja1110_pre_uc_upload] firmware appears to be valid
[ 4.482324] sja1110 spi5.0: [sja1110_pre_uc_upload] µC not ready for download (Status=0x31)
[ 4.482444] sja1110 spi5.0: Uploading firmware...
[ 4.485680] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 4.713699] random: crng init done
[ 4.713716] random: 4 urandom warning(s) missed due to ratelimiting
[ 4.722419] sja1110 spi5.0: [sja1110_uc_parse_status_many] Upload error detected in status message 23312 (status=0x36,err=0x5b)
[ 4.722448] sja1110 spi5.0: Upload error detected!
[ 4.722454] sja1110 spi5.0: uploading firmware failed with 91
[ 5.193647] s32cc-dwmac 4033c000.ethernet eth0: PHY [stmmac-0:01] driver [Micrel KSZ9031 Gigabit PHY] (irq=POLL)
[ 5.202961] s32cc-dwmac 4033c000.ethernet eth0: Enabling Safety Features
[ 5.203066] s32cc-dwmac 4033c000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported
[ 5.203351] s32cc-dwmac 4033c000.ethernet eth0: registered PTP clock
[ 5.204900] s32cc-dwmac 4033c000.ethernet eth0: configuring for phy/rgmii-id link mode
[ 5.207692] 8021q: adding VLAN 0 to HW filter on device eth0
Auto Linux BSP 33.0 s32g274ardb2 ttyLF0
I used "switch_config_s32g_vnp_rdb" as base project, then I updated the configuration to add the gPTP stack following the instructions in "SJA1110 GPTP CONFIGURATION" presentation, then I compiled the updated code and sent the configuration to the switch. could you help me to understand why I'm getting the error message?
Note: If I only include the gPTP stack as part of the configuration and I compile it (the gptp stack is not used in the user application) the issue also happens
My board is: S32G-VNP-RDB2
PFE FW: 1.3
PFE Driver: 1.0
Linux BSP 33.0
Best regards
解決済! 解決策の投稿を見る。
Hi @Ethan_L
I apologize about the delay on my answer, if you are still facing this problem this is what I have.
i was told that whenever you integrate the gPTP stack to de configuration file, the file is padded with 0x00, this padding is not included as part of the file size in the file headers. This provokes that the driver thinks that the file has already been transferred even when the padded data is still being transferred(the driver uses the length defined in the header, while Linux transfers the whole file), as the transference has not actually end, it causes a data corruption and for this reason we see this error message.
to solve this, a work around was provided.you need to manually remove the padded data at the end of the file (scroll to the end of the file, and remove the Last part where there are only 0x00) after doing this the file is successfully transferred and verified!
best regards
nico
Hi @nicolasespla93 ,
I had the same problem when I added gPTP to my project.
How did you solve this problem?
Thanks,
Ethan.
Hi @Ethan_L
I apologize about the delay on my answer, if you are still facing this problem this is what I have.
i was told that whenever you integrate the gPTP stack to de configuration file, the file is padded with 0x00, this padding is not included as part of the file size in the file headers. This provokes that the driver thinks that the file has already been transferred even when the padded data is still being transferred(the driver uses the length defined in the header, while Linux transfers the whole file), as the transference has not actually end, it causes a data corruption and for this reason we see this error message.
to solve this, a work around was provided.you need to manually remove the padded data at the end of the file (scroll to the end of the file, and remove the Last part where there are only 0x00) after doing this the file is successfully transferred and verified!
best regards
nico
Hi,
We have seen that we have a similar ticket that is being taken care of.
We will continue to support this inquiry through our ticket system, let us know if you find any problem with this.
Please, let us know.
Hi @Daniel-Aguirre ,
I also want to know if there is a way to solve this issue other than by manually deleting.
Thanks.
Hi Daniel,
It seems a known issue in NXP, will you fix this issue in the future?
Thanks.