îmx8 container encryption so i read the docs guide to encrypt the container  https://github.com/nxp-imx/uboot-imx/blob/lf_v2025.04/doc/imx/ahab/guides/mx8_mx8x_encrypted_boot.txt but the problem is with enabling encrypted boot support,the cst tool 4.0.1 provided by nxp dosent have a code folder that contains backend ... so do i need the cst source code to compile the tool and enable encryption support?and if so from where i download the source code since i have only the cst 4.0.1 and it dosent contain container encryption support Re: îmx8 container encryption Hello, Seems that the documentation is a bit old, please note that this step is no longer needed in CST after version 3.0.0 Also, this App note is more up to date for encrypt boot: https://www.nxp.com/webapp/Download?colCode=AN13994 And there is the SPSDK as well: https://www.nxp.com/design/design-center/software/development-software/secure-provisioning-sdk-spsdk:SPSDK Best regards/Saludos, Aldo.

FS32K146UAT0VLQT 烧录错误 嗨，团队、 在对 FS32K146UAT0VLQT 型号进行手动编程时，我们遇到了几种不同的情况：1.完全无法编程；2.编程并升级软件后，无法使用，手动编程再次失败。造成这些问题的原因是什么，您能提供有效的解决方案吗？谢谢。

PN7642 CTAUX pins as GPIO Hi! I am testing the use of CTAUX INT, IO and CLK pins as GPIO on PN7642 , as they are listed inside the gpio_pin_t enum (kGPIO_CTAUX_IO, kGPIO_CTAUX_CLK, kGPIO_CTAUX_INT). There is also a bitfield in the PCRM register: /**< 16-If set the CT_AUX IP is driving this pad, otherwise GPIO mode is active.*/  However it seems that the default init with GPIO_PinInit and GPIO_PinRead/Writed do not work. I also could not get it to work with some other configs in the register. I also noticed the pinot of the PN7642 datasheet they are not marked as GPIO Furthermore the datasheet says there are "Up to 21 GPIOs (6 dedicated GPIOs)". If the CTAUX pins could be used there would be 24 of them. Could you clarify if I can use these pins as GPIO or not. Thanks in advance! Re: PN7642 CTAUX pins as GPIO Hello @nekprimc  E4 can be used GPIO,but it's limited input.

使用 DP8384 代替 LAN8741 的 LWIP PING 项目示例 你好、 我版本并使用这个示例项目： \mcuxsdk\examples\lwip_examples\lwip_ping_enet_qos 与此开发。板: \ mcuxsdk\ 示例\ _boards\ frdmcxe31b 而且效果很好，我可以将开发板连接到 Raspberry Pi 4 然后 ping 开发板。 我有一块装有相同的 MCX 微控制器的定制板，但使用的是 DP8384 PHY 控制器，而不是 frdmcxe31b 板上使用的 LAN8741。我已经将示例项目移植到这个板上，板向 Raspberry 发送 ping，但它没有回复从树莓派发送的 ARP 请求。我进行了调试，可以看到微控制器接收到 ARP 请求，并尝试用该功能发送回复： status_t ENET_QOS_SendFrame   在该文件中： \mcuxsdk\drivers\enet_qos\fsl_enet_qos.c   您可以在 call_stack.png 中查看调用堆栈。   但是没有发送包裹，我也没有收到任何错误。我在 Raspberry 上运行了 tcpdump。 下面是 .pcap锉刀 disco__test14.zip ，可以看到数据包 18 是来自 Raspberry 的 ARP 请求。 我比较了 .config来自开发项目和自定义板项目的文件，除了 CONFIG_MCUX_COMPONENT_component.phydp8384x=y 以及 CONFIG_MCUX_COMPONENT_component.phylan8741=y 在 config.zip 中可以找到 .config 和 .config文件 我的问题是，是否还需要进行其他调整？是 DP8384 阻止了 ARP 回复吗？ 此致敬礼， 乔纳斯 MCXC Re: Example LWIP PING project using DP8384 instead of LAN8741 抱歉忘了其他文件，我已将它们附在本邮件中。 Re: Example LWIP PING project using DP8384 instead of LAN8741   你好、 我附上了原理图截图。 板可以发送其他以太网帧，例如回声请求，如所附的 .zip 所示锉刀 板的 IP 地址为 192.168.0.102，树莓的 IP 地址为 192.168.0.100。 Re: Example LWIP PING project using DP8384 instead of LAN8741 你好@JONASA "在 config.zip 中可以找到两个 .config 文件"。 能否共享您的 config.zip 文件？ 如果 MCU 接收到 ARP 请求，并由 lwIP 进行解析，调用 ENET_QOS_SendFrame()，但线路上始终没有出现帧，则表示 MAC 已准备就绪，但 PHY 没有进行传输。 这强烈表明是 PHY 配置问题，而不是 lwIP 或 ENET_QOS 驱动程序逻辑问题。 能否提供 DP83848 的原理图截图？ BR 哈利 Re: Example LWIP PING project using DP8384 instead of LAN8741 还有一件事： 在开发板上我们有一台 MCXE31BMPB 在自定义板上我们有一个 S32K324EHT。 这两个微控制器是一样的吧？ Re: Example LWIP PING project using DP8384 instead of LAN8741 你好@JONASA,@Harry_Zhang、 我检查了你的电路图，似乎是正确的。 根据 AN14792 - S32K31x 到 MCX E31x 移植指南，MCXE31BMPB 就是 S32K314EHT1。 首先，让我讨论一下共享的 pcap 文件。 IP为192.168.0.102的设备（您的恩智浦主板）首先发送流量：它传输无偿ARP（“192.168.0.102的ARP公告”），然后向树莓派（192.168.0.100）发送ICMP Echo请求。Raspberry Pi 用 ICMP Echo 回复了几秒钟，因此 TX 和 RX 最初都能工作（至少对于 IP/ICMP 而言）。 大约 10—12 秒后，树莓派开始重复发出 ARP “谁有 192.168.0.102？”请求，但未收到来自恩智浦设备的任何 ARP 回复。在 Linux 上，一旦对邻居的可达性产生怀疑，它会首先尝试单播 ARP 探测（发送到最后已知的 MAC），如果失败，就会退回到广播 ARP 请求。此时，Pi 无法再可靠地向 192.168.0.102 发送帧，因此也不再返回 ICMP 回复。 因此，核心问题不是 “硬件无法传输”（我们清楚地看到恩智浦主板在传输ICMP请求），而是在一段时间后恩智浦主板停止回复要求其自己的IP地址的ARP请求。 如果 ARP 请求运行一段时间后才停止应答，常见原因是 RX 路径不再处于服务状态（中断未触发、轮询未运行、RX 任务已耗尽）， RX 描述符/缓冲区耗尽（DMA 收到帧，但缓冲区未循环使用）、 一个时间/优先级问题，应用程序负载最终会阻止 lwIP 输入处理。 建议的快速实验 请尝试禁用恩智浦主板生成的定期 ping（或大幅降低其速率）。如果设备未持续生成 ICMP 时ARP 故障消失，则强烈表明存在调度/优先级/接收服务/缓冲区回收问题，而不是 PHY 限制。 作为快速诊断，请确认 D-Cache 是否已启用，并尝试禁用 D-Cache 运行 顺祝商祺！ 帕维尔 Re: Example LWIP PING project using DP8384 instead of LAN8741 我在 .cmake 中添加了这几行，现在就能正常工作了我的项目中的文件： mcux_add_macro ( CC "-DFSL_ETH_ENABLE_CACHE_CONTROL " ) 在示例项目中，这些行 位于这个文件中： C:\work\mcx\mcuxpresso-sdk\ mcuxsdk\ 示例\ _boards\ frdmcxe31b\ lwip_examples\ lwip_ping_enet_qos\ bm\ reconfig.cmake 您知道为什么需要启用以太网缓存控制吗？ Re: Example LWIP PING project using DP8384 instead of LAN8741 你好、 好的，同样的软件也可以在开发板 MCXE31BMPB 上运行。 这两种微控制器有什么区别吗？ 正如您所说，根本原因可能是未触发 EMAC DMS 中断。我是否需要修改 EMAC 的驱动程序代码，或者这两个微控制器是否完全相同？是否具有相同的 EMAC 控制寄存器等？ 这是一个裸机。 这是主循环： 虽然(1)     { /* 轮询驱动程序，获取任何未完成的帧 */ 以太网输入(&netif）； sys_check_timeouts();/* 处理所有核心协议的所有系统超时 */    }   Re: Example LWIP PING project using DP8384 instead of LAN8741 你好@jonasa、 MCXE31BMPB 是 S32K314EHT1。S32K14 和 S32K324 的区别仅在于内核数量不同，请参阅 S32K3 数据表，表 1。我认为您不需要修改代码。 顺祝商祺！ 帕维尔 Re: Example LWIP PING project using DP8384 instead of LAN8741 你好@jonasa、 接得好 以太网驱动程序通常使用 DMA 来读取 TX 描述符/缓冲区和写入 RX 描述符/缓冲区，因此这并不奇怪。很抱歉，我不知道与该 SDK 相关的详细信息。 顺祝商祺！ 帕维尔

Variscite IMX8M Mini セキュアブート || ロックおよびクローズコマンド こんにちは、 現在、Variscite DART-MX8M-MINIプラットフォームに取り組んでおり、HAB関連のコマンドの生成と必要なeFuseのプログラミングを正常に完了しました。 しかしながら、セキュリティ強化のためにU-Boot経由で実行できる、デバイスのシャットダウン、ロック、および追加のセキュリティ設定（JTAGの無効化など）に関する適切なコマンドと手順をまだ探しています。 入手可能なドキュメントをすべて確認しましたが、見つけた資料のほとんどはi.MX5、i.MX6、i.MX7シリーズのデバイスに関するものでした。i.MX8M Miniプラットフォーム専用の、明確で最新の公式ドキュメントを見つけることができませんでした。 AN4581 ドキュメント 以前のi.MXシリーズに関する既存のドキュメントがi.MX8M Miniにも適用されるかどうか、あるいはこのプラットフォーム向けにこれらのセキュリティ関連コマンドを具体的に解説した更新版/公式ドキュメントが存在するかどうか、ご確認いただけますでしょうか？ i.MX 8ファミリ | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: Variscite IMX8M Mini Secure Boot || lock and close commands こんにちは、 @Sudharsun さん。 参考資料としてはAN4581が挙げられます。また、私の方ではi.MX8M専用のセキュアブートガイドも参考になると思います。 uboot-imx/doc/imx/habv4/guides/mx8m_secure_boot.txt (maaxboard_v2020.04_5.4.24_2.1.0)· Avnet/uboot-imx · GitHub mx8m_spl_secure_boot.txt - doc/imx/habv4/guides/mx8m_spl_secure_boot.txt - U-boot ソースコード v2026.01 - Bootlin Elixir クロスリファレンス doc/imx/habv4/guides/mx8m_mx8mm_secure_boot.txt - uboot-imx - Google の Git i.MX8M Miniのリファレンスマニュアルには、JTAGに関するセクションがあります。 JTAG無効化およびヒューズ定義について。 これがあなたのお役に立てば幸いです。 素敵な一日をお過ごしください よろしくお願いいたします。 リタ

FS23は常にMCUをリセットします こんにちは、 問題が ボードの電源を入れてFS23をデバッグモードから外すと、必ずリセットされます。 そしてこのようにリセットライン     デバッグモードを有効にすると、リセットは行われません。 どのような問題がこの現象を引き起こす可能性がありますか？ また、私のプロジェクトにはブートプロジェクトとアプリケーションプロジェクトが含まれていますが、ブートプロジェクトとアプリケーションプロジェクトの両方を扱う際に注意すべき点は何ですか？ Re: FS23 always reset MCU こんにちは、ビンさん。 FS23は、256msのINITウィンドウ内で厳密な初期化シーケンスを完了する必要があります。このシーケンスが正しく完了しない場合、またはウォッチドッグが適切に処理されない場合、デバイスは次のようになります。 - フェイルセーフモードに入る - RSTB を低く主張する - 自動的に再起動する（設定されている場合）、その結果、リセットループが発生する。 デバッグモードが有効になっている場合、ウォッチドッグ監視とフェイルセーフエントリーが無効になるため、リセット動作がなくなります。 推奨される起動手順の概要については、弊社のAN14041に掲載されている図1「FS23初期化フローチャート例」を特にご参照ください。 AN14129では、基本的な動作と起動/アプリケーションに関する考慮事項について説明しています。 BRs、トーマス Re: FS23 always reset MCU ありがとう、トーマス

EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 Dear NXP Support, I would like to report an issue with EfficientDet-Lite0 on i.MX95 using the Neutron conversion flow. My setup is: Board: i.MX95 EVK BSP: Linux imx95evk 6.12.34-lts Original model: efficientdet_lite0_int8.tflite Application: NNStreamer pipeline with TensorFlow Lite and external Neutron delegate Input: live camera stream from /dev/video13 I compared the original model and the Neutron-converted model using the same application and added debug prints for both the model input tensor and output tensors. Findings: The original model efficientdet_lite0_int8.tflite runs correctly on CPU. For the original model, the input tensor changes frame by frame, and the output tensor statistics also change frame by frame. For the Neutron-converted model, the input tensor still changes frame by frame, but the output tensors remain almost constant across frames. As a result, detections are static or empty even though the live camera image is changing. I tested two Neutron paths: A) Standalone Neutron SDK 3.0.1 Converted with eiq-neutron-sdk-windows-3.0.1\bin\neutron-converter.exe Runtime on target updated to 3.0.1 Result: converted model loads, but outputs remain nearly constant and produce static boxes B) Rolled back to the 6.12.34-era toolchain Converted with: C:\nxp\eIQ_Toolkit_v1.17.0\bin\neutron-converter\MCU_SDK_25.09.00+Linux_6.12.34_2.1.0\neutron-converter.exe Runtime rolled back accordingly Result: converted model loads, input changes, but outputs are still nearly constant and detections remain empty Example behavior with the rolled-back conversion/runtime: Input changes: INPUT range: min=0 max=255 mean=141.903 sum=43592724 INPUT range: min=0 max=255 mean=137.091 sum=42114370 INPUT range: min=1 max=255 mean=105.373 sum=32370478 Output remains nearly constant: classes_raw range: min=0.000000 max=0.019531 mean=0.000009 boxes_raw range: min=-2.926135 max=0.535502 mean=-0.30798 The conversion statistics for the rolled-back path show: operators after extract: 33 Neutron graphs: 4 operators total: 371 operators converted: 342 operators NOT converted: 29 This suggests that the live input reaches the model correctly, but the converted Neutron model path is not producing frame-dependent outputs for EfficientDet-Lite0. Could you please advise: Whether EfficientDet-Lite0 is expected to be supported correctly on i.MX95 with BSP LF_6.12.34_2.1.0. Whether this model is known to have issues with Neutron conversion on i.MX95. Whether there is a recommended reference object detection model for Neutron on this BSP that is known to behave correctly with live video. Whether this behavior indicates a converter issue, a delegate/runtime issue, or an unsupported operator pattern for EfficientDet-Lite0. Thank you in advance! Best regards, EOF Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 Hi @Rita_Wang, Thank you, I look forward for your reply. Have a nice day you too! Best regards, EOF Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 Hi @EOF ， We will check in our side and then give you reply, please wait. Wish you have a nice day Best Regards Rita Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 Hi @Rita_Wang, I am using the i.MX 95 19mm x 19mm evaluation kit (EVK) (i.MX 95 19mm x 19mm Evaluation Kit | NXP Semiconductors) With  BSP: Linux imx95evk 6.12.34-lts I've attached the converted model (trained in COCO dataset) in this message.  This model was converted using (no additional flag only --input,--ouput,--target): C:\nxp\eIQ_Toolkit_v1.17.0\bin\neutron-converter\MCU_SDK_25.09.00+Linux_6.12.34_2.1.0\neutron-converter.exe Best regards,  EOF Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 Hi @EOF ， Here we need more information, Could you please provide the customer's model for further analysis? Wish you have a nice day Best Regards Rita Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 Hi @Rita_Wang , Thank you for your reply. Yes, the non-coverted file is attached to this message. Thank you again, I look forward for your reply.  Have a nice day! Best regards, EOF Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 Hi @EOF , Could you provide us the source model ,not the neutron converted model to us ?  We can  try to convert the model on our side and validate if there are any accuracy issues. Thanks. Wish you have a nice day Best Regards Rita

[ABUSE] Post By: @RishavKaaraTech / Board: TapLinx-SDK / Reported by: rgjvhfiy rgjvhfiy has reported the post RFIDDiscover tool acquired but how to use it posted by @RishavKaaraTech for the following reasons: Reason: Plagiarism Details: http://polden.info/story/nuvigil-can-i-buy">nuvigil fedex cod https://www.internationalhumanistparty.org/es/content/nuvigil-buy-online-30-mg">buy no perscription nuvigil https://www.thebiketube.com/velo-lora">buy nuvigil in nebraska https://www.rom.by/tema-na-forume/nuvigil-buy-canada">cod nuvigil overnight delivery http://ru.ph-ed-plus.nspu.ru/article/18517">buy nuvigil canada no prescription http://santorini.cz/node/6482">saturday delivery on nuvigil http://www.le-cercle-des-sourires.fr/evnementmultisessions/nuvigil-can-i-purchase">nuvigil fedex cod https://ufa-help.ru/content/nuvigil-free-prescription-free-shipping">buy codest online nuvigil http://www.familygalactictravel.com/node/3443">purchase nuvigil mail order https://www.internationalhumanistparty.org/es/content/nuvigil-buy-online-30-mg">purchase nuvigil mail order https://mnbride.com/your-couple-name-3213">where to buy next nuvigil http://gamblingobzor.net/forum/nuvigil-cod-overnight-delivery">nuvigil cash delivery cod https://jeunescathos-bxl.org/fr/content/nuvigil-buy-montgomery">buy nuvigil canada no prescription https://www.flohmy.ch/en/node/4737">free prescription nuvigil free shipping https://www.geofak85.ru/nuvigil-canada-online-pharmacy-yoamoabarranquilla">nuvigil non prescription fedex overnight https://arendville.ru/nuvigil-how-buy">buy nuvigil from canada https://reflexologie-cerilly.fr/en/node/4592">can i order nuvigil https://www.worldcolleges.info/node/29844">where to order next nuvigil https://hr-life.ru/node/54151">nuvigil cash delivery cod https://www.rom.by/tema-na-forume/nuvigil-buy-canada">buy cheap nuvigil ipharmacy https://www.castnblastadvisor.com/nuvigil-how-purchase">nuvigil discount fedex no prescription https://www.danduo168.com/en/artworks/692/nuvigil-buy-canada">want to order nuvigil http://ph-ed-plus.nspu.ru/article/18220">free prescription nuvigil free shipping http://polden.info/story/nuvigil-can-i-buy">how to order nuvigil http://www.2008.zbaszyn1938.pl/zbaszyn/archive/nuvigil-buy-canada">buy nuvigil usa http://www.familygalactictravel.com/node/3443">want to order nuvigil https://rus.langnotes.ru/songs/nuvigil-buy-canada-no-prescription">buy nuvigil 50mg 180 tablets http://dev.nikol-buket.com/content/nuvigil-fedex-online-cod">can you order nuvigil online http://old-bxl.jeunescathos.org/fr/content/nuvigil-cod-overnight-delivery">fedex nuvigil online cod https://reflexologie-cerilly.fr/en/node/4592">how to purchase nuvigil https://slp.millingtonpubliclibrary.org/content/nuvigil-canada-online-pharmacy-yoamoabarranquilla">buy cheap nuvigil ipharmacy https://hr-life.ru/node/54151">buy nuvigil er https://mnbride.com/your-couple-name-3213">can you order nuvigil online https://rus.langnotes.ru/songs/nuvigil-buy-canada-no-prescription">buy nuvigil 50mg 180 tablets https://www.intellectualpedia.org/countyelectron-nuvigil-money-order">cod nuvigil overnight delivery https://jeunescathos-bxl.org/fr/content/nuvigil-buy-montgomery">buying nuvigil on line https://www.horecascout.nl/vacatures/5723/nuvigil-buying-online-without-prescription">free prescription nuvigil free shipping https://hr-life.ru/node/54151">purchase nuvigil uk delivery https://www.intellectualpedia.org/countyelectron-nuvigil-money-order">buy cheap nuvigil cod https://equicted.de/node/5671">buy codest online nuvigil Post link: https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/m-p/2164324#M205 Post author: @RishavKaaraTech | Email Author Reported by: rgjvhfiy | Email Reporter The reported post has 3 replies.

[滥用] 发布者：@RishavKaaraTech /板：Taplinx-SDK /举报人：ydgeafy ydgeafy报告了 @RishavKaaraTech 发布的 RFIDDiscover工具已被收购但如何使用 的帖子，原因如下： 原因： Something else Details: < a href="https://www.danduo168.com/en/artworks/693/cephalexin-generic-u-s-pharmacy"> buycheap cephalexin without presciption < a href="https://direct.needshub.com/node/28280"> pennsylvaniaorder cephalexin online < a href="http://www.le-cercle-des-sourires.fr/article/cephalexin-purchase-next-day-delivery"> where can I buy cephalexin < a href="https://www.castnblastadvisor.com/cephalexin-low-price-edinburgh"> overseaspharmacy cephalexin no prescription < a href="https://www.rom.by/tema-na-forume/cephalexin-buy-online-store"> want to purchase cephalexin < a href="https://oregonweddingday.com/your-couple-name-3289"> want to order cephalexin < a href="http://hubram.cz/content/cephalexin-cheap-paypal-uk"> low price cephalexin in edinburgh < a href="https://www.player1.app/team/post/1840523243/1464"> how购买头孢氨苄 < a href="https://evere.co/articles/cephalexin-online-pharmacy-buy"> 购买头孢氨苄 < a href="https://www.rom.by/tema-na-forume/cephalexin-buy-online-store"> genericcephalexin cost < a href="https://hetnieuweteamwerken.be/forums/forum/cephalexin-can-i-buy"> cephalexin邮购 联邦快递 < a href="http://ph-ed-plus.nspu.ru/article/18520"> 购买cephalexin next day delivery < a href="https://backend.dawahnigeria.com/audit/315572"> cephalexinonline overnight delivery cod < a href="https://ruckup.org/caregivers-forum/topic/6642"> cheap cephalexin paypal uk < a href="https://whs6570.com/node/2204"> lowprice cephalexin in edinburgh < a href="http://xn--80aah2bgapnqg.xn--p1ai/art/cephalexin-fast-generic"> cheapcephalexin prescriptions < a href="https://www.intellectualpedia.org/audiologistwholesale-cephalexin-where-buy-next"> salecheap cephalexin in leeds < a href="https://www.aairlab.com/IDev/?q=node/290"> fast generic cephalexin < a href="https://hr-life.ru/node/54011"> fastgeneric cephalexin < a href="https://www.ziveknihy.sk/autor/cephalexin-online-prescription"> onlineconsultation cephalexin online cheap < a href="https://hr-life.ru/node/54011"> buymedicine online cephalexin < a href="https://neweddingday.com/your-couple-name-4090"> buylow cost cephalexin < a href="https://www.aairlab.com/IDev/?q=node/290"> uk cephalexin s overnighted cod < a href="https://theanubianwar.com/node/6655"> online药店购买头孢氨苄 < a href="https://www.cableman.ru/node/85708"> cephalexin廉价订购处方 < a href="http://old-bxl.jeunescathos.org/fr/content/cephalexin-online-overnight-delivery-cod"> online购买头孢氨苄 < a href="https://www.cableman.ru/node/85708"> cephalexin邮寄折扣 < a href="https://www.player1.app/team/post/1840523243/1464"> pennsylvaniaorder cephalexin online < a href="https://neweddingday.com/your-couple-name-4090"> pennsylvaniaorder cephalexin online < a href="https://museusvalenciapre.grupotecopy.es/en/node/4050"> buycephalexin by phone < a href="https://new.roger24.de/cephalexin-buy-cheap-without-presciption"> bestcephalexin online delivery cash < a href="https://www.tripmayntra.com/cephalexin-discount-or-cheap-fedex"> genericcephalexin cost < a href="http://en.sp-journal.ru/article/20007"> overnight购买头孢菌素免费送货 < a href="https://wibride.com/your-couple-name-2618"> genericcephalexin lowest cost < a href="https://www.tripmayntra.com/cephalexin-discount-or-cheap-fedex"> cheapcephalexin sales us < a href="https://www.geofak85.ru/cephalexin-next-day-delivery"> whereto order next cephalexin < a href="http://www.batshaw.qc.ca/fr/node/435"> want to buy cephalexin < a href="https://californiaweddingday.com/your-couple-name-3920"> where to order next cephalexin < a href="https://darkmetal2039.com/history/cephalexin-where-buy-next"> ordercephalexin online uk < a href="https://theanubianwar.com/node/6655"> fda通用批文头孢氨苄 发布链接 ：https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/m-p/2164324#M205 帖子作者 @RishavKaaraTech|Email Author 报告人：ydgeafy |Email Reporter 报告的帖子有 3 个回复。

[滥用] 发布者：@RishavKaaraTech /板：Taplinx-SDK /举报人：qubdcnxk qubdcnxk 报告了 @RishavKaaraTech 发布的帖子 RFIDDiscover 工具已被收购，但如何使用它 ，原因如下： 原因： " 详情： < a href="http://www.gradspot.com/qa/naprosyn-generic"> naprosyn 药物价格 < a href=https://www.geofak85.ru/naprosyn-buy-now"> buynaprosyn now < a href="http://www.preprod.objetparlant.com/?q=node/2011"> naprosyn cost at walmart < a href="http://xn--37-6kci4a9aahjr0a.xn--p1ai/naprosyn-buy-online-mexican-ivanovo"> where to get naprosyn cheap < a href="https://museusvalenciades.grupotecopy.es/en/node/2421"> buynaprosyn online paypal uk < a href="https://www.ziveknihy.sk/autor/naprosyn-where-get-cheap"> genericnaprosyn 的药物 < a href="https://neweddingday.com/your-couple-name-3992"> genericnaprosyn canadian < a href="https://www.estate21.ru/naprosyn-where-buy-france"> buy品牌 naprosyn 肌腱炎 < a href="https://www.horecascout.nl/vacatures/5777/naprosyn-real-buy-online"> naprosyn250mg 在哪里购买 < a href="https://arendville.ru/naprosyn-order-cheap-online-australia"> naprosyn药物健康药物药房 < a href="https://enki.ua/advert/17185"> order naprosyn cheap online australia < a href="https://mnbride.com/your-couple-name-4298"> want order naprosyn < a href="http://fictioneer.org/content/naprosyn-were-can-i-buy"> canI purchase naprosyn < a href="https://arendville.ru/naprosyn-order-cheap-online-australia"> buynaprosyn in kingston < a href="https://jeunescathos-bxl.org/fr/content/naprosyn-where-buy-tablet"> findnaprosyn discount < a href="https://www.rapidservice.com.ec/es/content/1-carga-pesada-14875"> pharmacyNAPROSYN 购买药物 < a href="http://ph-ed-plus.nspu.ru/article/18124"> 在哪里购买 NAPROSYN VERMONT < a href="https://whs6570.com/node/2445"> NAPROSYNorder mexican < a href="http://surfing.4fan.cz/node/464"> naprosynover counter canadian < a href="https://www.aairlab.com/IDev/?q=node/311"> buy naprosyn online mexican < a href="https://www.vgame.ca/node/47208"> discountnaprosyn sale tablets < a href="https://diaslovakia.sk/content/naprosyn-order-cheap-online"> naprosyncod saturday delivery usa < a href="http://lsdsng.com/node/4500"> want to buy naprosyn < a href="http://www.xe-none.com/topic/10501"> buy品牌 naprosyn 肌腱炎 < a href="https://darkmetal2039.com/history/naprosyn-can-i-order"> naprosyn药物 健康 药品 < a href="https://oregonweddingday.com/your-couple-name-3795"> canadian萘普生价格 < a href="https://reflexologie-cerilly.fr/en/node/4774"> cani purchase naprosyn uk < a href="https://www.danduo168.com/en/artworks/692/naprosyn-line-pharmacy"> genericnaprosyn 的药物 < a href="http://dev.nikol-buket.com/content/naprosyn-help-buy"> naprosyn廉价咨询 < a href="https://wibride.com/your-couple-name-3948"> cani buy naprosyn uk < a href="http://www.familygalactictravel.com/node/3124"> naprosyn250mg 在哪里购买 < a href="https://www.itconnecta.es/naprosyn-can-i-buy-uk"> realnaprosyn buy online < a href="http://xn--37-6kci4a9aahjr0a.xn--p1ai/naprosyn-buy-online-mexican-ivanovo"> buynaprosyn tablet iowa < a href="https://www.rom.by/tema-na-forume/naprosyn-where-get-cheap"> cheapnaprosyn ach no doctors < a href="http://www.preprod.objetparlant.com/?q=node/2011"> can I purchase naprosyn uk < a href="https://www.estate21.ru/naprosyn-where-buy-france"> buycod naprosyn fast delivery < a href="https://www.trustcirclenetworks.org/issues/2386"> want to purchase naprosyn < a href="https://ruckup.org/caregivers-forum/topic/6960"> naprosyn drug health medication pharmacy < a href="https://www.w2wdev.spartlow.com/song/16624"> buynaprosyn saturday delivery < a href="https://escolesvalenciades.grupotecopy.es/val/node/1678"> genericnaprosyn canadian Post link: https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/m-p/2164324#M205 帖子作者 @RishavKaaraTech|Email Author 报告人：qubdcnxk |Email Reporter 报告的帖子有 3 个回复。

[ABUSE] Post By: @RishavKaaraTech / Board: TapLinx-SDK / Reported by: vjkhkwv vjkhkwv has reported the post RFIDDiscover tool acquired but how to use it posted by @RishavKaaraTech for the following reasons: Reason: Hate Speech Details: https://www.chstm.org/node/80729">can i purchase ambien http://www.le-cercle-des-sourires.fr/article/ambien-zolpidem-vs-lunesta-generic">ambien cheapest https://mnbride.com/your-couple-name-4060">purchase rx free ambien https://www.internationalhumanistparty.org/es/content/ambien-cr-order">ambien online zopiclone purchase soma https://www.formandoformadores.org.mx/colabora/publicaciones/ambien-buy-cr-online">find cheapest tramadol ambien https://www.player1.app/post/ambien-buy-viagra-india-generic">find cheapest tramadol ambien https://gglabs.us/node/5811">can i purchase ambien https://satto.vtranet.com/binh-luan-472">can i purchase ambien http://fictioneer.org/content/ambien-cr-order">ambien cr order https://neweddingday.com/your-couple-name-3208">purchase rx free ambien https://www.flohmy.ch/en/node/4727">want to buy ambien https://www.rapidservice.com.ec/es/content/ambien-cheap-non-prescription">can i purchase ambien http://surfing.4fan.cz/node/428">discount ambien cr https://exercisetool.cetmar.org/en/node/5278">cheap non prescription ambien https://mail.globalrealtor.co.in/node/4255">ambien without prescription in sydney http://dev.nikol-buket.com/content/ambien-can-i-purchase">buy ambien in sherbrooke https://exercisetool.cetmar.org/en/node/5278">buy ambien in british columbia http://alabasirah.com/node/8498">valium and ambien interaction generic http://old-namur.jeunescathos.org/fr/content/ambien-zolpidem-sleeping-pill-buy-0">buy ambien with paypal https://www.jobwebby.com/domainasname-stockwell-services/ambien-buy-cheap">discount ambien cr https://mail.reflexologie-cerilly.fr/hi/node/4632">ambien without prescription in idaho https://slp.millingtonpubliclibrary.org/content/ambien-online-zopiclone-purchase-soma">ambien generic photo http://santorini.cz/node/6421">want to buy ambien https://darkmetal2039.com/history/ambien-buy-australia">ambien detox generic name http://ru.ph-ed-plus.nspu.ru/article/18309">cheap non prescription ambien https://www.herzundhuf.de/node/5176">buy ambien in montreal https://www.thebiketube.com/park-paula">buy ambien paypal without prescription http://alabasirah.com/node/8498">order ambien prescription in australia http://surfing.4fan.cz/node/428">buy ambien in sherbrooke https://californiaweddingday.com/your-couple-name-3847">cheap ambien in australia https://www.flohmy.ch/en/node/4727">where can i buy ambien https://museusvalenciades.grupotecopy.es/en/node/2552">how to order ambien https://oregonweddingday.com/your-couple-name-3734">cheap ambien in australia https://www.jobwebby.ilovemarkso.com/domainasname-anthony-gmbh/ambien-buy-paypal">purchase price for ambien https://www.jobwebby.com/domainasname-stockwell-services/ambien-buy-cheap">ambien without prescription in sydney https://golemobuchino.com/content/2693/ambien-without-prescription-bulgaria">want to purchase ambien https://www.trustcirclenetworks.org/issues/2603">find cheapest tramadol ambien https://www.flohmy.ch/en/node/4727">want to purchase ambien https://www.trustcirclenetworks.org/issues/2603">buy ambien online! http://xn--80aah2bgapnqg.xn--p1ai/job/ambien-buy-cod">ambien generic photo Post link: https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/m-p/2164324#M205 Post author: @RishavKaaraTech | Email Author Reported by: vjkhkwv | Email Reporter The reported post has 3 replies.

[滥用] 发布者：@RishavKaaraTech /董事会：Taplinx-SDK /举报人：anwnlk anwnlk 报告了 @RishavKaaraTech 发布的 " RFIDDiscover 工具已获得，但如何使用"一文，原因如下： 原因：仇恨言论 详情： < a href="https://arendville.ru/atarax-and-purchase"> ataraxorder online overnight shipping < a href="https://slp.millingtonpubliclibrary.org/content/atarax-cheap-price"> discount drugs lowest price atarax < a href="https://slp.millingtonpubliclibrary.org/content/atarax-cheap-price"> atarax cheap and fast < a href="https://wibride.com/your-couple-name-2583"> fedexcheap atarax online buy < a href="https://www.xiruca.com/foro/comentarios-dudas-o-propuestas-rutas-monta/atarax-cost-order"> fedexcheap atarax online buy < a href="https://satto.vtranet.com/binh-luan-464"> genericonline atarax side effects < a href="https://www.cableman.ru/node/85778"> canI order atarax < a href="http://www.familygalactictravel.com/node/3148"> ataraxcod saturday < a href="http://sp-journal.ru/article/19840"> buyatarax online australia < a href="https://jeunescathos-bxl.org/fr/content/atarax-want-purchase"> onlineatarax pharmacy cheap < a href="http://alabasirah.com/node/8667"> buyatarax from mexico online < a href="https://slp.millingtonpubliclibrary.org/content/atarax-cheap-price"> atarax cod saturday < a href="https://www.xiruca.com/foro/comentarios-dudas-o-propuestas-rutas-monta/atarax-cost-order"> buyatarax shipped cod < a href="http://dev.nikol-buket.com/content/atarax-how-get-cheapest"> genericatarax to buy < a href="http://surfing.4fan.cz/node/397"> where我可以买阿他乐吗 < a href="http://www.essen-bei-krebs.de/rezepte/vorspeisen/atarax-want-order"> genericonline atarax side effects < a href="https://masters.adminskiracing.com/node/419004"> avaliablity of generic atarax < a href="http://www.essen-bei-krebs.de/rezepte/vorspeisen/atarax-want-order"> buyatarax online canadian health < a href="http://shop.ls-s.ru/product/10234"> buyatarax from mexico online < a href="https://www.rom.by/tema-na-forume/atarax-where-purchase-next"> want to purchase atarax < a href="https://www.internationalhumanistparty.org/es/content/atarax-buy-discount"> atarax无需处方 < a href="https://arendville.ru/atarax-and-purchase"> cheapest阿特拉克价格 < a href="http://alabasirah.com/node/8667"> lowerprice atarax < a href="https://www.jobwebby.ilovemarkso.com/33/atarax-lower-price"> purchasecheap atarax in florida < a href="https://www.martensfamily.co.za/node/3183"> where to buy next atarax < a href="https://direct.needshub.com/node/28450"> buyingatarax free delivery < a href="https://www.internationalhumanistparty.org/es/content/atarax-buy-discount"> atarax便宜的美国供应商 < a href= " https://jeunescathos-bxl.org/fr/content/atarax-want-purchase " > 下次在哪里订购 atarax < a href= " https://gglabs.us/node/5931 " > atarax 带处方的最低价格 < a href= " https://www.danduo168.com/en/artworks/692/atarax-no-rx-overnight " > 如何获得最便宜的 atarax < a href= " https://arendville.ru/atarax-and-purchase " > 购买atarax online canadian health < a href="http://ysrp.bnl.bm/review/atarax-ordering-best-buy"> buycheapest atarax no prescription < a href="https://openreviewhub.org/applicant-reviewers/goodwinbustard/become-reviewer-17"> getatarax buy cod < a href="https://www.internationalhumanistparty.org/es/content/atarax-buy-discount"> buyatarax shipped cod < a href="https://ufa-help.ru/content/atarax-drug-find-cheap"> atarax带处方的最低价格 < a href="https://www.w2wdev.spartlow.com/song/17039"> ataraxno prescriptions needed cod < a href="https://www.geofak85.ru/atarax-avaliablity-generic"> buyatarax in perth < a href="https://darkmetalmush.net/history/atarax-online-pharmacy-cheap"> how to buy atarax < a href="http://alabasirah.com/node/8667"> buycheap atarax online cod < a href="http://santorini.cz/node/6362"> cheapestatarax free Post link: https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/m-p/2164324#M205 帖子作者 @RishavKaaraTech|Email Author 报告人：anwnlk |Email Reporter 报告的帖子有 3 个回复。

MCXN947: Is there a "1588_EVENT_IN" pin available? Hello @Harry_Zhang is there a "1588_EVENT_IN" pin available? I want to synchronize the internal 1588 timer to e.g. an external GPS PPS signal. Therefore, I need a input pin which capture the signal and store the 1588 counter. In case of a RT1170, I can found e.g. “ENET_1588_EVENT0_IN” pin. But I can not found such a pin for the N947. Best regards, Michael MCXN Re: MCXN947: Is there a "1588_EVENT_IN" pin available? Hello @michael_fischer , Thanks for your port. No, the MCXN947 does not provide an external 1588 event input pin. Hope it helps. BR Celeste Re: MCXN947: Is there a "1588_EVENT_IN" pin available? Hello @Celeste_Liu  It's a pity that such a pin is not available. I thought I had just overlooked it. Then I have to think of something else here for synchronization to a GPS PPS signal. Plan B is to add both signals to inputs from the CTIMER and thus determine the time difference. Best regards, Michael

[滥用] 发布者：@RishavKaaraTech /板：Taplinx-SDK /举报者：kvghtdb kvghtdb 报告了 @RishavKaaraTech 发布的帖子 RFIDDiscover 工具已被收购，但如何使用它 ，原因如下： 原因： 抄袭详情 ： < a href= " https://arendville.ru/leukeran-no-prescription-2mg " > 功能安全购买 leukeran < a href="https://oregonweddingday.com/your-couple-name-3520"> online药房 leukeran < a href="https://www.aairlab.com/IDev/?q=node/612"> 在弗雷斯诺购买 leukeran < a href="https://jeunescathos-bxl.org/fr/content/leukeran-order-cheapest-ups-cod"> 想要购买 leukeran < a href="http://alabasirah.com/node/8468"> 购买leukeran in georgia < a href="http://wsb2.pl/content/leukeran-buy-discount-online"> order leukeran no rx usa < a href="https://www.castnblastadvisor.com/leukeran-buy-georgia"> can我购买 leukeran < a href="http://www.batshaw.qc.ca/fr/node/375"> 如何购买 leukeran < a href="https://www.chstm.org/node/80935"> 购买leukeran in wales < a href="http://vechirka.pl.ua/ad/use-dlya-domu/20910"> codonly leukeran < a href="https://openreviewhub.org/applicant-reviewers/goodwinbustard/become-reviewer-4"> 如何在线购买 leukeran < a href="https://www.aairlab.com/IDev/?q=node/612"> 如何购买 leukeran < a href="https://ruckup.org/caregivers-forum/topic/6855"> order cheapest leukeran ups cod < a href="https://wibride.com/your-couple-name-2660"> leukeran隔夜送货无需处方 < a href="http://www.xe-none.com/topic/10492"> pharmacyleukeran 折扣 < a href="https://cdrc.nasc.org.np/application/bess-brennan-has-applied-nodefield-training-training-323"> leukeranovernight delivery no rx http://vechirka.pl.ua/ad/use-dlya-domu/20910">buy leukeran medication online https://www.danduo168.com/en/artworks/692/leukeran-no-doctor-fast-delivery">功能安全购买 leukeran < a href="http://old-namur.jeunescathos.org/fr/content/leukeran-pharmacy-online-sale"> leukeran to buy online < a href="https://cdrc.nasc.org.np/application/bess-brennan-has-applied-nodefield-training-training-323"> mailOrder discounts on leukeran < a href="https://hunam.mx/no-12951-estudios-de-factibilidad-de-proyectos"> cheap leukeran overnight < a href="https://darkmetalmush.net/history/leukeran-can-i-purchase"> buyleukeran medication online < a href="https://www.aairlab.com/IDev/?q=node/612"> where to purchase next leukeran < a href="https://neweddingday.com/your-couple-name-2686"> want to buy leukeran < a href="https://direct.needshub.com/node/28387"> leukerancod shipping < a href="http://vechirka.pl.ua/ad/use-dlya-domu/20910"> can I order leukeran < a href="http://dev.nikol-buket.com/content/leukeran-where-can-i-buy"> where订购下一个 leukeran < a href="http://xn--80ab2anoq0a.xn--p1ai/art/leukeran-where-can-i-buy"> leukeran无需处方 < a href="https://californiaweddingday.com/your-couple-name-3545"> buyLeukeran in Georgia < a href="https://www.herzundhuf.de/node/5206"> leukerancash delivery < a href="https://ruckup.org/caregivers-forum/topic/6855"> buy discount leukeran online < a href="https://neweddingday.com/your-couple-name-2686"> mailOrder discounts on leukeran < a href="https://mail.reflexologie-cerilly.fr/hi/node/4739"> ordercheap cost leukeran < a href="https://www.geofak85.ru/leukeran-buy-soft-alabama"> leukeran药房在线销售 < a href="http://www.2008.zbaszyn1938.pl/zbaszyn/archive/leukeran-buy-georgia"> leukeran在线处方 < a href="http://www.batshaw.qc.ca/fr/node/375"> leukeran delivered cod fedex < a href="https://equicted.de/node/5588"> buyleukeran.orghttp://xn--80ab2anoq0a.xn--p1ai/art/leukeran-where-can-i-buy"> leukeranovernight delivery no rx < a href="http://03otvet.ru/voprosy/stomatologiya/leukeran-cod-only"> buy leukeran in wales < a href="https://hetnieuweteamwerken.be/forums/forum/leukeran-generic-no-prescription-cod"> mailOrder discounts on leukeran Post link: https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/m-p/2164324#M205 帖子作者：@RishavKaaraTech | Email Author @RishavKaaraTech|Email Author 报告人：kvghtdb |Email Reporter 报告的帖子有 3 个回复。

[滥用] 发布者：@RishavKaaraTech /板：Taplinx-SDK /举报人：mzhaqq mzhaqq 报告了 @RishavKaaraTech 发布的帖子 RFIDDiscover 工具已被收购，但如何使用它 ，原因如下： 原因： 抄袭 详情： < a href="https://www.worldcolleges.info/node/29810"> 廉价的imuran without rx < a href="https://arendville.ru/imuran-medicine-generic"> where to order next imuran < a href="https://californiaweddingday.com/your-couple-name-2700"> buyimuran 供应商 < a href= " https://www.flohmy.ch/en/node/4579 " > 购买imuran azasan 税务摊销收益成本 < a href= " http://shop.ls-s.ru/product/10421 " > imuran购买最便宜价格的处方 < a href="https://www.flohmy.ch/en/node/4579"> 折扣imuran pain < a href="https://enki.ua/advert/17270"> 在全球范围内在线购买 imuran < a href="http://lsdsng.com/node/4384"> 我可以购买 imuran < a href="https://www.spinsheet.com/century-club-log/imuran-cheap-imported"> onlinediscount imuran < a href="https://diaslovakia.sk/content/imuran-how-buy"> low硫唑嘌呤依木兰价格 < a href="https://darkmetalmush.net/history/imuran-buy-mastercard-pharmacy"> buyimuran without prescription idaho < a href="https://www.formandoformadores.org.mx/colabora/publicaciones/imuran-buy-need-prescription"> buy功能安全无处方 imuran < a href= " http://xn--80aah2bgapnqg.xn--p1ai/story/imuran-buy-mastercard-pharmacy " > 需要硫唑嘌呤依木兰仿制药 < a href="http://lsdsng.com/node/4384"> otc imuran fedex price uk < a href="https://reflexologie-cerilly.fr/en/node/4328"> buyimuran online pharmacy < a href="https://ufa-help.ru/content/imuran-can-i-buy-overnight"> buybrand imuran overnight find < a href="https://www.isupportveterans.org/node/3078"> pharmacyimuran saturday shipping thailand < a href="https://www.itconnecta.es/imuran-20-mg-without-prescription"> buygeneric imuran soft < a href="https://www.jobwebby.com/domainasname-stockwell-services/imuran-cheap-new-york"> bestprice imuran legally discounts < a href="https://slp.millingtonpubliclibrary.org/content/imuran-where-can-i-buy"> purchase imuran azasan < a href="http://shop.ls-s.ru/product/10421"> how to purchase imuran < a href="http://en.sp-journal.ru/article/19312"> buyimuran in internet < a href="http://old-bxl.jeunescathos.org/fr/content/imuran-low-price-azathioprine"> cheapimuran buy online canada < a href="https://wibride.com/your-couple-name-2669"> cheapimuran buy online canada < a href="https://www.aairlab.com/IDev/?q=node/298"> cheap imuran new york < a href="https://videocorsi.sinervis.com/?q=forum/test-course/topic/167201/imuran-discount-mastercard"> prescription imuran er < a href="https://wibride.com/your-couple-name-2669"> buy需要处方 Imuran < a href="http://old.jeunescathos.org/fr/content/imuran-manufactur-generic"> prescriptionimuran er < a href="https://videocorsi.sinervis.com/?q=forum/test-course/topic/167201/imuran-discount-mastercard"> purchase imuran cheapest pills discount < a href="http://www.familygalactictravel.com/node/3105"> noscript imuran flintshire < a href="https://www.aairlab.com/IDev/?q=node/298"> no script imuran cost < a href="http://dev.nikol-buket.com/content/imuran-buy-online-worldwide"> cheapimuran buy online canada < a href="https://www.aairlab.com/IDev/?q=node/298"> buy imuran pellets < a href="https://www.martensfamily.co.za/node/3293"> where to buy imuran azasan < a href="https://www.thebiketube.com/rockshox-taylor"> onlinediscount imuran < a href="https://videocorsi.sinervis.com/?q=forum/test-course/topic/167201/imuran-discount-mastercard"> buy imuran in internet < a href="https://museusvalenciapre.grupotecopy.es/en/node/3737"> orderimuran new zealand < a href="http://xn--80aah2bgapnqg.xn--p1ai/story/imuran-buy-mastercard-pharmacy"> cheapimuran buy online canada < a href="https://www.w2wdev.spartlow.com/song/17087"> orderimuran price < a href="http://www.sccu.chula.ac.th/node/2302"> cheap imported imuran Post link: https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/m-p/2164324#M205 帖子作者：@RishavKaaraTech | Email Author @RishavKaaraTech|Email Author 报告人：mzhaqq |Email Reporter 报告的帖子有 3 个回复。

[不正行為] 投稿者: @RishavKaaraTech / 掲示板: TapLinx-SDK / 報告者: bophdx bophdx は、 @RishavKaaraTech が投稿した 「RFIDDiscover ツールを入手したが、その使い方はわからない」という 投稿を以下の理由で報告しました。 理由：ヘイトスピーチ 詳細： メールインディアナ州でジルテックを注文する ジルテック今すぐメールで入手 オンラインジルテック代金引換 オンラインジルテック代金引換 効果ジルテック（ジルチン）処方箋不要 ジルテックをオンラインで安く購入する ジルテック10mg最安値 安いジルテック10mg錠 ジルテックをオンラインで購入することについて インターネットでジルテックを購入する 薬局ジルテック一晩中 where次のジルテックを購入する 最安値のジルテック送料無料 最も安いジルテックの1日あたりの価格 購入オンライン薬局ジルテック 購入オンライン薬局ジルテック ジルテック薬局でタダで買う ジルテック割引薬 安いジルテック ペイパル イギリス 低価格ジルテック アラセット ケンタッキー コルルベルルタラジルテックゾンバット 次のジルテックの購入場所 ジルテックbuy online dry mouth https://mail.globalrealtor.co.in/node/4242">CAN i order zyrtec http://lsdsng.com/node/4420">cheap cetzine zyrtec no doctors http://www.familygalactictravel.com/node/3385">cheapest ジルテックの1日あたりの価格 ジルテック10mg 最安値 購入オンライン薬局ジルテック ジルテックを代金引換で購入できる薬局 can私はジルテックを購入しました ジルテックの服用量を購入する 購入オンライン薬局ジルテック ジルテックヘルスソリューションズネットワークを購入する 入手ジルテック・サーテックス24の迅速な配送 ジルテックの購入方法 ジェネリックジルテックをフェデックスで購入 そしてアモキシシリン・ジルテックのジェネリック 低価格ジルテック薬の費用（翌日配送） メールインディアナ州でジルテックを注文する ジルテック処方に関する情報 投稿リンク： https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/mp/2164324#M205 投稿者: @RishavKaaraTech |作成者に電子メールを送信する 報告者： bophdx |メールによる報告 報告された投稿には3件の返信があります。

[ABUSE] Post By: @RishavKaaraTech / Board: TapLinx-SDK / Reported by: tgpbnt tgpbnt has reported the post RFIDDiscover tool acquired but how to use it posted by @RishavKaaraTech for the following reasons: Reason: Plagiarism Details: http://ph-ed-plus.nspu.ru/article/17986">want to order imovane https://darkmetalmush.net/history/imovane-buying-without-prescription">order imovane overnight http://old-bxl.jeunescathos.org/fr/content/imovane-buy-online-without-script">imovane shipped cod only http://fictioneer.org/content/imovane-how-purchase">imovane buy no prepaid http://www.preprod.objetparlant.com/?q=node/1993">imovane no rx foreign https://www.tripmayntra.com/imovane-where-purchase-next">saudi arabia sirdalud price imovane https://www.estate21.ru/story/imovane-buy-online-without-script">buy imovane from us http://www.sccu.chula.ac.th/node/2252">no prescriptin imovane fedex delivery https://museusvalenciades.grupotecopy.es/en/node/2559">imovane 2mg cheap https://oregonweddingday.com/your-couple-name-2521">imovane overnight no prescription http://ru.ph-ed-plus.nspu.ru/article/18542">imovane with cod http://old.jeunescathos.org/fr/content/imovane-free-without-prescription-online">imovane fedex delivery only http://www.xe-none.com/topic/10607">free imovane without prescription online https://mail.reflexologie-cerilly.fr/hi/node/4817">imovane no prescription overnight shipping https://www.spinsheet.com/racing-team-log/imovane-buying-without-prescription">buy imovane online without script https://www.ziveknihy.sk/autor/imovane-where-purchase-next">buy imovane online without script https://www.internationalhumanistparty.org/es/content/imovane-online-no-prescription-fedex">saudi arabia sirdalud price imovane https://cadel.ru/forum/imovane-overnight-no-prescription">vriligy v price ja imovane http://www.familygalactictravel.com/node/3083">want to purchase imovane http://ru.ph-ed-plus.nspu.ru/article/18542">legally order imovane online http://old-namur.jeunescathos.org/fr/content/imovane-where-buy-next">imovane no rx foreign http://old-namur.jeunescathos.org/fr/content/imovane-where-buy-next">no prescriptin imovane fedex delivery https://diaslovakia.sk/content/imovane-buy-online-without-script">can i order imovane http://www.preprod.objetparlant.com/?q=node/1993">where to purchase next imovane https://ufa-help.ru/content/imovane-want-purchase">imovane shipped cod only http://xn--80ab2anoq0a.xn--p1ai/art/imovane-where-buy-next">buy imovane online without script https://www.spinsheet.com/racing-team-log/imovane-buying-without-prescription">where can i buy imovane http://www.familygalactictravel.com/node/3083">cheapest plrice imovane https://stage.cc.radiant.digital/node/3353">imovane fedex delivery only https://slp.millingtonpubliclibrary.org/content/imovane-aus-order">imovane shipped cod only https://www.drupalcampnj.org/bof/imovane-online-cod">want to purchase imovane http://www.le-cercle-des-sourires.fr/lien/imovane-online-cod">buy imovane from us http://www.le-cercle-des-sourires.fr/lien/imovane-online-cod">cheapest plrice imovane http://www.sccu.chula.ac.th/node/2252">prescription pain meds imovane https://www.chstm.org/node/80740">how to order imovane http://www.le-cercle-des-sourires.fr/lien/imovane-online-cod">buy imovane cr online https://www.player1.app/team/post/995074171/1244">order imovane overnight https://www.internationalhumanistparty.org/es/content/imovane-online-no-prescription-fedex">imovane no prescription overnight shipping http://www.familygalactictravel.com/node/3083">buy imovane ireland http://en.sp-journal.ru/article/19420">want to buy imovane Post link: https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/m-p/2164324#M205 Post author: @RishavKaaraTech | Email Author Reported by: tgpbnt | Email Reporter The reported post has 3 replies.

feasibility for S32N7 update of a cohort image in independently Hi team，  Schaeffler needs to evaluate and test the OTA use case. This means that an OTA update should be performed for one cohort and observe that this cohort can be updated independently from the others and also while the other ones are in running mode. The current AP software does not support the OTA feature. But the OTA is an important topic for all customers.  do we have a document to describe how the FSS supports the OTA feature?  Is it possible to implement this scenario for the customer's proposal ? FSS_FW Re: feasibility for S32N7 update of a cohort image in independently Hello, Raoul Please see the required information as follow: Project Name*:  Schaeffler S32N79 project Customer Contact Point* (Name & Email): [email protected] (FAE) Software & Hardware Information: S32N79 SW Package Info*: FSS-FW/S32N7 RTD/GrayVIP SW Version*: FSS-FW 1.18.0/S32N7 RTD 2.0.0 /GrayVIP 1.0.5.3 Re: feasibility for S32N7 update of a cohort image in independently Hi @Yu_Song., The team has been made aware and I'll get back soon with an answer from them. In the meantime make sure to provide the following information: BSSM Contract: Yes / No Project Name*: Customer Contact Point* (Name & Email): Software & Hardware Information: SW Package Info*: HW* (Board/Chipset/Platform): SW Version*: *required Thanks a lot, Raoul Re: feasibility for S32N7 update of a cohort image in independently Hi Raoul, any feedback? BR, Yu Re: feasibility for S32N7 update of a cohort image in independently Hi Yu, You have received an email from Mircea Ionica with more information. If you have more questions please ask. If the email response is satisfactory, please mark this message as solution for this post. Tanks, Raoul Re: feasibility for S32N7 update of a cohort image in independently understand the case and thanks very much 

Abnormal gPTP pDelay (~5600ns) on S32K358 with TJA1120A PHY Hi NXP Community, I am currently working on a gPTP (IEEE 802.1AS) implementation using the S32K358 microcontroller and the TJA1120A (1000BASE-T1) Ethernet PHY. I am encountering an issue where the calculated propagation delay (pDelay) is consistently and inaccurately high, reaching approximately 5600ns. Given that my cable length is short, the expected pDelay should be significantly lower (typically in the range of tens to hundreds of nanoseconds depending on the setup). Environment MCU: S32K358 PHY: TJA1120A (connected via RGMII/SGMII) Software Stack: RTD 6.0.0, gPTP stack 1.0.0 Protocol: gPTP (802.1AS) Log [Rx][20:57:30.890] Pdelay 5642 ns [Rx][20:57:30.890] gPTP clock offset 6 ns [Rx][20:57:31.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:31.610] [Rx][20:57:31.870] Heart beat from core 0, cnt:871,GMAC time: 97s:341166759ns [Rx][20:57:31.881] Pdelay 5642 ns [Rx][20:57:31.890] gPTP clock offset 1 ns [Rx][20:57:32.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:32.610] [Rx][20:57:32.870] Heart beat from core 0, cnt:872,GMAC time: 98s:341211152ns [Rx][20:57:32.891] Pdelay 5642 ns [Rx][20:57:32.891] gPTP clock offset -6 ns [Rx][20:57:33.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:33.610] [Rx][20:57:33.870] Heart beat from core 0, cnt:873,GMAC time: 99s:341214323ns [Rx][20:57:33.890] Pdelay 5642 ns [Rx][20:57:33.890] gPTP clock offset -2 ns [Rx][20:57:34.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:34.610] [Rx][20:57:34.870] Heart beat from core 0, cnt:874,GMAC time: 100s:341176287ns [Rx][20:57:34.890] Pdelay 5642 ns [Rx][20:57:34.890] gPTP clock offset 6 ns [Rx][20:57:35.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:35.611] [Rx][20:57:35.870] Heart beat from core 0, cnt:875,GMAC time: 101s:341179474ns [Rx][20:57:35.890] Pdelay 5642 ns [Rx][20:57:35.890] gPTP clock offset 6 ns [Rx][20:57:36.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:36.610] [Rx][20:57:36.870] Heart beat from core 0, cnt:876,GMAC time: 102s:341182640ns [Rx][20:57:36.890] Pdelay 5642 ns [Rx][20:57:36.890] gPTP clock offset 2 ns [Rx][20:57:37.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:37.610] [Rx][20:57:37.870] Heart beat from core 0, cnt:877,GMAC time: 103s:341227490ns [Rx][20:57:37.890] Pdelay 5642 ns [Rx][20:57:37.890] gPTP clock offset 9 ns [Rx][20:57:38.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:38.610] [Rx][20:57:38.870] Heart beat from core 0, cnt:878,GMAC time: 104s:341189001ns [Rx][20:57:38.890] Pdelay 5642 ns [Rx][20:57:38.890] gPTP clock offset 2 ns [Rx][20:57:39.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:39.611] [Rx][20:57:39.871] Heart beat from core 0, cnt:879,GMAC time: 105s:341240063ns [Rx][20:57:39.891] Pdelay 5642 ns [Rx][20:57:39.891] gPTP clock offset -2 ns [Rx][20:57:40.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:40.620] [Rx][20:57:40.870] Heart beat from core 0, cnt:880,GMAC time: 106s:341195225ns [Rx][20:57:40.890] Pdelay 5642 ns [Rx][20:57:40.890] gPTP clock offset -3 ns [Rx][20:57:41.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:41.621] [Rx][20:57:41.870] Heart beat from core 0, cnt:881,GMAC time: 107s:341198255ns [Rx][20:57:41.890] Pdelay 5642 ns [Rx][20:57:41.890] gPTP clock offset -3 ns [Rx][20:57:42.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:42.620] [Rx][20:57:42.870] Heart beat from core 0, cnt:882,GMAC time: 108s:341201518ns [Rx][20:57:42.890] Pdelay 5642 ns [Rx][20:57:42.890] gPTP clock offset -6 ns [Rx][20:57:43.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:43.610] [Rx][20:57:43.870] Heart beat from core 0, cnt:883,GMAC time: 109s:341204713ns [Rx][20:57:43.890] Pdelay 5642 ns [Rx][20:57:43.890] gPTP clock offset -7 ns [Rx][20:57:44.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:44.610] [Rx][20:57:44.870] Heart beat from core 0, cnt:884,GMAC time: 110s:341207863ns [Rx][20:57:44.890] Pdelay 5642 ns [Rx][20:57:44.890] gPTP clock offset 6 ns [Rx][20:57:45.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:45.610] [Rx][20:57:45.870] Heart beat from core 0, cnt:885,GMAC time: 111s:341210973ns [Rx][20:57:45.890] Pdelay 5642 ns [Rx][20:57:45.890] gPTP clock offset 1 ns [Rx][20:57:46.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:46.610] [Rx][20:57:46.870] Heart beat from core 0, cnt:886,GMAC time: 112s:341214123ns [Rx][20:57:46.890] Pdelay 5642 ns [Rx][20:57:46.890] gPTP clock offset 1 ns [Rx][20:57:47.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:47.610] [Rx][20:57:47.870] Heart beat from core 0, cnt:887,GMAC time: 113s:341217209ns [Rx][20:57:47.890] Pdelay 5642 ns [Rx][20:57:47.890] gPTP clock offset -3 ns [Rx][20:57:48.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:48.611] [Rx][20:57:48.871] Heart beat from core 0, cnt:888,GMAC time: 114s:341262103ns [Rx][20:57:48.890] Pdelay 5642 ns [Rx][20:57:48.890] gPTP clock offset 2 ns [Rx][20:57:49.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:49.610] [Rx][20:57:49.870] Heart beat from core 0, cnt:889,GMAC time: 115s:341265193ns [Rx][20:57:49.890] Pdelay 5642 ns [Rx][20:57:49.890] gPTP clock offset 2 ns [Rx][20:57:50.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:50.610] [Rx][20:57:50.871] Heart beat from core 0, cnt:890,GMAC time: 116s:341226543ns [Rx][20:57:50.891] Pdelay 5642 ns [Rx][20:57:50.891] gPTP clock offset 1 ns [Rx][20:57:51.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:51.611] [Rx][20:57:51.871] Heart beat from core 0, cnt:891,GMAC time: 117s:341229653ns [Rx][20:57:51.890] Pdelay 5642 ns [Rx][20:57:51.890] gPTP clock offset 2 ns [Rx][20:57:52.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:52.611] [Rx][20:57:52.870] Heart beat from core 0, cnt:892,GMAC time: 118s:341232775ns [Rx][20:57:52.890] Pdelay 5642 ns [Rx][20:57:52.890] gPTP clock offset -2 ns [Rx][20:57:53.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:53.610] [Rx][20:57:53.870] Heart beat from core 0, cnt:893,GMAC time: 119s:341235820ns [Rx][20:57:53.890] Pdelay 5642 ns [Rx][20:57:53.890] gPTP clock offset 6 ns [Rx][20:57:54.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:54.610] [Rx][20:57:54.870] Heart beat from core 0, cnt:894,GMAC time: 120s:341238926ns [Rx][20:57:54.890] Pdelay 5642 ns [Rx][20:57:54.890] gPTP clock offset 6 ns [Rx][20:57:55.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:55.620] [Rx][20:57:55.870] Heart beat from core 0, cnt:895,GMAC time: 121s:341241948ns [Rx][20:57:55.891] Pdelay 5642 ns [Rx][20:57:55.891] gPTP clock offset -7 ns [Rx][20:57:56.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:56.620] [Rx][20:57:56.870] Heart beat from core 0, cnt:896,GMAC time: 122s:341245045ns [Rx][20:57:56.890] Pdelay 5642 ns [Rx][20:57:56.890] gPTP clock offset -2 ns [Rx][20:57:57.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:57.620] [Rx][20:57:57.871] Heart beat from core 0, cnt:897,GMAC time: 123s:341289370ns [Rx][20:57:57.890] Pdelay 5642 ns [Rx][20:57:57.890] gPTP clock offset 5 ns [Rx][20:57:58.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:58.620] [Rx][20:57:58.870] Heart beat from core 0, cnt:898,GMAC time: 124s:341251136ns [Rx][20:57:58.891] Pdelay 5642 ns [Rx][20:57:58.891] gPTP clock offset -6 ns [Rx][20:57:59.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:57:59.610] [Rx][20:57:59.870] Heart beat from core 0, cnt:899,GMAC time: 125s:341254262ns [Rx][20:57:59.890] Pdelay 5642 ns [Rx][20:57:59.900] gPTP clock offset 6 ns [Rx][20:58:00.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:00.610] [Rx][20:58:00.870] Heart beat from core 0, cnt:900,GMAC time: 126s:341257453ns [Rx][20:58:00.890] Pdelay 5642 ns [Rx][20:58:00.900] gPTP clock offset -11 ns [Rx][20:58:01.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:01.610] [Rx][20:58:01.870] Heart beat from core 0, cnt:901,GMAC time: 127s:341260397ns [Rx][20:58:01.890] Pdelay 5642 ns [Rx][20:58:01.900] gPTP clock offset 1 ns [Rx][20:58:02.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:02.610] [Rx][20:58:02.870] Heart beat from core 0, cnt:902,GMAC time: 128s:341263515ns [Rx][20:58:02.891] Pdelay 5642 ns [Rx][20:58:02.891] gPTP clock offset 5 ns [Rx][20:58:03.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:03.610] [Rx][20:58:03.870] Heart beat from core 0, cnt:903,GMAC time: 129s:341266549ns [Rx][20:58:03.890] Pdelay 5642 ns [Rx][20:58:03.890] gPTP clock offset 1 ns [Rx][20:58:04.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:04.610] [Rx][20:58:04.870] Heart beat from core 0, cnt:904,GMAC time: 130s:341269650ns [Rx][20:58:04.891] Pdelay 5642 ns [Rx][20:58:04.891] gPTP clock offset 2 ns [Rx][20:58:05.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:05.610] [Rx][20:58:05.870] Heart beat from core 0, cnt:905,GMAC time: 131s:341313959ns [Rx][20:58:05.890] Pdelay 5642 ns [Rx][20:58:05.890] gPTP clock offset -11 ns [Rx][20:58:06.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:06.610] [Rx][20:58:06.870] Heart beat from core 0, cnt:906,GMAC time: 132s:341275753ns [Rx][20:58:06.891] Pdelay 5642 ns [Rx][20:58:06.891] gPTP clock offset 2 ns [Rx][20:58:07.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:07.610] [Rx][20:58:07.870] Heart beat from core 0, cnt:907,GMAC time: 133s:341278815ns [Rx][20:58:07.890] Pdelay 5642 ns [Rx][20:58:07.890] gPTP clock offset 2 ns [Rx][20:58:08.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:08.620] [Rx][20:58:08.870] Heart beat from core 0, cnt:908,GMAC time: 134s:341281888ns [Rx][20:58:08.890] Pdelay 5642 ns [Rx][20:58:08.890] gPTP clock offset 10 ns [Rx][20:58:09.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:09.610] [Rx][20:58:09.870] Heart beat from core 0, cnt:909,GMAC time: 135s:341284897ns [Rx][20:58:09.891] Pdelay 5642 ns [Rx][20:58:09.891] gPTP clock offset -2 ns [Rx][20:58:10.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:10.620] [Rx][20:58:10.870] Heart beat from core 0, cnt:910,GMAC time: 136s:341287947ns [Rx][20:58:10.890] Pdelay 5642 ns [Rx][20:58:10.890] gPTP clock offset -7 ns [Rx][20:58:11.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:11.620] [Rx][20:58:11.870] Heart beat from core 0, cnt:911,GMAC time: 137s:341290952ns [Rx][20:58:11.891] Pdelay 5642 ns [Rx][20:58:11.891] gPTP clock offset 5 ns [Rx][20:58:12.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:12.621] [Rx][20:58:12.870] Heart beat from core 0, cnt:912,GMAC time: 138s:341294037ns [Rx][20:58:12.890] Pdelay 5642 ns [Rx][20:58:12.900] gPTP clock offset -7 ns [Rx][20:58:13.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:13.620] [Rx][20:58:13.871] Heart beat from core 0, cnt:913,GMAC time: 139s:341296990ns [Rx][20:58:13.890] Pdelay 5642 ns [Rx][20:58:13.890] gPTP clock offset 9 ns [Rx][20:58:14.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:14.620] [Rx][20:58:14.870] Heart beat from core 0, cnt:914,GMAC time: 140s:341300063ns [Rx][20:58:14.890] Pdelay 5642 ns [Rx][20:58:14.900] gPTP clock offset -3 ns [Rx][20:58:15.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:15.621] [Rx][20:58:15.870] Heart beat from core 0, cnt:915,GMAC time: 141s:341303064ns [Rx][20:58:15.890] Pdelay 5642 ns [Rx][20:58:15.900] gPTP clock offset 1 ns [Rx][20:58:16.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:16.620] [Rx][20:58:16.870] Heart beat from core 0, cnt:916,GMAC time: 142s:341306118ns [Rx][20:58:16.890] Pdelay 5642 ns [Rx][20:58:16.901] gPTP clock offset -10 ns [Rx][20:58:17.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:17.620] [Rx][20:58:17.871] Heart beat from core 0, cnt:917,GMAC time: 143s:341309426ns [Rx][20:58:17.890] Pdelay 5642 ns [Rx][20:58:17.900] gPTP clock offset 5 ns [Rx][20:58:18.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:18.621] [Rx][20:58:18.870] Heart beat from core 0, cnt:918,GMAC time: 144s:341353395ns [Rx][20:58:18.890] Pdelay 5642 ns [Rx][20:58:18.890] gPTP clock offset -7 ns [Rx][20:58:19.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:19.620] [Rx][20:58:19.870] Heart beat from core 0, cnt:919,GMAC time: 145s:341315112ns [Rx][20:58:19.890] Pdelay 5642 ns [Rx][20:58:19.900] gPTP clock offset 6 ns [Rx][20:58:20.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:20.621] [Rx][20:58:20.870] Heart beat from core 0, cnt:920,GMAC time: 146s:341318154ns [Rx][20:58:20.890] Pdelay 5642 ns [Rx][20:58:20.900] gPTP clock offset 2 ns [Rx][20:58:21.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:21.620] [Rx][20:58:21.870] Heart beat from core 0, cnt:921,GMAC time: 147s:341321066ns [Rx][20:58:21.891] Pdelay 5642 ns [Rx][20:58:21.900] gPTP clock offset 5 ns [Rx][20:58:22.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:22.620] [Rx][20:58:22.871] Heart beat from core 0, cnt:922,GMAC time: 148s:341324127ns [Rx][20:58:22.890] Pdelay 5642 ns [Rx][20:58:22.901] gPTP clock offset 1 ns [Rx][20:58:23.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:23.620] [Rx][20:58:23.871] Heart beat from core 0, cnt:923,GMAC time: 149s:341327092ns [Rx][20:58:23.890] Pdelay 5642 ns [Rx][20:58:23.900] gPTP clock offset -3 ns [Rx][20:58:24.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:24.621] [Rx][20:58:24.870] Heart beat from core 0, cnt:924,GMAC time: 150s:341330105ns [Rx][20:58:24.891] Pdelay 5642 ns [Rx][20:58:24.900] gPTP clock offset 2 ns [Rx][20:58:25.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:25.620] [Rx][20:58:25.870] Heart beat from core 0, cnt:925,GMAC time: 151s:341333013ns [Rx][20:58:25.890] Pdelay 5642 ns [Rx][20:58:25.900] gPTP clock offset -11 ns [Rx][20:58:26.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:26.620] [Rx][20:58:26.871] Heart beat from core 0, cnt:926,GMAC time: 152s:341336050ns [Rx][20:58:26.890] Pdelay 5642 ns [Rx][20:58:26.900] gPTP clock offset 1 ns [Rx][20:58:27.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:27.620] [Rx][20:58:27.870] Heart beat from core 0, cnt:927,GMAC time: 153s:341339002ns [Rx][20:58:27.890] Pdelay 5642 ns [Rx][20:58:27.900] gPTP clock offset 2 ns [Rx][20:58:28.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:28.620] [Rx][20:58:28.870] Heart beat from core 0, cnt:928,GMAC time: 154s:341342003ns [Rx][20:58:28.890] Pdelay 5642 ns [Rx][20:58:28.900] gPTP clock offset -7 ns [Rx][20:58:29.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:29.620] [Rx][20:58:29.870] Heart beat from core 0, cnt:929,GMAC time: 155s:341392895ns [Rx][20:58:29.890] Pdelay 5642 ns [Rx][20:58:29.900] gPTP clock offset -2 ns [Rx][20:58:30.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:30.620] [Rx][20:58:30.870] Heart beat from core 0, cnt:930,GMAC time: 156s:341348098ns [Rx][20:58:30.891] Pdelay 5642 ns [Rx][20:58:30.902] gPTP clock offset 5 ns [Rx][20:58:31.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:31.621] [Rx][20:58:31.870] Heart beat from core 0, cnt:931,GMAC time: 157s:341509765ns [Rx][20:58:31.890] Pdelay 5642 ns [Rx][20:58:31.900] gPTP clock offset 6 ns [Rx][20:58:32.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:32.620] [Rx][20:58:32.870] Heart beat from core 0, cnt:932,GMAC time: 158s:341353773ns [Rx][20:58:32.890] Pdelay 5642 ns [Rx][20:58:32.901] gPTP clock offset 2 ns [Rx][20:58:33.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:33.620] [Rx][20:58:33.870] Heart beat from core 0, cnt:933,GMAC time: 159s:341356620ns [Rx][20:58:33.890] Pdelay 5642 ns [Rx][20:58:33.900] gPTP clock offset -2 ns [Rx][20:58:34.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:34.620] [Rx][20:58:34.870] Heart beat from core 0, cnt:934,GMAC time: 160s:341359653ns [Rx][20:58:34.890] Pdelay 5642 ns [Rx][20:58:34.900] gPTP clock offset -2 ns [Rx][20:58:35.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:35.620] [Rx][20:58:35.870] Heart beat from core 0, cnt:935,GMAC time: 161s:341362614ns [Rx][20:58:35.890] Pdelay 5642 ns [Rx][20:58:35.900] gPTP clock offset 5 ns [Rx][20:58:36.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:36.620] [Rx][20:58:36.870] Heart beat from core 0, cnt:936,GMAC time: 162s:341365530ns [Rx][20:58:36.890] Pdelay 5642 ns [Rx][20:58:36.901] gPTP clock offset -2 ns [Rx][20:58:37.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:37.621] [Rx][20:58:37.870] Heart beat from core 0, cnt:937,GMAC time: 163s:341368499ns [Rx][20:58:37.890] Pdelay 5642 ns [Rx][20:58:37.900] gPTP clock offset 2 ns [Rx][20:58:38.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:38.620] [Rx][20:58:38.870] Heart beat from core 0, cnt:938,GMAC time: 164s:341371447ns [Rx][20:58:38.890] Pdelay 5642 ns [Rx][20:58:38.900] gPTP clock offset 10 ns [Rx][20:58:39.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:39.620] [Rx][20:58:39.870] Heart beat from core 0, cnt:939,GMAC time: 165s:341374311ns [Rx][20:58:39.891] Pdelay 5642 ns [Rx][20:58:39.900] gPTP clock offset -2 ns [Rx][20:58:40.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:40.620] [Rx][20:58:40.870] Heart beat from core 0, cnt:940,GMAC time: 166s:341377255ns [Rx][20:58:40.890] Pdelay 5642 ns [Rx][20:58:40.900] gPTP clock offset 6 ns [Rx][20:58:41.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:41.620] [Rx][20:58:41.870] Heart beat from core 0, cnt:941,GMAC time: 167s:341380135ns [Rx][20:58:41.890] Pdelay 5642 ns [Rx][20:58:41.900] gPTP clock offset -6 ns [Rx][20:58:42.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:42.620] [Rx][20:58:42.870] Heart beat from core 0, cnt:942,GMAC time: 168s:341383075ns [Rx][20:58:42.890] Pdelay 5642 ns [Rx][20:58:42.900] gPTP clock offset 1 ns [Rx][20:58:43.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:43.620] [Rx][20:58:43.870] Heart beat from core 0, cnt:943,GMAC time: 169s:341385987ns [Rx][20:58:43.890] Pdelay 5642 ns [Rx][20:58:43.900] gPTP clock offset -2 ns [Rx][20:58:44.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:44.620] [Rx][20:58:44.870] Heart beat from core 0, cnt:944,GMAC time: 170s:341388947ns [Rx][20:58:44.890] Pdelay 5642 ns [Rx][20:58:44.901] gPTP clock offset 2 ns [Rx][20:58:45.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:45.621] [Rx][20:58:45.870] Heart beat from core 0, cnt:945,GMAC time: 171s:341391864ns [Rx][20:58:45.890] Pdelay 5642 ns [Rx][20:58:45.900] gPTP clock offset -6 ns [Rx][20:58:46.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:46.620] [Rx][20:58:46.870] Heart beat from core 0, cnt:946,GMAC time: 172s:341435978ns [Rx][20:58:46.890] Pdelay 5642 ns [Rx][20:58:46.901] gPTP clock offset -7 ns [Rx][20:58:47.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:47.620] [Rx][20:58:47.871] Heart beat from core 0, cnt:947,GMAC time: 173s:341397595ns [Rx][20:58:47.890] Pdelay 5642 ns [Rx][20:58:47.900] gPTP clock offset -7 ns [Rx][20:58:48.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:48.621] [Rx][20:58:48.870] Heart beat from core 0, cnt:948,GMAC time: 174s:341400592ns [Rx][20:58:48.901] Pdelay 5642 ns [Rx][20:58:48.901] gPTP clock offset -3 ns [Rx][20:58:49.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:49.621] [Rx][20:58:49.870] Heart beat from core 0, cnt:949,GMAC time: 175s:341403475ns [Rx][20:58:49.900] Pdelay 5642 ns [Rx][20:58:49.900] gPTP clock offset 10 ns [Rx][20:58:50.592] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:50.620] [Rx][20:58:50.870] Heart beat from core 0, cnt:950,GMAC time: 176s:341406703ns [Rx][20:58:50.900] Pdelay 5642 ns [Rx][20:58:50.900] gPTP clock offset 1 ns [Rx][20:58:51.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:51.620] [Rx][20:58:51.870] Heart beat from core 0, cnt:951,GMAC time: 177s:341409279ns [Rx][20:58:51.890] Pdelay 5642 ns [Rx][20:58:51.900] gPTP clock offset 5 ns [Rx][20:58:52.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:52.620] [Rx][20:58:52.870] Heart beat from core 0, cnt:952,GMAC time: 178s:341412232ns [Rx][20:58:52.890] Pdelay 5642 ns [Rx][20:58:52.901] gPTP clock offset 2 ns [Rx][20:58:53.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:53.620] [Rx][20:58:53.870] Heart beat from core 0, cnt:953,GMAC time: 179s:341415095ns [Rx][20:58:53.890] Pdelay 5642 ns [Rx][20:58:53.900] gPTP clock offset 2 ns [Rx][20:58:54.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:54.621] [Rx][20:58:54.870] Heart beat from core 0, cnt:954,GMAC time: 180s:341417987ns [Rx][20:58:54.891] Pdelay 5642 ns [Rx][20:58:54.900] gPTP clock offset 2 ns [Rx][20:58:55.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:55.621] [Rx][20:58:55.870] Heart beat from core 0, cnt:955,GMAC time: 181s:341420859ns [Rx][20:58:55.891] Pdelay 5642 ns [Rx][20:58:55.900] gPTP clock offset 9 ns [Rx][20:58:56.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:56.620] [Rx][20:58:56.871] Heart beat from core 0, cnt:956,GMAC time: 182s:341423827ns [Rx][20:58:56.891] Pdelay 5642 ns [Rx][20:58:56.901] gPTP clock offset -14 ns [Rx][20:58:57.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:57.620] [Rx][20:58:57.871] Heart beat from core 0, cnt:957,GMAC time: 183s:341426687ns [Rx][20:58:57.890] Pdelay 5642 ns [Rx][20:58:57.900] gPTP clock offset 10 ns [Rx][20:58:58.590] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:58.621] [Rx][20:58:58.870] Heart beat from core 0, cnt:958,GMAC time: 184s:341429623ns [Rx][20:58:58.890] Pdelay 5642 ns [Rx][20:58:58.900] gPTP clock offset -7 ns [Rx][20:58:59.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:58:59.620] [Rx][20:58:59.871] Heart beat from core 0, cnt:959,GMAC time: 185s:341432414ns [Rx][20:58:59.900] Pdelay 5642 ns [Rx][20:58:59.900] gPTP clock offset -15 ns [Rx][20:59:00.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:00.620] [Rx][20:59:00.880] Heart beat from core 0, cnt:960,GMAC time: 186s:341435399ns [Rx][20:59:00.900] Pdelay 5642 ns [Rx][20:59:00.900] gPTP clock offset -7 ns [Rx][20:59:01.591] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:01.620] [Rx][20:59:01.880] Heart beat from core 0, cnt:961,GMAC time: 187s:341438254ns [Rx][20:59:01.891] Pdelay 5642 ns [Rx][20:59:01.900] gPTP clock offset -3 ns [Rx][20:59:02.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:02.621] [Rx][20:59:02.880] Heart beat from core 0, cnt:962,GMAC time: 188s:341441122ns [Rx][20:59:02.891] Pdelay 5642 ns [Rx][20:59:02.900] gPTP clock offset -3 ns [Rx][20:59:03.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:03.620] [Rx][20:59:03.871] Heart beat from core 0, cnt:963,GMAC time: 189s:341443965ns [Rx][20:59:03.900] Pdelay 5642 ns [Rx][20:59:03.900] gPTP clock offset -2 ns [Rx][20:59:04.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:04.621] [Rx][20:59:04.880] Heart beat from core 0, cnt:964,GMAC time: 190s:341446950ns [Rx][20:59:04.900] Pdelay 5642 ns [Rx][20:59:04.900] gPTP clock offset 1 ns [Rx][20:59:05.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:05.620] [Rx][20:59:05.880] Heart beat from core 0, cnt:965,GMAC time: 191s:341449798ns [Rx][20:59:05.900] Pdelay 5642 ns [Rx][20:59:05.900] gPTP clock offset 1 ns [Rx][20:59:06.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:06.620] [Rx][20:59:06.880] Heart beat from core 0, cnt:966,GMAC time: 192s:341452702ns [Rx][20:59:06.900] Pdelay 5642 ns [Rx][20:59:06.900] gPTP clock offset -6 ns [Rx][20:59:07.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:07.620] [Rx][20:59:07.880] Heart beat from core 0, cnt:967,GMAC time: 193s:341497107ns [Rx][20:59:07.890] Pdelay 5642 ns [Rx][20:59:07.900] gPTP clock offset 5 ns [Rx][20:59:08.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:08.620] [Rx][20:59:08.880] Heart beat from core 0, cnt:968,GMAC time: 194s:341458522ns [Rx][20:59:08.900] Pdelay 5642 ns [Rx][20:59:08.900] gPTP clock offset -6 ns [Rx][20:59:09.607] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:09.620] [Rx][20:59:09.880] Heart beat from core 0, cnt:969,GMAC time: 195s:341461353ns [Rx][20:59:09.891] Pdelay 5642 ns [Rx][20:59:09.900] gPTP clock offset -2 ns [Rx][20:59:10.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:10.620] [Rx][20:59:10.880] Heart beat from core 0, cnt:970,GMAC time: 196s:341464321ns [Rx][20:59:10.900] Pdelay 5642 ns [Rx][20:59:10.900] gPTP clock offset 6 ns [Rx][20:59:11.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:11.620] [Rx][20:59:11.880] Heart beat from core 0, cnt:971,GMAC time: 197s:341467185ns [Rx][20:59:11.901] Pdelay 5642 ns [Rx][20:59:11.901] gPTP clock offset 2 ns [Rx][20:59:12.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:12.620] [Rx][20:59:12.881] Heart beat from core 0, cnt:972,GMAC time: 198s:341470081ns [Rx][20:59:12.900] Pdelay 5642 ns [Rx][20:59:12.900] gPTP clock offset -7 ns [Rx][20:59:13.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:13.620] [Rx][20:59:13.880] Heart beat from core 0, cnt:973,GMAC time: 199s:341472949ns [Rx][20:59:13.900] Pdelay 5642 ns [Rx][20:59:13.900] gPTP clock offset -2 ns [Rx][20:59:14.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:14.620] [Rx][20:59:14.880] Heart beat from core 0, cnt:974,GMAC time: 200s:341475808ns [Rx][20:59:14.900] Pdelay 5642 ns [Rx][20:59:14.900] gPTP clock offset -10 ns [Rx][20:59:15.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:15.620] [Rx][20:59:15.880] Heart beat from core 0, cnt:975,GMAC time: 201s:341478643ns [Rx][20:59:15.900] Pdelay 5642 ns [Rx][20:59:15.900] gPTP clock offset 2 ns [Rx][20:59:16.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:16.620] [Rx][20:59:16.881] Heart beat from core 0, cnt:976,GMAC time: 202s:341481640ns [Rx][20:59:16.900] Pdelay 5642 ns [Rx][20:59:16.900] gPTP clock offset -6 ns [Rx][20:59:17.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:17.621] [Rx][20:59:17.880] Heart beat from core 0, cnt:977,GMAC time: 203s:341484787ns [Rx][20:59:17.900] Pdelay 5642 ns [Rx][20:59:17.900] gPTP clock offset -3 ns [Rx][20:59:18.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:18.620] [Rx][20:59:18.880] Heart beat from core 0, cnt:978,GMAC time: 204s:341535158ns [Rx][20:59:18.900] Pdelay 5642 ns [Rx][20:59:18.900] gPTP clock offset 2 ns [Rx][20:59:19.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:19.621] [Rx][20:59:19.880] Heart beat from core 0, cnt:979,GMAC time: 205s:341490316ns [Rx][20:59:19.901] Pdelay 5642 ns [Rx][20:59:19.901] gPTP clock offset -2 ns [Rx][20:59:20.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:20.620] [Rx][20:59:20.880] Heart beat from core 0, cnt:980,GMAC time: 206s:341651709ns [Rx][20:59:20.900] Pdelay 5642 ns [Rx][20:59:20.900] gPTP clock offset 9 ns [Rx][20:59:21.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:21.620] [Rx][20:59:21.880] Heart beat from core 0, cnt:981,GMAC time: 207s:341495768ns [Rx][20:59:21.900] Pdelay 5642 ns [Rx][20:59:21.900] gPTP clock offset 1 ns [Rx][20:59:22.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:22.620] [Rx][20:59:22.880] Heart beat from core 0, cnt:982,GMAC time: 208s:341498668ns [Rx][20:59:22.900] Pdelay 5642 ns [Rx][20:59:22.900] gPTP clock offset -6 ns [Rx][20:59:23.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:23.620] [Rx][20:59:23.880] Heart beat from core 0, cnt:983,GMAC time: 209s:341501419ns [Rx][20:59:23.900] Pdelay 5642 ns [Rx][20:59:23.900] gPTP clock offset -3 ns [Rx][20:59:24.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:24.621] [Rx][20:59:24.880] Heart beat from core 0, cnt:984,GMAC time: 210s:341504298ns [Rx][20:59:24.900] Pdelay 5642 ns [Rx][20:59:24.900] gPTP clock offset 9 ns [Rx][20:59:25.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:25.620] [Rx][20:59:25.880] Heart beat from core 0, cnt:985,GMAC time: 211s:341507174ns [Rx][20:59:25.900] Pdelay 5642 ns [Rx][20:59:25.900] gPTP clock offset -2 ns [Rx][20:59:26.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:26.620] [Rx][20:59:26.880] Heart beat from core 0, cnt:986,GMAC time: 212s:341509985ns [Rx][20:59:26.900] Pdelay 5642 ns [Rx][20:59:26.900] gPTP clock offset 1 ns [Rx][20:59:27.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:27.620] [Rx][20:59:27.881] Heart beat from core 0, cnt:987,GMAC time: 213s:341512829ns [Rx][20:59:27.900] Pdelay 5642 ns [Rx][20:59:27.900] gPTP clock offset -2 ns [Rx][20:59:28.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:28.620] [Rx][20:59:28.880] Heart beat from core 0, cnt:988,GMAC time: 214s:341515652ns [Rx][20:59:28.900] Pdelay 5642 ns [Rx][20:59:28.900] gPTP clock offset 6 ns [Rx][20:59:29.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:29.620] [Rx][20:59:29.880] Heart beat from core 0, cnt:989,GMAC time: 215s:341518475ns [Rx][20:59:29.900] Pdelay 5642 ns [Rx][20:59:29.900] gPTP clock offset 6 ns [Rx][20:59:30.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:30.620] [Rx][20:59:30.880] Heart beat from core 0, cnt:990,GMAC time: 216s:341521355ns [Rx][20:59:30.900] Pdelay 5642 ns [Rx][20:59:30.900] gPTP clock offset -10 ns [Rx][20:59:31.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:31.621] [Rx][20:59:31.880] Heart beat from core 0, cnt:991,GMAC time: 217s:341524186ns [Rx][20:59:31.900] Pdelay 5642 ns [Rx][20:59:31.900] gPTP clock offset 2 ns [Rx][20:59:32.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:32.620] [Rx][20:59:32.880] Heart beat from core 0, cnt:992,GMAC time: 218s:341527126ns [Rx][20:59:32.900] Pdelay 5642 ns [Rx][20:59:32.900] gPTP clock offset -7 ns [Rx][20:59:33.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:33.630] [Rx][20:59:33.880] Heart beat from core 0, cnt:993,GMAC time: 219s:341529949ns [Rx][20:59:33.900] Pdelay 5642 ns [Rx][20:59:33.900] gPTP clock offset 2 ns [Rx][20:59:34.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:34.621] [Rx][20:59:34.880] Heart beat from core 0, cnt:994,GMAC time: 220s:341532894ns [Rx][20:59:34.900] Pdelay 5642 ns [Rx][20:59:34.900] gPTP clock offset 2 ns [Rx][20:59:35.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:35.630] [Rx][20:59:35.880] Heart beat from core 0, cnt:995,GMAC time: 221s:341535786ns [Rx][20:59:35.900] Pdelay 5642 ns [Rx][20:59:35.900] gPTP clock offset 1 ns [Rx][20:59:36.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:36.620] [Rx][20:59:36.880] Heart beat from core 0, cnt:996,GMAC time: 222s:341876880ns [Rx][20:59:36.901] Pdelay 5642 ns [Rx][20:59:36.901] gPTP clock offset 6 ns [Rx][20:59:37.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:37.620] [Rx][20:59:37.880] Heart beat from core 0, cnt:997,GMAC time: 223s:341541472ns [Rx][20:59:37.900] Pdelay 5642 ns [Rx][20:59:37.911] gPTP clock offset -2 ns [Rx][20:59:38.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:38.620] [Rx][20:59:38.880] Heart beat from core 0, cnt:998,GMAC time: 224s:341544397ns [Rx][20:59:38.900] Pdelay 5642 ns [Rx][20:59:38.900] gPTP clock offset -6 ns [Rx][20:59:39.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:39.620] [Rx][20:59:39.880] Heart beat from core 0, cnt:999,GMAC time: 225s:341547244ns [Rx][20:59:39.900] Pdelay 5642 ns [Rx][20:59:39.911] gPTP clock offset 2 ns [Rx][20:59:40.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:40.620] [Rx][20:59:40.880] Heart beat from core 0, cnt:1000,GMAC time: 226s:341550132ns [Rx][20:59:40.900] Pdelay 5642 ns [Rx][20:59:40.900] gPTP clock offset 2 ns [Rx][20:59:41.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:41.620] [Rx][20:59:41.880] Heart beat from core 0, cnt:1001,GMAC time: 227s:341553310ns [Rx][20:59:41.900] Pdelay 5642 ns [Rx][20:59:41.900] gPTP clock offset 6 ns [Rx][20:59:42.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:42.620] [Rx][20:59:42.880] Heart beat from core 0, cnt:1002,GMAC time: 228s:341555875ns [Rx][20:59:42.900] Pdelay 5642 ns [Rx][20:59:42.900] gPTP clock offset -3 ns [Rx][20:59:43.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:43.620] [Rx][20:59:43.881] Heart beat from core 0, cnt:1003,GMAC time: 229s:341599909ns [Rx][20:59:43.900] Pdelay 5642 ns [Rx][20:59:43.900] gPTP clock offset 6 ns [Rx][20:59:44.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:44.630] [Rx][20:59:44.880] Heart beat from core 0, cnt:1004,GMAC time: 230s:341561570ns [Rx][20:59:44.900] Pdelay 5642 ns [Rx][20:59:44.900] gPTP clock offset -3 ns [Rx][20:59:45.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:45.620] [Rx][20:59:45.881] Heart beat from core 0, cnt:1005,GMAC time: 231s:341564470ns [Rx][20:59:45.900] Pdelay 5642 ns [Rx][20:59:45.900] gPTP clock offset 10 ns [Rx][20:59:46.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:46.621] [Rx][20:59:46.880] Heart beat from core 0, cnt:1006,GMAC time: 232s:341567378ns [Rx][20:59:46.901] Pdelay 5642 ns [Rx][20:59:46.901] gPTP clock offset 1 ns [Rx][20:59:47.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:47.620] [Rx][20:59:47.880] Heart beat from core 0, cnt:1007,GMAC time: 233s:341570266ns [Rx][20:59:47.900] Pdelay 5642 ns [Rx][20:59:47.900] gPTP clock offset 1 ns [Rx][20:59:48.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:48.620] [Rx][20:59:48.880] Heart beat from core 0, cnt:1008,GMAC time: 234s:341578101ns [Rx][20:59:48.901] Pdelay 5642 ns [Rx][20:59:48.912] gPTP clock offset 2 ns [Rx][20:59:49.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:49.632] [Rx][20:59:49.880] Heart beat from core 0, cnt:1009,GMAC time: 235s:341575827ns [Rx][20:59:49.901] Pdelay 5642 ns [Rx][20:59:49.901] gPTP clock offset -2 ns [Rx][20:59:50.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:50.630] [Rx][20:59:50.880] Heart beat from core 0, cnt:1010,GMAC time: 236s:341578780ns [Rx][20:59:50.901] Pdelay 5642 ns [Rx][20:59:50.901] gPTP clock offset -3 ns [Rx][20:59:51.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:51.630] [Rx][20:59:51.880] Heart beat from core 0, cnt:1011,GMAC time: 237s:341622902ns [Rx][20:59:51.901] Pdelay 5642 ns [Rx][20:59:51.901] gPTP clock offset -2 ns [Rx][20:59:52.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:52.630] [Rx][20:59:52.880] Heart beat from core 0, cnt:1012,GMAC time: 238s:341584515ns [Rx][20:59:52.901] Pdelay 5642 ns [Rx][20:59:52.901] gPTP clock offset -7 ns [Rx][20:59:53.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:53.620] [Rx][20:59:53.880] Heart beat from core 0, cnt:1013,GMAC time: 239s:341587350ns [Rx][20:59:53.900] Pdelay 5642 ns [Rx][20:59:53.910] gPTP clock offset -7 ns [Rx][20:59:54.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:54.630] [Rx][20:59:54.880] Heart beat from core 0, cnt:1014,GMAC time: 240s:341590553ns [Rx][20:59:54.900] Pdelay 5642 ns [Rx][20:59:54.910] gPTP clock offset 5 ns [Rx][20:59:55.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:55.630] [Rx][20:59:55.880] Heart beat from core 0, cnt:1015,GMAC time: 241s:341593392ns [Rx][20:59:55.901] Pdelay 5642 ns [Rx][20:59:55.910] gPTP clock offset -7 ns [Rx][20:59:56.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:56.630] [Rx][20:59:56.880] Heart beat from core 0, cnt:1016,GMAC time: 242s:341637467ns [Rx][20:59:56.900] Pdelay 5642 ns [Rx][20:59:56.900] gPTP clock offset -2 ns [Rx][20:59:57.602] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:57.630] [Rx][20:59:57.880] Heart beat from core 0, cnt:1017,GMAC time: 243s:341598797ns [Rx][20:59:57.900] Pdelay 5642 ns [Rx][20:59:57.911] gPTP clock offset 2 ns [Rx][20:59:58.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:58.631] [Rx][20:59:58.880] Heart beat from core 0, cnt:1018,GMAC time: 244s:341601680ns [Rx][20:59:58.900] Pdelay 5642 ns [Rx][20:59:58.910] gPTP clock offset -11 ns [Rx][20:59:59.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][20:59:59.631] [Rx][20:59:59.880] Heart beat from core 0, cnt:1019,GMAC time: 245s:341604467ns [Rx][20:59:59.900] Pdelay 5642 ns [Rx][20:59:59.910] gPTP clock offset -3 ns [Rx][21:00:00.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:00.630] [Rx][21:00:00.880] Heart beat from core 0, cnt:1020,GMAC time: 246s:341607371ns [Rx][21:00:00.900] Pdelay 5642 ns [Rx][21:00:00.914] gPTP clock offset -3 ns [Rx][21:00:01.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:01.630] [Rx][21:00:01.880] Heart beat from core 0, cnt:1021,GMAC time: 247s:341610174ns [Rx][21:00:01.900] Pdelay 5642 ns [Rx][21:00:01.910] gPTP clock offset 5 ns [Rx][21:00:02.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:02.630] [Rx][21:00:02.880] Heart beat from core 0, cnt:1022,GMAC time: 248s:341613062ns [Rx][21:00:02.901] Pdelay 5642 ns [Rx][21:00:02.911] gPTP clock offset -3 ns [Rx][21:00:03.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:03.630] [Rx][21:00:03.881] Heart beat from core 0, cnt:1023,GMAC time: 249s:341616539ns [Rx][21:00:03.901] Pdelay 5642 ns [Rx][21:00:03.911] gPTP clock offset -2 ns [Rx][21:00:04.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:04.631] [Rx][21:00:04.880] Heart beat from core 0, cnt:1024,GMAC time: 250s:341619027ns [Rx][21:00:04.900] Pdelay 5642 ns [Rx][21:00:04.910] gPTP clock offset -6 ns [Rx][21:00:05.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:05.630] [Rx][21:00:05.880] Heart beat from core 0, cnt:1025,GMAC time: 251s:341621406ns [Rx][21:00:05.900] Pdelay 5642 ns [Rx][21:00:05.910] gPTP clock offset -3 ns [Rx][21:00:06.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:06.630] [Rx][21:00:06.880] Heart beat from core 0, cnt:1026,GMAC time: 252s:341624326ns [Rx][21:00:06.900] Pdelay 5642 ns [Rx][21:00:06.910] gPTP clock offset 6 ns [Rx][21:00:07.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:07.631] [Rx][21:00:07.881] Heart beat from core 0, cnt:1027,GMAC time: 253s:341627198ns [Rx][21:00:07.900] Pdelay 5642 ns [Rx][21:00:07.911] gPTP clock offset 2 ns [Rx][21:00:08.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:08.630] [Rx][21:00:08.880] Heart beat from core 0, cnt:1028,GMAC time: 254s:341630037ns [Rx][21:00:08.900] Pdelay 5642 ns [Rx][21:00:08.910] gPTP clock offset -7 ns [Rx][21:00:09.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:09.630] [Rx][21:00:09.880] Heart beat from core 0, cnt:1029,GMAC time: 255s:341632909ns [Rx][21:00:09.900] Pdelay 5642 ns [Rx][21:00:09.911] gPTP clock offset -15 ns [Rx][21:00:10.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:10.630] [Rx][21:00:10.880] Heart beat from core 0, cnt:1030,GMAC time: 256s:341635760ns [Rx][21:00:10.900] Pdelay 5642 ns [Rx][21:00:10.911] gPTP clock offset 1 ns [Rx][21:00:11.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:11.631] [Rx][21:00:11.880] Heart beat from core 0, cnt:1031,GMAC time: 257s:341638547ns [Rx][21:00:11.900] Pdelay 5642 ns [Rx][21:00:11.911] gPTP clock offset 2 ns [Rx][21:00:12.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:12.630] [Rx][21:00:12.880] Heart beat from core 0, cnt:1032,GMAC time: 258s:341641726ns [Rx][21:00:12.900] Pdelay 5642 ns [Rx][21:00:12.910] gPTP clock offset -3 ns [Rx][21:00:13.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:13.630] [Rx][21:00:13.880] Heart beat from core 0, cnt:1033,GMAC time: 259s:341644537ns [Rx][21:00:13.900] Pdelay 5642 ns [Rx][21:00:13.910] gPTP clock offset 6 ns [Rx][21:00:14.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:14.630] [Rx][21:00:14.880] Heart beat from core 0, cnt:1034,GMAC time: 260s:341647102ns [Rx][21:00:14.900] Pdelay 5642 ns [Rx][21:00:14.911] gPTP clock offset -2 ns [Rx][21:00:15.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:15.630] [Rx][21:00:15.880] Heart beat from core 0, cnt:1035,GMAC time: 261s:341649897ns [Rx][21:00:15.900] Pdelay 5642 ns [Rx][21:00:15.910] gPTP clock offset -3 ns [Rx][21:00:16.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:16.630] [Rx][21:00:16.880] Heart beat from core 0, cnt:1036,GMAC time: 262s:341652780ns [Rx][21:00:16.900] Pdelay 5642 ns [Rx][21:00:16.911] gPTP clock offset -2 ns [Rx][21:00:17.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:17.630] [Rx][21:00:17.880] Heart beat from core 0, cnt:1037,GMAC time: 263s:341655567ns [Rx][21:00:17.900] Pdelay 5642 ns [Rx][21:00:17.912] gPTP clock offset 6 ns [Rx][21:00:18.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:18.631] [Rx][21:00:18.880] Heart beat from core 0, cnt:1038,GMAC time: 264s:341658435ns [Rx][21:00:18.900] Pdelay 5642 ns [Rx][21:00:18.910] gPTP clock offset -2 ns [Rx][21:00:19.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:19.630] [Rx][21:00:19.880] Heart beat from core 0, cnt:1039,GMAC time: 265s:341661924ns [Rx][21:00:19.901] Pdelay 5642 ns [Rx][21:00:19.911] gPTP clock offset -2 ns [Rx][21:00:20.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:20.631] [Rx][21:00:20.880] Heart beat from core 0, cnt:1040,GMAC time: 266s:341664077ns [Rx][21:00:20.900] Pdelay 5642 ns [Rx][21:00:20.910] gPTP clock offset -7 ns [Rx][21:00:21.601] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:21.632] [Rx][21:00:21.880] Heart beat from core 0, cnt:1041,GMAC time: 267s:341666965ns [Rx][21:00:21.900] Pdelay 5642 ns [Rx][21:00:21.910] gPTP clock offset -6 ns [Rx][21:00:22.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:22.630] [Rx][21:00:22.880] Heart beat from core 0, cnt:1042,GMAC time: 268s:341669820ns [Rx][21:00:22.900] Pdelay 5642 ns [Rx][21:00:22.910] gPTP clock offset -7 ns [Rx][21:00:23.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:23.631] [Rx][21:00:23.880] Heart beat from core 0, cnt:1043,GMAC time: 269s:341720604ns [Rx][21:00:23.900] Pdelay 5642 ns [Rx][21:00:23.911] gPTP clock offset 1 ns [Rx][21:00:24.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:24.630] [Rx][21:00:24.880] Heart beat from core 0, cnt:1044,GMAC time: 270s:341675503ns [Rx][21:00:24.900] Pdelay 5642 ns [Rx][21:00:24.911] gPTP clock offset -6 ns [Rx][21:00:25.600] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:25.631] [Rx][21:00:25.880] Heart beat from core 0, cnt:1045,GMAC time: 271s:341837110ns [Rx][21:00:25.901] Pdelay 5642 ns [Rx][21:00:25.910] gPTP clock offset -6 ns [Rx][21:00:26.610] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:26.631] [Rx][21:00:26.881] Heart beat from core 0, cnt:1046,GMAC time: 272s:341681614ns [Rx][21:00:26.911] Pdelay 5642 ns [Rx][21:00:26.911] gPTP clock offset 1 ns [Rx][21:00:27.611] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:27.630] [Rx][21:00:27.880] Heart beat from core 0, cnt:1047,GMAC time: 273s:341684138ns [Rx][21:00:27.911] Pdelay 5642 ns [Rx][21:00:27.911] gPTP clock offset 1 ns [Rx][21:00:28.610] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:28.630] [Rx][21:00:28.880] Heart beat from core 0, cnt:1048,GMAC time: 274s:341687059ns [Rx][21:00:28.900] Pdelay 5642 ns [Rx][21:00:28.910] gPTP clock offset -6 ns [Rx][21:00:29.610] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:29.630] [Rx][21:00:29.880] Heart beat from core 0, cnt:1049,GMAC time: 275s:341690245ns [Rx][21:00:29.900] Pdelay 5642 ns [Rx][21:00:29.911] gPTP clock offset 2 ns [Rx][21:00:30.610] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task [Rx][21:00:30.630] [Rx][21:00:30.880] Heart beat from core 0, cnt:1050,GMAC time: 276s:341692770ns [Rx][21:00:30.900] Pdelay 5642 ns [Rx][21:00:30.912] gPTP clock offset 2 ns [Rx][21:00:31.610] udp_recv_task: received 21 bytes from 192.168.0.200:62510 -> hello from udp task Re: Abnormal gPTP pDelay (~5600ns) on S32K358 with TJA1120A PHY Hello @frankie-zeng , Who's your gPTP GrandMaster?  How many hops do you have between S32K358 and GM? Can you shared simple drawing of your connection between GM and S32K358? Best regards, Pavel Re: Abnormal gPTP pDelay (~5600ns) on S32K358 with TJA1120A PHY The issue has fixed. PHY internel delay almost 4.5us

[滥用] 发布者：@RishavKaaraTech /板：Taplinx-SDK /举报人：yqdvqom yqdvqom 报告了 @RishavKaaraTech 发布的帖子 RFIDDiscover 工具已被收购，但如何使用它 ，原因如下： 原因： 其他 详情： < a href="https://whs6570.com/node/2431"> lorazepam处方费用 < a href="https://masters.adminskiracing.com/node/419591"> us无处方劳拉西泮 < a href="http://surfing.4fan.cz/node/380"> legallybuy lorazepam no rx < a href="https://www.fr.adrenal-fatigue.de/node/5397"> orderlorazepam 1mg < a href="https://slp.millingtonpubliclibrary.org/content/lorazepam-xr-buy-online-cheap"> order lorazepam cod cash delivery < a href="https://darkmetal2039.com/history/lorazepam-buy-online-usa"> orderlorazepam no prescriptin < a href="https://www.fr.adrenal-fatigue.de/node/5397"> buylorazepam next day delivery < a href="http://santorini.cz/node/6411"> want to buy lorazepam < a href="https://satto.vtranet.com/binh-luan-442"> lorazepamcod overnight < a href="https://darkmetalmush.net/history/lorazepam-can-i-buy"> buyLorazepam adhd medications < a href="http://en.sp-journal.ru/article/19515"> buylorazepam adhd medications < a href="https://mail.globalrealtor.co.in/node/4327"> buy lorazepam online consult < a href="https://museusvalenciapre.grupotecopy.es/en/node/3982"> buycheap lorazepam overnight < a href="https://www.jobwebby.ilovemarkso.com/domainasname-anthony-gmbh/lorazepam-where-order-next"> whereto buy next lorazepam < a href="https://museusvalenciapre.grupotecopy.es/en/node/3982"> buylorazepam online cod < a href="https://mnbride.com/your-couple-name-3088"> where to buy next lorazepam < a href="http://xn--80aah2bgapnqg.xn--p1ai/blog/8094/lorazepam-ambien-soma-ultram-8-ana-8-without-prescriptioninfo"> buy劳拉西泮 adhd 药物 < a href="http://fictioneer.org/content/lorazepam-can-i-purchase-online"> orderlorazepam no prescriptin < a href="http://student.dolivanov.ru/content/lorazepam-buy-hydrochloride-online"> good购买劳拉西泮的网站 < a href="http://www.le-cercle-des-sourires.fr/session/3526"> lorazepam 1mg for sale < a href="https://www.estate21.ru/lorazepam-want-order"> purchase">overnight lorazepam < a href="http://www.le-cercle-des-sourires.fr/session/3526"> buy lorazepam online kaufen < a href="https://mail.globalrealtor.co.in/node/4327"> buy lorazepam ultram < a href="https://slp.millingtonpubliclibrary.org/content/lorazepam-xr-buy-online-cheap"> lorazepam xr buy online cheap < a href="http://slorazepam 1mg < a href="https://hetnieuweteamwerken.be/forums/forum/lorazepam-cod-money-order"> buycheap lorazepam < a href="https://wibride.com/your-couple-name-3418"> buyonline rx lorazepam without < a href="https://whs6570.com/node/2431"> how to buy lorazepam < a href="http://www.le-cercle-des-sourires.fr/session/3526"> buy lorazepam in bulgaria < a href="https://ruckup.org/caregivers-forum/topic/6616"> how to purchase lorazepam < a href="https://ecuro.ru/en/node/6665"> buy lorazepam online usa < a href=http://ru.ph-ed-plus.nspu.ru/article/17967"> buylorazepam online usa < a href="http://wsb2.pl/content/lorazepam-fast-delivery-no-doctors"> buy cheap lorazepam < a href="https://arendville.ru/lorazepam-how-order"> lorazepamxr buy online cheap < a href="https://nsssp-prod-backend.parallelpublicworks.com/node/6356"> lorazepam online no script < a href="https://mail.globalrealtor.co.in/node/4327"> order cheap lorazepam no prescription < a href="http://ru.ph-ed-plus.nspu.ru/article/17967"> orderlorazepam cod cash delivery < a href="http://ph-ed-plus.nspu.ru/article/18229"> buylorazepam ultram < a href="https://ecuro.ru/en/node/6665"> cost fluoxetine 145 interactions lorazepam < a href="https://www.thebiketube.com/sci-con-aryanna"> orderlorazepam saturday delivery fedex Post link: https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/m-p/2164324#M205 帖子作者 @RishavKaaraTech|Email Author 报告人：yqdvqom |Email Reporter 报告的帖子有 3 个回复。