Multi Source Translation Content

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

Multi Source Translation Content

讨论

排序依据:
i.MX95 上的 EfficientDet-Lite0 中子转换在 LF_6.12.34_2.1.0 上产生静态输出 亲爱的恩智浦支持人员 我想报告 i.MX95 上使用 Neutron 转换流程的 EfficientDet-Lite0 的一个问题。 我的设置是 板:i.MX95 EVK 电路板支持包:Linux imx95evk 6.12.34-lts 原始模型:efficiencydet_lite0_int8.tflite 应用:带有 TensorFlow Lite 和外部 Neutron 委托的 NNStreamer 管道 输入:来自 /dev/video13 的实时摄像机数据流 我使用同一个应用程序比较了原始模型和经过 Neutron 转换的模型,并为模型的输入张量和输出张量添加了调试打印。 调查结果 原始模型 efficientdet_lite0_int8.tflite 在 CPU 上运行正常。 对于原始模型,输入张量会逐帧变化,输出张量的统计数据也会逐帧变化。 对于中子转换模型,输入张量仍在逐帧变化,但输出张量在各帧之间几乎保持不变。 因此,即使实时摄像机图像在不断变化,检测结果也是静态或空的。 我测试了两条中子路径: A) 独立组网 \(SA\) Neutron SDK 3.0.1 使用 eiq-neutron-sdk-windows-3.0.1 转换\ bin\n eutron-变流器.exe 目标运行时更新至 3.0.1 结果:转换后的模型加载,但输出几乎保持不变,并产生静态方框 B) 回滚到 6.12.34 时代的工具链 转换为: C:\nxp\eIQ_Toolkit_v1.17.0\bin\变流器\MCU_SDK_25.09.00+Linux_6.12.34_2.1.0\变流器.exe 运行时间相应回滚 结果:转换后的模型加载、输入发生变化,但输出仍几乎保持不变,检测结果仍为空 回滚转换/运行时间的行为示例: 输入变化: 输入范围: min=0 max=255 mean=141.903 sum=43592724 输入范围: min=0 max=255 mean=137.091 sum=42114370 输入范围: min=1 max=255 mean=105.373 sum=32370478 输出几乎保持不变: classes_raw 范围: min=0.000000max=0.019531平均值=0.000009 boxes_raw range: min=-2.926135max=0.535502平均值=-0.30798 回滚路径的转换统计信息显示 提取后的操作员:33 中子图4 操作员总数:371 转换的运营商:342 运算符未转换:29 这表明实时输入正确到达模型,但转换后的 Neutron 模型路径没有为 EfficientDet-Lite0 生成帧相关输出。 能否请您指点一二? 使用 电路板支持包 LF_6.12.34_2.1.0 的 i.MX95 是否有望正确支持 EfficientDet-Lite0。 该型号在 i.MX95 上是否存在 Neutron 转换问题。 此 BSP 上是否有推荐的 Neutron 参考物体检测模型,该模型已知该模型在直播视频中表现正常。 此行为是否表示变流器问题、委托/运行时问题或 EfficientDet-Lite0 不支持的运算符模式。 提前谢谢! 致以最崇高的敬意, EOF Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 你好@Rita_Wang, 谢谢,期待您的回复。 祝您也有美好的一天! 最崇高的敬意, EOF Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 你好@EOF, 我们会进行核实,然后给您答复,请稍候。 祝您有美好的一天 顺祝商祺! Rita Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 嗨,@Rita_Wang、 我使用的是 i.MX 95 19mm x 19mm 评估套件 (EVK)(i.MX 95 19mm x 19mm 评估套件 | 恩智浦半导体) 与 电路板支持包:Linux imx95evk 6.12.34-lts 我在本邮件中附上了转换后的模型(在 COCO 数据集中训练)。 该模型使用(无附加标记,只有--输入、--输出、--目标)转换: C:\nxp\eIQ_Toolkit_v1.17.0\ bin\n eutron-converter\ mcu_SDK_25.09.00+Linux_6.12.34_2.1.0\n eutron-converter.exe 致以最崇高的敬意 EOF Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 你好@EOF, 我们需要更多信息,能否请您提供客户的模型,以便进一步分析? 祝您有美好的一天 顺祝商祺! Rita Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 你好@Rita_Wang、 感谢您的回复。 是的,本邮件附有非封面文件。再次感谢您,我期待着您的答复。 祝您愉快 顺祝商祺! EOF Re: EfficientDet-Lite0 Neutron conversion on i.MX95 produces static outputs on LF_6.12.34_2.1.0 你好@EOF、 您能否向我们提供源模型,而不是中子转换模型? 我们可以尝试在我们这边转换模型,并验证是否存在任何准确性问题。谢谢。 祝您有美好的一天 顺祝商祺! Rita
查看全文
[ABUSE] Post By: @RishavKaaraTech / Board: TapLinx-SDK / Reported by: uwofhwt uwofhwt has reported the post RFIDDiscover tool acquired but how to use it posted by @RishavKaaraTech for the following reasons: Reason: Nudity or Sexual activity Details: https://www.jobwebby.ilovemarkso.com/domainasname-anthony-gmbh/aldactone-line-cheap">generic substitution for aldactone https://www.ziveknihy.sk/aldactone-cod-saturday-delivery">cheapest generic aldactone pills online http://xn--80ab2anoq0a.xn--p1ai/art/aldactone-best-price-generic">where to purchase next aldactone https://mail.reflexologie-cerilly.fr/hi/node/4821">buy fast online aldactone https://museusvalenciades.grupotecopy.es/en/node/2395">generic aldactone u s pharmacy https://mail.reflexologie-cerilly.fr/hi/node/4821">canadian online pharmacy selling aldactone https://www.lawtech.ru/subscribe/27097-17022026">cheap india generic aldactone https://mail.reflexologie-cerilly.fr/hi/node/4821">aldactone buy online overseas https://direct.needshub.com/node/28494">aldactone generic drug equivalents https://neweddingday.com/your-couple-name-2846">order aldactone overseas https://www.thebiketube.com/crossmax-rosy">aldactone medicine generic name https://museusvalenciades.grupotecopy.es/en/node/2395">generic aldactone fedex https://www.aairlab.com/IDev/?q=node/508">how to order aldactone https://museusvalenciades.grupotecopy.es/en/node/2395">buy aldactone canada pharmacy http://ph-ed-plus.nspu.ru/article/18350">aldactone online without prescription https://www.worldcolleges.info/node/29951">find cheap aldactone in arkansas http://sp-journal.ru/article/19400">cheapest aldactone without a prescription https://www.ziveknihy.sk/aldactone-cod-saturday-delivery">aldactone saturday delivery http://lsdsng.com/node/4417">where can i order aldactone https://www.player1.app/team/post/712544928/1339">generic drug names for aldactone https://www.player1.app/team/post/712544928/1339">want to order aldactone https://stage.cc.radiant.digital/node/3417">best price generic aldactone https://www.chstm.org/node/80693">buy aldactone cheap https://satto.vtranet.com/aldactone-how-purchase">aldactone 100 mg buy https://mail.reflexologie-cerilly.fr/hi/node/4821">where to order next aldactone https://satto.vtranet.com/aldactone-how-purchase">manufacturers of generic aldactone https://ufa-help.ru/content/aldactone-cheapest-without-prescription">least expensive pharmacy for aldactone https://satto.vtranet.com/aldactone-how-purchase">cheap india generic aldactone http://www.xe-none.com/topic/10552">generic aldactone no prescription india https://www.jobwebby.ilovemarkso.com/domainasname-anthony-gmbh/aldactone-line-cheap">canada order aldactone online https://cadel.ru/forum/aldactone-cheap-online-free-shipping">aldactone london united kingdom pharmacy https://www.cableman.ru/node/85786">cheap aldactone online canada https://hr-life.ru/node/54030">can i order aldactone https://neweddingday.com/your-couple-name-2846">aldactone for sale no prescription https://videocorsi.sinervis.com/?q=forum/forum-excel-avanzato/topic/167844/aldactone-buy-without-script">cod aldactone with no prescriptions https://www.jobwebby.com/domainasname-stockwell-services/aldactone-where-purchase-next">generic aldactone no prescription india https://www.tripmayntra.com/aldactone-buy-cheap">buy aldactone without a script http://xn--80ab2anoq0a.xn--p1ai/art/aldactone-best-price-generic">order cheap aldactone sale cheap https://slp.millingtonpubliclibrary.org/content/aldactone-purchase-visa">aldactone generic drug equivalents http://xn--80ab2anoq0a.xn--p1ai/art/aldactone-best-price-generic">where to purchase next aldactone 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: uwofhwt | Email Reporter The reported post has 3 replies.
查看全文
[不正行為] 投稿者: @RishavKaaraTech / 掲示板: TapLinx-SDK / 報告者: ydgeafy ydgeafy は、 @RishavKaaraTech が投稿した RFIDDiscover ツールを入手したが、その使い方について、 以下の理由で報告しました。 理由:その他 詳細: 購入処方箋なしで買える安価なセファレキシン ペンシルバニアセファレキシンをオンラインで注文する セファレキシンはどこで買えますか 海外薬局でセファレキシンを処方箋なしで購入 セファレキシンを購入したい セファレキシンを注文したい エジンバラでセファレキシンを低価格で購入 方法セファレキシンを購入する イギリスでセファレキシンを購入する ジェネリックセファレキシンの価格 セファレキシン通信販売 FedEx 購入セファレキシン翌日配送 セファレキシンオンライン翌日配達代金引換 安いセファレキシン PayPal イギリス 低価格エジンバラでのセファレキシンの価格 安いセファレキシン処方箋 セールリーズで安いセファレキシン 速効性ジェネリックセファレキシン 速いジェネリックセファレキシン オンラインセファレキシンをオンラインで安く相談する 購入オンラインでセファレキシンを購入 購入低価格のセファレキシン 英国セファレキシンS翌日配送代金引換 オンラインセファレキシンを購入できる薬局 セファレキシン安価な処方箋を注文 オンラインセファレキシンを購入する セファレキシンメール割引 ペンシルバニアセファレキシンをオンラインで注文する ペンシルバニアセファレキシンをオンラインで注文する 購入電話でセファレキシンを処方してもらう ベストセファレキシン オンライン配送 現金 ジェネリックセファレキシンの価格 一晩中セファレキシンを送料無料で購入 汎用セファレキシン最安値 安いセファレキシン販売米国 どこで次のセファレキシンを注文する セファレキシンを購入したい セファレキシンを次に注文する場所 注文セファレキシン オンライン イギリス fdaセファレキシンのジェネリック承認 投稿リンク: https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/mp/2164324#M205 投稿者: @RishavKaaraTech |作成者に電子メールを送信する 報告者: ydgeafy |メールによる報告 報告された投稿には3件の返信があります。
查看全文
[ABUSE] Post By: @RishavKaaraTech / Board: TapLinx-SDK / Reported by: wamvhs wamvhs has reported the post RFIDDiscover tool acquired but how to use it posted by @RishavKaaraTech for the following reasons: Reason: Scam or Fraud Details: https://neweddingday.com/your-couple-name-2974">purchase glucotrol online overnight hawaii http://ph-ed-plus.nspu.ru/article/18178">how to order glucotrol https://ruckup.org/caregivers-forum/topic/6952">buy 1 glucotrol xl pill http://www.familygalactictravel.com/node/3197">can i order glucotrol http://www.batshaw.qc.ca/fr/node/516">can i order glucotrol https://diaslovakia.sk/content/glucotrol-sale-cheapest-san-jose">glucotrol pharmacy order https://neweddingday.com/your-couple-name-2974">glucotrol internet pill fast delivery https://satto.vtranet.com/glucotrol-order-xl-online-jcb">generic glucotrol versus brand name https://neweddingday.com/your-couple-name-2974">cheapest glucotrol fedex overnight https://www.vgame.ca/node/47874">pharmacy no prescripition glucotrol https://enki.ua/advert/17282">buy 1 glucotrol xl pill https://nagrushe.ru/content/tami">can i order glucotrol https://www.chstm.org/node/80727">glucotrol ups delivery only https://www.estate21.ru/forum/glucotrol-cheapest-fedex-overnight">glucotrol chewable buy online http://en.sp-journal.ru/article/19523">buying glucotrol online without prescriptin https://www.worldcolleges.info/node/29938">where to buy next glucotrol http://polden.info/story/glucotrol-where-buy-next">fedex glucotrol xl online cod https://www.jobwebby.ilovemarkso.com/domainasname-anthony-gmbh/glucotrol-where-purchase-next">get cheap glucotrol xl mubwr http://xn--80ab2anoq0a.xn--p1ai/art/glucotrol-xl-generic-buy">buy glucotrol birmingham https://darkmetalmush.net/history/glucotrol-generic-cheap">buy 1 glucotrol xl pill https://museusvalenciades.grupotecopy.es/en/node/2422">buy glucotrol xl online london https://www.jobwebby.com/domainasname-erma-gmbh/glucotrol-how-buy">get cheap glucotrol xl mubwr http://www.gradspot.com/qa/glucotrol-buy-uk">cheapest online glucotrol xl qmfdy https://eventandjudge.com/node/27408">to buy glipizide glucotrol visa https://theanubianwar.com/node/6490">online pharmacy fedex cod glucotrol https://wibride.com/your-couple-name-2610">buy glucotrol online tablets international http://alabasirah.com/node/8633">order glucotrol paypal overnight wyoming https://ruckup.org/caregivers-forum/topic/6952">how to buy glucotrol http://lsdsng.com/node/4408">where to purchase next glucotrol http://lsdsng.com/node/4408">want to purchase glucotrol https://mail.reflexologie-cerilly.fr/hi/node/4463">buy glucotrol xl online london http://en.sp-journal.ru/article/19523">buy cheap glucotrol 2 https://arendville.ru/glucotrol-how-buy">order glucotrol no prescription required https://direct.needshub.com/node/28662">glucotrol internet pill fast delivery https://www.player1.app/post/glucotrol-purchase-online-overnight-hawaii">fedex glucotrol xl online cod http://callcards.ie/content/glucotrol-and-overnight-generic">purchase glucotrol xl purchase https://www.horecascout.nl/vacatures/5524/glucotrol-pharmacy-no-prescripition">pharmacy no prescripition glucotrol http://surfing.4fan.cz/node/403">generic glucotrol pharmaceutical manufacturer http://callcards.ie/content/glucotrol-and-overnight-generic">buy cheap glucotrol 2 https://museusvalenciades.grupotecopy.es/en/node/2422">glucotrol xl online buy mastercard 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: wamvhs | Email Reporter The reported post has 3 replies.
查看全文
[滥用] 发布者:@RishavKaaraTech /板:TapLinx-SDK /举报人:wiygqdux wiygqdux 报告了 @RishavKaaraTech 发布的帖子 RFIDDiscover 工具已被收购,但如何使用它 ,原因如下: 原因: 裸体或性活动 详情: < a href="https://darkmetal2039.com/history/sinemet-onlinetore-no-prescription"> sinemetdelivery ach otc belfast < a href="https://darkmetal2039.com/history/sinemet-onlinetore-no-prescription"> sinemetonlinetore no prescription < a href="https://hetnieuweteamwerken.be/forums/forum/sinemet-online-consultation-buy"> buysinemet with cod < a href="http://ph-ed-plus.nspu.ru/article/18159"> how to buy sinemet < a href="https://gglabs.us/node/6032"> sinemet cheap pharmacy without prescription < a href="https://www.worldcolleges.info/node/29873"> discountbulk sinemet < a href="https://www.jobwebby.com/domainasname-stockwell-services/sinemet-low-price-discount-discounts"> buysinemet without pre < a href="https://museusvalenciades.grupotecopy.es/en/node/2473"> buysinemet jefferson city < a href="https://evere.co/articles/sinemet-cheap-pharmacy-without-prescription"> 低价 sinemet calderdale < a href="https://videocorsi.sinervis.com/?q=forum/videocorso-su-chatgpt/topic/167247/sinemet-canadian"> canadian sinemet pills < a href=" https://www.aairlab.com/IDev/?q=node/502" > cheapest sinemet in usa online < a href="https://gglabs.us/node/6032"> to buy sinemet buy drug < a href="https://diaslovakia.sk/content/sinemet-canadian-pills"> getsinemet cheap no prescription < a href="https://arendville.ru/sinemet-otc-carbidopa-levodopa-purchase-tabs"> buyingsinemet from tesco australia < a href="https://www.aairlab.com/IDev/?q=node/502"> generic replacement for sinemet < a href="https://www.jobwebby.com/domainasname-stockwell-services/sinemet-low-price-discount-discounts"> cheapsinemet pills generic < a href="http://ru.ph-ed-plus.nspu.ru/article/18233"> sinemetcheck cheap < a href="https://slp.millingtonpubliclibrary.org/content/sinemet-price-saturday-delivery"> compounding pharmacy natural sinemet < a href="https://www.cafiac.com/?q=fr/idea/sinemet-cr-online-cod-usa"> best price sinemet pharmacy pills < a href="https://www.rapidservice.com.ec/es/content/1-carga-liviana-984"> buysinemet 在线聊天 < a href="https://www.availcalendar.com/calendar/25839"> cheapSinmet pills generic < a href="https://cdrc.nasc.org.np/application/bess-brennan-has-applied-nodefield-training-training-120"> compoundingPharmacy natural sinemet < a href="https://backend.dawahnigeria.com/audit/315073"> genericsinemet co-careldopa cheapest shop < a href="http://www.familygalactictravel.com/node/3166"> pharmacysinemet 100mg store < a href="https://www.aairlab.com/IDev/?q=node/502"> 如何购买 sinemet < a href="https://museusvalenciades.grupotecopy.es/en/node/2473"> 价格sinemet visa 税务摊销收益 https://slp.millingtonpubliclibrary.org/content/sinemet-price-saturday-delivery">how can i buy sinemet https://rahuldolas.com/forum/dummy-basic-course/topic/749/sinemet-pharmacy-100mg-store">where to order next sinemet http://www.sccu.chula.ac.th/node/2425">sinemet cr online cod usa http://kepco.co.in/?q=node/14682">best price sinemet pharmacy pills https://videocorsi.sinervis.com/?q=forum/videocorso-su-chatgpt/topic/167247/sinemet-canadian">sinemet vadodara buy http://www.gradspot.com/qa/sinemet-buying-tesco-australia">sinemet delivery ach otc belfast < a href="https://www.siriuspup.com/breeders/sinemet-canadian"> sinemetcr online cod usa < a href="http://ph-ed-plus.nspu.ru/article/18159"> pricesinemet 签证税务摊销收益 http://en.sp-journal.ru/article/19308">在线consultation buy sinemet < a href="http://www.preprod.objetparlant.com/?q=node/2013"> to buy sinemet co-careldopa rx < a href="https://wibride.com/your-couple-name-3977"> where to purchase next sinemet < a href="http://www.familygalactictravel.com/node/3166"> how to buy sinemet < a href="https://www.availcalendar.com/calendar/25839"> cheapsinemet pills generic < a href="http://pi5ny.com/node/5312"> want to buy sinemet 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 报告人:wiygqdux |Email Reporter 报告的帖子有 3 个回复。
查看全文
[滥用] 发布者:@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
查看全文
KM35 数据表 您好, 我在 KM35 的技术数据表中发现了区域功能,其中写道:"支持中性断开使用情况" 。该功能究竟是如何工作的? Re: KM35 DATASHEET 你好@Harsh2026 KM3x MCU 系列支持单芯片单相、两相和三相电表,以及流量计和其他精密测量应用。 "支持中性断开用例" -> > 这表明 MCU 支持与测量仪的中性断开继电器/切断致动器协同工作。   BR 爱丽丝
查看全文
[滥用] 发布者:@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 个回复。
查看全文
ACEはCryptoドライバとBASEで更新されていません チームの皆さん、こんにちは! S32K3コミュニティから質問をいただきました。「Ace_Ip.h」に不一致があるようです。(SW32K3_S32M27x_RTD_R23-11_7.0.0_QLP02) および "S32K388_ACE.h"(SW32K3_S32M27x_RTD_R23-11_7.0.0) SW32K3_S32M27x_RTD_R23-11_7.0.0 では、アクセスは 64 ビットです。       SW32K3_S32M27x_RTD_R23-11_7.0.0_QLP02 では、アクセスは 32 ビットです。   AESアクセラレータのドキュメントによると、32ビットアクセスのみを受け入れるように制限されています。   「S32K388_ACE.h」を更新していただけますか?BaseNXP_TS_T40D34M70I0R0フォルダ内のファイルですか? BR、 ミグ 優先度:高 RTD SECURITY_CRYPTO Re: ACE is not updated in the Crypto driver and the BASE @Migue 暗号化ドライバは、ACEレジスタにアクセスするために Ace_Ip.h の ACE_Type_32bit を使用します。 さらに、構造体名も2つのファイル間で異なっている。Ace_Ip.hではACE_Type_32bitとなっている。および S32K388_ACE.h の ACE_Type 。 これは、Cryptoが意図的にこれら2つの別々の構造を定義したことを示唆している。 私の見解では、これは問題ではないように思われます。 Re: ACE is not updated in the Crypto driver and the BASE @cuongnguyemphu さん、 両方のヘッダーファイルに同じアクセス権限が定義されているべきではないでしょうか。以下はベースRTDです。これは64ビットアクセスでは動作しません。 以下は更新された暗号化ドライバ Ace_Ip.h です。これはうまくいくでしょう: S32K388_ACE.hにACE_Typeを残しておく理由は何ですか?これにより、ACEエンジンへの適切なアクセスができなくなります。 よろしくお願いいたします。 ジョン Re: ACE is not updated in the Crypto driver and the BASE こんにちは、 では、ACE+の32ビット版Crypto Driverインターフェースを反映させるために、RTDに変更を加えるためのJiraチケットを起票すべきでしょうか? よろしくお願いいたします。 ジョン Re: ACE is not updated in the Crypto driver and the BASE こんにちは、 JIRAチケットを作成しました: [CESSCEP-168] "Ace_Ip.h" (SW32K3_S32M27x_RTD_R23-11_7.0.0_QLP02) と "S32K388_ACE.h" (SW32K3_S32M27x_RTD_R23-11_7.0.0) の不一致。 - NXP JIRA よろしくお願いいたします。 ジョン
查看全文
[滥用] 发布者:@RishavKaaraTech /板:Taplinx-SDK /举报人:kzpsiofd kzpsiofd 报告了 @RishavKaaraTech 发布的帖子 RFIDDiscover 工具已被收购,但如何使用它 ,原因如下: 原因: Something else Details: < a href="https://www.ziveknihy.sk/audiokniha/evista-order-canada"> orderevista raloxifene online no < a href="https://cdrc.nasc.org.np/application/bess-brennan-has-applied-nodefield-training-training-294"> lowerprice evista < a href="https://arendville.ru/evista-buy-buy-online"> where to buy next evista < a href="https://oregonweddingday.com/your-couple-name-3320"> evista每周购买上马登 < a href="https://www.worldcolleges.info/node/29859"> cheapevista 供应商评论 < a href= " http://www.le-cercle-des-sourires.fr/evnementmultisessions/evista-order-canada " > 最便宜的免费购买 evista < a href= " https://jeunescathos-bxl.org/fr/content/evista-buy-cod-look " > 想买 evista < a href= " https://theanubianwar.com/node/6649 " > 便宜evista 供应商评论 < a href= " https://www.spinsheet.com/century-club-log/evista-online-cod-pharmacy-96vxv " > 怎么买 evista < a href= " http://shop.ls-s.ru/product/10414 " > i想要便宜的 evista < a href="https://museusvalenciades.grupotecopy.es/en/node/2626"> 购买evista 片 < a href="https://masters.adminskiracing.com/node/420600"> orderevista overnight no script < a href="https://masters.adminskiracing.com/node/420600"> how to purchase evista < a href="https://www.geofak85.ru/evista-purchase-cr-money-purchase"> orderevista from usa < a href="https://www.thebiketube.com/magura-sibyl"> no处方 evista 片剂药物 < a href="https://www.ziveknihy.sk/audiokniha/evista-order-canada"> 购买evista london uk paypal < a href="http://www.sccu.chula.ac.th/node/2479"> best price evista mastercard < a href="http://lsdsng.com/node/4437"> where to order next evista < a href="https://new.roger24.de/evista-order-discounts-canadian-pharmacy"> getevista delivery < a href="http://xn--80ab2anoq0a.xn--p1ai/story/evista-order-canada"> buyevista bar < a href="http://xn--80ab2anoq0a.xn--p1ai/story/evista-order-canada"> bestprice evista visa 5yzq9 < a href="https://hetnieuweteamwerken.be/forums/forum/evista-order-discounts-canadian-pharmacy"> evistano script california < a href="https://arendville.ru/evista-buy-buy-online"> canI order evista < a href="https://diaslovakia.sk/content/evista-no-script-required-bestellen"> buyevista otc online < a href="https://gglabs.us/node/5969"> can i purchase evista < a href="https://satto.vtranet.com/evista-cheapest-buy-free"> i<"need evista cheap < a href="https://oregonweddingday.com/your-couple-name-3320"> where can i buy evista < a href="https://slp.millingtonpubliclibrary.org/content/evista-raloxifene-pharmaceutical-cod-accepted"> evista cheap no membership overnight < a href="http://www.le-cercle-des-sourires.fr/evnementmultisessions/evista-order-canada"> want to buy evista [email protected]">买到evista london uk paypal < a href="https://enki.ua/advert/17140"> order evista levia and viagra < a href="https://museusvalenciades.grupotecopy.es/en/node/2626"> noscript required evista bestellen < a href="https://www.formandoformadores.org.mx/colabora/publicaciones/evista-60-mg-lowest-price"> how to order evista < a href="http://www.sccu.chula.ac.th/node/2479"> cheap evista no doctor prescription < a href="http://xn--80aah2bgapnqg.xn--p1ai/art/evista-no-rx"> buycod evista 看起来像 < a href="https://masters.adminskiracing.com/node/420600"> buyevista 50 mg online < a href="https://direct.needshub.com/node/28270"> cheapevista 37 5 片 < a href="https://theanubianwar.com/node/6649"> orderevista discounts canadian pharmacy < a href="https://ruckup.org/caregivers-forum/topic/6784"> purchase evista no script utah < a href="http://old.jeunescathos.org/fr/content/evista-weekly-purchase-upper-marden"> lowerprice evista 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 报告人:kzpsiofd |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件の返信があります。
查看全文
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
查看全文
mcu-sdk-cmsis version In our projects, we use an SDK downloaded manually. We use four repositories: manifest, core, mcux, and cmsis. Currently, we are using version 24.12.00. We want to switch to the newest version, 26.03.00. I see that manifest, core and mcux have release branches for the latest version, but cmsis does not have a release branch for version 26.03.00. Can we use cmsis release version 24.12.00 together with the newer versions of the other repositories? Re: mcu-sdk-cmsis version Thank you very much for the quick and reliable response. I hadn't noticed this .yml file earlier. Best regards, Andrzej Re: mcu-sdk-cmsis version Hi @AndrzejWo  About the mcx-sdk-cmisis version. I think you can check mcuxpresso-sdk/manifests/submanifests/base.yml. - name: CMSIS repo-path: mcu-sdk-cmsis path: mcuxsdk/arch/arm/CMSIS revision: dc8b75b360fce9c864a12f1ccc54172e0c733805 groups: - core - ble_nxp userdata: track_branch: mcux_main branch_flow: false display_name: CMSIS description: Vendor-independent hardware abstraction layer for microcontrollers that are based on Arm Cortex processors, distributed by ARM. I recommend that you can follow the manifest. BR Harry
查看全文
Detailed bit-map and structure of 16-byte Die-ID (phhalSysSer_GetDieID) for PN7462AU Hi Team, I am currently working with the PN7462 NFC MCU and using the API phhalSysSer_GetDieID() to retrieve the 16-byte Die ID. I am able to successfully read the Die ID, for example: 00 00 00 00 00 01 7C 0A 39 0A 91 4E 90 36 10 04 I would like to understand more about the internal structure and meaning of these 16 bytes. Specifically: Is there any official documentation that explains the breakdown of the Die ID? Thanks and best regards, Uday Gowda Re: Detailed bit-map and structure of 16-byte Die-ID (phhalSysSer_GetDieID) for PN7462AU Hi Fabian, Thanks for reply. Re: Detailed bit-map and structure of 16-byte Die-ID (phhalSysSer_GetDieID) for PN7462AU Hello sir, Unfortunately, we don't have a document that provides a bit-map or the structure of the Die ID. Since it can be used as a constant value for each IC the structure isn't disclosed.
查看全文
[ABUSE] Post By: @RishavKaaraTech / Board: TapLinx-SDK / Reported by: pkaipody pkaipody has reported the post RFIDDiscover tool acquired but how to use it posted by @RishavKaaraTech for the following reasons: Reason: Misleading or False information Details: http://www.familygalactictravel.com/node/3304">where can i buy evista http://surfing.4fan.cz/node/514">cheap evista supplier review https://rus.langnotes.ru/exercises/evista-order-discounts-canadian-pharmacy">evista 60 mg lowest price http://callcards.ie/content/evista-where-can-i-buy">want to buy evista http://polden.info/story/evista-no-script-california">evista with no rx https://dev.beautynbrushes.com/services-provided/two-strand-twist-maroonimmortalep-0">order evista discounts canadian pharmacy http://old.jeunescathos.org/fr/content/evista-weekly-purchase-upper-marden">no script required evista bestellen https://www.flohmy.ch/en/node/4394">purchase evista no script utah http://wsb2.pl/content/evista-best-price-visa-5yzq9">how to purchase evista https://www.geofak85.ru/evista-purchase-cr-money-purchase">purchase evista augusta https://californiaweddingday.com/your-couple-name-3866">what is evista in pharmacy https://www.horecascout.nl/vacatures/5691/evista-raloxifene-no-rx-buy">where to order next evista https://www.internationalhumanistparty.org/es/content/evista-i-need-cheap">purchase evista pharmacy online sgvfx http://alabasirah.com/node/8379">evista on line pharmacy https://backend.dawahnigeria.com/audit/315056">buy evista in uk https://darkmetalmush.net/history/evista-online-discount">purchase evista pharmacy online sgvfx https://eventandjudge.com/node/27374">buying evista tablets http://www.go4go.net/go/node/158230">order evista raloxifene online no https://rus.langnotes.ru/exercises/evista-order-discounts-canadian-pharmacy">order evista overnight no script https://www.formandoformadores.org.mx/colabora/publicaciones/evista-60-mg-lowest-price">best price evista visa 5yzq9 https://cadel.ru/forum/evista-cheapest-buy-free">can i order evista https://ufa-help.ru/content/evista-i-want-cheap">buy evista buy online http://pi5ny.com/node/5342">order evista raloxifene online no https://whs6570.com/node/2338">evista weekly purchase upper marden https://backend.dawahnigeria.com/audit/315056">i want to cheap evista https://eventandjudge.com/node/27374">purchase evista no script utah https://arendville.ru/evista-buy-buy-online">evista weekly purchase upper marden https://neweddingday.com/your-couple-name-2992">evista uk no prescription https://www.xiruca.com/foro/salidas-y-quedadas-punto-encuentro-excursionistas/evista-want-purchase">purchase evista no script utah https://www.jobwebby.ilovemarkso.com/domainasname-anthony-gmbh/evista-what-pharmacy">best price evista mastercard https://www.vgame.ca/node/47431">where to purchase next evista https://www.rom.by/stranica/evista-prescription-care-called">order evista raloxifene online no https://rus.langnotes.ru/exercises/evista-order-discounts-canadian-pharmacy">evista with no rx https://diaslovakia.sk/content/evista-no-script-required-bestellen">i need evista cheap https://www.horecascout.nl/vacatures/5691/evista-raloxifene-no-rx-buy">evista no script california https://darkmetal2039.com/history/evista-online-rx-cod-accepted">want to buy evista http://pi5ny.com/node/5342">buy evista otc online https://enki.ua/advert/17140">buy online evista in atlanta https://www.spinsheet.com/century-club-log/evista-online-cod-pharmacy-96vxv">evista legally online order https://rus.langnotes.ru/exercises/evista-order-discounts-canadian-pharmacy">cheapest buy evista free 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: pkaipody | Email Reporter The reported post has 3 replies.
查看全文
[滥用] 发布者:@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 个回复。
查看全文
[滥用] 发布者:@RishavKaaraTech /板:Taplinx-SDK /举报人:lrzqcq lrzqcq 报告了 @RishavKaaraTech 发布的帖子 RFIDDiscover 工具已被收购,但如何使用它 ,原因如下: 原因: 诈骗或欺诈 详情: < a href="https://stage.cc.radiant.digital/node/3498"> 购买印度伊莫兰 < a href="https://neweddingday.com/your-couple-name-3610"> 20mg imuran without prescription < a href="https://hunam.mx/no-12682-planeacion-de-cronogramas-y-programas"> cheapest imuran pill usa < a href="http://sp-journal.ru/article/19593"> discountimuran pain < a href="https://arendville.ru/imuran-medicine-generic"> canI buy imuran overnight < a href="https://museusvalenciapre.grupotecopy.es/en/node/3737"> cheapestimuran 50mg generic < a href="https://exercisetool.cetmar.org/en/node/5267"> needimuran rx delivery < a href="http://xn--80ab2anoq0a.xn--p1ai/art/imuran-discount-mastercard"> buy功能安全无处方 imuran < a href= " https://carros-usados.us/imuran-cheapest-anywhere " > 不是script imuran cost < a href="https://www.worldcolleges.info/node/29810"> buyimuran ach saturday shipping < a href="http://en.sp-journal.ru/article/19312"> buygeneric imuran soft < a href="http://lsdsng.com/node/4384"> pharmacy imuran saturday shipping thailand < a href="https://masters.adminskiracing.com/node/419964"> cheapimuran new york < a href="https://museusvalenciades.grupotecopy.es/en/node/2653"> purchaseimuran cheapest pills discount < a href="https://www.spinsheet.com/century-club-log/imuran-cheap-imported"> buygeneric imuran soft < a href="https://hunam.mx/no-12682-planeacion-de-cronogramas-y-programas"> order imuran price < a href="https://www.flohmy.ch/en/node/4579"> buyimuran online pharmacy < a href="https://www.isupportveterans.org/node/3078"> imuranmedicine generic < a href="http://www.le-cercle-des-sourires.fr/session/3543"> buy imuran online pharmacy < a href="https://reflexologie-cerilly.fr/en/node/4328"> effectimuran pharmacy no doctors < a href="http://ph-ed-plus.nspu.ru/article/18430"> orderimuran 价格 < a href="https://www.isupportveterans.org/node/3078"> needimuran rx delivery < a href="http://fictioneer.org/content/imuran-cheapest-pill-usa"> cheapimuran purchase saturday shipping < a href="http://polden.info/story/imuran-buy-internet"> buy imuran 4 < a href="https://evere.co/articles/imuran-cheap-buy-online-canada"> manufactur generic imuran < a href="https://www.internationalhumanistparty.org/es/content/imuran-buy-need-prescription"> imuran购买最便宜价格的处方 < a href="https://www.trustcirclenetworks.org/issues/2395"> need imuran rx delivery < a href="https://golemobuchino.com/content/2557/kristiyana-stoyneva-shche-predstavi-noviya-si-tvorcheski-proekt-cvetovete-na-lyatoto"> orderimuran new zealand < a href="https://gglabs.us/node/5952"> where to buy imuran azasan < a href="http://ru.ph-ed-plus.nspu.ru/article/18188"> buyimuran 供应商 < a href= " http://www.go4go.net/go/node/158599 " > imuran选项卡没有脚本 < a href= " https://wibride.com/your-couple-name-2669 " > 便宜imuran new york < a href="https://www.internationalhumanistparty.org/es/content/imuran-buy-need-prescription"> noscript imuran cost < a href="https://californiaweddingday.com/your-couple-name-2700"> buyimuran 4 < a href="https://www.isupportveterans.org/node/3078"> 如何购买 imuran < a href="https://museusvalenciades.grupotecopy.es/en/node/2653"> orderimuran new zealand < a href="https://wibride.com/your-couple-name-2669"> orderimuran price < a href="https://gglabs.us/node/5952"> need azathioprine imuran generic < a href="http://ysrp.bnl.bm/review/imuran-cheapest-anywhere"> noscript imuran cost < a href="https://www.estate21.ru/imuran-want-purchase"> buyimuran without prescription idaho 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 报告人:lrzqcq |Email Reporter 报告的帖子有 3 个回复。
查看全文
s32k311チップのブートローダーとデバッグに関する問題 s32ds:3.5.6 rtd:7.0.0 s32k311チップを使用してブートローダーの実験を行っていた際に問題が発生しました。通常のCANを設定し、プログラムがBLプログラムからアプリに切り替わることを確認しようとしました。しかし、ジャンプ機能を追加した後、BLプログラムのCAN送信機能が動作しなくなった。デバッグのためにJ-Linkに接続しない限り、そしてデバッグが開始されると、常にデバッグ出力からの出力を受け取ります。 プログラムがシグナルSIGTRAP(トレース/ブレークポイントトラップ)を受信しました。 0x20008008 in ?? () この問題の解決にご協力いただければ幸いです。ありがとう Re: Bootloader and debugging issues on the s32k311 chip ありがとうございます。問題は既に解決しました。 Re: Bootloader and debugging issues on the s32k311 chip こんにちは、 @feixingren1さん ジャンプ自体には問題がないようです。しかし、ブートローダーのmain.cを見ると、初期化解除を行わずにアプリケーションにジャンプしているようです。これは通常、トラブルの主な原因となる。お勧めします: リセット後、アプリケーションに直接ジャンプします。起動ファイルに、特定の条件に基づいてアプリケーションを起動する最小限のコードを記述することができます。ブートローダーがアプリケーションにジャンプする必要がある場合は、ソフトウェアリセットをトリガーするだけでよく、リセット後、初期化処理の前にアプリケーションにジャンプします。これが最も安全な選択肢です。 ブートローダーの後半(多くのリソースが初期化された後)でアプリケーションにジャンプしたい場合は、初期化解除を実行することが重要です。すべての割り込みを無効にする(コアによるグローバルな無効化、ペリフェラルのレジスタによるローカルな無効化など)、ペリフェラルの初期化解除など。アプリケーションは、デフォルトリセット状態を想定しているか、またはデフォルトリセット状態にない機能を完全に認識している必要があります。 よろしくお願いいたします。 ルーカス
查看全文
[不正行為] 投稿者: @RishavKaaraTech / 掲示板: TapLinx-SDK / 報告者: gqhepwb gqhepwb は、 @RishavKaaraTech が投稿した 「RFIDDiscover ツールを入手したが、その使い方はわからない」という 記事を以下の理由で報告しました。 理由:ヘイトスピーチ 詳細: ケプラを注文したい 購入ケプラ配送フェデックス割引 薬局ジェネリックケプラを携帯 5mgケプラのコスト ケプラの価格 オンライン薬局販売 ケプラ錠を購入する アメリカン・エキスプレスでケプラを最安値で購入 最安値ケプラ購入 アメリカン・エキスプレス ケプラを次に買う場所 オレゴン州で低価格のケプラ 購入タラ ケプラ 格安 ウォルソール ケプラOTCを購入する 購入ケプラストアセール ケプラの乱用と迅速な配送 genericケプラ750mg販売 低ケプラ オレゴンの費用 http://old-bxl.jeunescathos.org/fr/content/keppra-buy-brand-overnight-medicine">how to order keppra https://www.ziveknihy.sk/keppra-price-sale-pharmacy-online">ご注文ケプラ オーバーナイト タラ 購入ケプラJCB速達 ケプラセールで購入 ケプラを代金引換で翌日配送でご注文 汎用ケプラ750mg販売 薬局ケプラ250mgジェネリック 汎用ケプラ750mg販売 ジェネリックケプラ750mg販売 購入ブランドケプラの翌日配送薬 ケプラオンラインでゲンタマイシン点眼薬をマスターカードで購入 いいえ処方箋ケプラ250mg錠 購入ケプラJCB速達 オンラインポートランドの薬局でケプラを購入できます ケプラの代金引換はどうすればいいですか 購入オンラインケプラ割引を見つける ケプラ320mgの価格 価格薬局ケプラ 購入ケプラをオンラインで合法的に入手 ケプラをフェデックスで発送 購入ケプラをオンラインで合法的に入手 ケプラをフェデックスで発送 汎用ケプラ750mg販売 最も安いケプラオンラインストア ケプラの費用(ラボック) ケプラセールで購入 投稿リンク: https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/mp/2164324#M205 投稿者: @RishavKaaraTech |作成者に電子メールを送信する 報告者: gqhepwb |メールによる報告 報告された投稿には3件の返信があります。
查看全文