Multi Source Translation Content

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Multi Source Translation Content

Discussions

Sort by:
Implementing AI/ML on KW45B41Z-EVK using eIQ TSS and Ported TFLM Middleware Hi NXP Community, I am working on an edge AI application for the KW45B41Z-EVK (Cortex-M33) and would like advice on deploying a machine learning model on this board. Since the KW45 SDK does not include the eIQ/TFLM middleware by default, my plan is: Model Training: Train an n-class classification model for time-series data using eIQ Time Series Studio (eIQ TSS). Since the KW45 is not listed as a target in eIQ TSS, I selected the FRDM-MCXN947 (Cortex-M33) as the target platform to export the model. Runtime Deployment: Port the middleware/eiq/tensorflow-lite folder from the FRDM-MCXN947 SDK into my KW45 SDK project and link it with CMSIS-NN. My Questions: Is porting the eIQ TFLM middleware from the MCXN947 SDK to the KW45 SDK a valid and supported approach? Is selecting the FRDM-MCXN947 in eIQ TSS suitable for generating models to run on the KW45? Is there any other recommended or native workflow to implement AI/ML on the KW45B41Z-EVK? Thanks for your help! Kinetis W Series MCUs Re: Implementing AI/ML on KW45B41Z-EVK using eIQ TSS and Ported TFLM Middleware Hi NXP Support Team & Community, I am writing to follow up on this inquiry, as finding a resolution is quite urgent for my current project timeline. Could someone from the NXP team please provide a quick confirmation on whether porting the eIQ/TFLM middleware from the FRDM-MCXN947 SDK over to the KW45 SDK is a valid and supported workaround? Any brief guidance or confirmation on the recommended workflow would be extremely helpful so I can confidently proceed with development. Thank you in advance for your time and assistance! KW45B41Z-EVK EIQ-TOOLKIT EIQ-TFLITE-MICRO #AI/ML Re: Implementing AI/ML on KW45B41Z-EVK using eIQ TSS and Ported TFLM Middleware Hello @Srushti_Mulimani , hope you are doing well.   If you are using eIQ Time Series Studio (TSS), I would recommend porting your project from the FRDM-MCXW71 instead. It is an officially supported target in eIQ TSS and is software compatible with the KW45. Both devices share the same Cortex-M33 core architecture and a similar memory profile, so the generated library should be a much closer match for your hardware. When using a device with such a different hardware profile as the FRDM-MCXN947 as a target for porting, there is a risk of generating incompatible models, for example, due to the differences in available RAM between both devices, or the generation of NPU-accelerated models specific to the MCXN947. Hope this helps! Best regards, Sofia.
View full article
IPCF_Example_S32R47_to_A53_M7_0 build error The default program exported from the IPCF_Example_S32R47_to_A53_M7_0 SDK fails to build, resulting in compilation errors.    Initial troubleshooting indicates that the issue stems from the timing configuration, with three clock output settings exceeding the valid range (as shown in the screenshot). Could you please clarify why this error still exists in the example program, which theoretically should not happen? Please help verify this. Thank you! wxh1_1-1788255373531.png S32 SDK for S32K1 Re: IPCF_Example_S32R47_to_A53_M7_0 build error Hello, For S32R47 products please get in  touch with direct NXP support assigned to you. petervlna_0-1788264837185.png Possible root cause  could be S32CT version mismatch. Best regards, Peter
View full article
EMI EMC 合规性证书和测试报告 大家好, 请帮忙确认一下下面提到的15W接收器套件是否符合EMI/EMC标准。 零件号:WPR1500-HV 产品描述 - 高压无线充电接收器 此致, 帕尔特·巴夫萨尔 Re: EMI EMC Compliance certificate and test report 你好@P907 , 感谢你的帖子。此EVK主要用于评估并通过基本的EMI/EMC测试,以符合CE标准。总的来说,我们的解决方案与市场上通用的解决方案之间并没有什么重大区别。 希望对您有所帮助。 BR 塞莱斯特 Re: EMI EMC Compliance certificate and test report 嗨, Celeste, 感谢您的回复。 能否请您帮忙分享一下测试报告及其结果?因此,我们将检查对这款 EVK 执行了哪些基本的 EMI/EMC 测试。 问候, 帕尔特·巴夫萨尔 Re: EMI EMC Compliance certificate and test report 你好@P907 , 当然,我可以和你分享。但是,这些材料不适合在社区等公共平台上分享。我稍后会通过私人邮件发送给你。请留意您的收件箱。 此致, 塞莱斯特 Re: EMI EMC Compliance certificate and test report 嗨,Celeste, 感谢您分享所请求的EVM的EMI/EMC测试报告。 此致, 帕尔特·巴夫萨尔
View full article
S32G399A IIC Configuration Hello, I plan to use the I2C4 module of the S32G399 to configure an external PMIC. I would like to ask if this I2C4 module can be configured at a low level via the A core (e.g., clock frequency, pull-up/pull-down resistors, address, etc.)? We will not be using the M core for now. Therefore, we want to use the A core for low-level I/O configuration of the S32G. MichaelTao_0-1788251860175.pngMichaelTao_0-1788251860175.png Re: S32G399A IIC 配置 Hello, @MichaelTao Hello, yes, it is possible. The A core can be configured with the I2C4 module. BR Chenyin Re: S32G399A IIC 配置 you may try with s32 design studio for I2C low level driver configuration
View full article
EMI/EMC適合証明書および試験報告書 チームの皆さん、こんにちは。 下記の15W受信キットがEMI/EMC準拠かどうか、確認していただけませんか? 部品番号:WPR1500-HV 説明 - 高電圧ワイヤレス充電レシーバ よろしくお願いいたします。 パース・バヴサル Re: EMI EMC Compliance certificate and test report こんにちは、セレステさん。 ご返信ありがとうございます。 検査結果と検査結果の共有を手伝っていただけませんか?そこで、このEVKに対して基本的なEMI/EMCテストが行われているかを確認します。 よろしくお願いいたします。 パース・バヴサル Re: EMI EMC Compliance certificate and test report こんにちは、 @P907 さん。 投稿ありがとうございます。このEVKは主に評価用であり、CE規格に準拠するための基本的なEMI/EMC試験に合格する必要があります。一般的に、当社のソリューションと市販の一般的なソリューションの間に大きな違いはありません。 お役に立てば幸いです。 BR セレステ Re: EMI EMC Compliance certificate and test report こんにちは、 @P907 さん。 もちろん、あなたと共有できます。ただし、これらの資料はコミュニティなどの公開プラットフォームでの共有には適していません。後ほど、プライベートメールでお送りします。受信トレイをこまめに確認してください。 よろしくお願いいたします。 セレステ Re: EMI EMC Compliance certificate and test report こんにちは、セレステさん。 ご依頼いただいたEVMのEMI/EMC試験報告書をご共有いただきありがとうございます。 よろしくお願いいたします。 パース・バヴサル
View full article
RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun Unfortunately I can't directly connect the mipi output to this LCD, so LT8918 is added, but I don't seem to have problems with that. The test pattern goes through well onto that device and also my debug log shows that it syncs and passes basic setup. But I do get problems with the output. The current code I have is for a very simple small memory buffer (128x256) in the middle of 800x1280 screen. No need to look at the actual output screen, but it looks very distorted. Also in printed diagnostics I get a lot of underrun error as if the DMA is not getting data quickly enough for an entire row write. So, I'm not any expert in LCDs or NXP registers. Am I making some dumb mistake somewhere? There's plenty of uncertainty. Is SRAM_OC1 actually quite slow? Maybe there's some AXI or DMA setting to get the timings right? I reconfigured it in the MPU code to be noncached, but maybe that also is a mistake. Unfortunately I don't see a difference whether it's default or ncache region. There are a lof of other things to consider, like I tried changing the stride length to be the entire 800pixel row instead of the smaller 128 layer 0 size. The RGB pixel clock is slower than the MIPI byte clock, but I'd expect MIPI to be much faster anyway because it has 2 lines instead of the RGB parallel 24 connections. And also, the reason why I'm making such a small layer 0 area is because SDRAM might have errors. I am reducing this into a smaller controlled piece to get away from that uncertainty, but seems even in here I can't find exactly what's going wrong. It's neat to have come this far but also quite frustrating that I don't see what to do to get more progress. The background single color displays all work fine, also the test patterns make nice-shaped bar regions, so I don't think it's a real 'LCD' problem, it looks instead like the RAM buffer read or LCDIFv2 putting that to the parallel output has some timing issue. How could I debug this? Thanks. Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun I've tried a few more things, and now it actually looks like a stable output without underrun errors, at least according to my printed diagnostic. I think the primary change has been the first one, and other changes are a bit more difficult actually, but listing them for clarity. This particular setup is still RGB888 and I haven't wanted to change to experiment with alpha layer drawing yet as it's still not super good. 1. make the pixel clock much slower, down to a refresh closer to 15Hz. Maybe the DMA has extra time to work? But like you said, OCRAM should be fast. I have it set up to be an NCACHE region in that space too, in the MPU config. 2. the colors used are only black and white. Trying a green background actually introduces some background problems where the green can get shifted into an RGB pattern changing every row (off by 1 byte?). 3. the RAM layer 0 width is changed to 256 to match the height 256. Actually it's also fine as 128 height, just this particular log is 256 and you can see the stride changes too to 768. 4. The video settings for front porch and back porch are much bigger. I suspect this isn't the primary factor, I've also tried these settings at faster speeds, not super helpful. The datasheet maximum allows Hfp + Hbp + Hs to be as large as desired, is there any reason to have more than the 200 total here? Vertical settings are the ones limited to 250 altogether. So anyway, it's interesting! Technically the LCD datasheet says that it should be run at minimum 22Hz, but I don't see flickering on the white section. I'd love to run it faster. I haven't paid attention to DMA on RT1172 at all, is there anything to do to run it faster or give it more priority or something? Does LCDIFv2 have other settings for this? Particularly because OCRAM should be super fast, I'm surprised that slowing down so much had this effect. Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun Right. Thanks very much! Let's try more things. Here's another log. I wanted to stick with RGB888. Is there some reason ARGB8888 would be better for this? I might try playing with alpha sometime. CTRLDESCL5: 0xD8000260 I checked in the reference manual, the BPP setting is in bits 27-24, so that '8' indicates I successfully put it in RGB888, or so it seems. the last bytes seem unrelated and alpha settings seem harmlessly off. The screen output looks different but not fixed. Perhaps improved? There's still wraparound, but less aggressive. I've also experimented with increasing the speed of the pixel clock, not sure if that helps or hurts. I could try more video setting changes? I had thought my 25% Hsync settings were very strong here, but then again, I've never done this before. What makes a setting particularly good? Is Vsync relevant too? There's a LT8918 bridge that also needs to get these settings input, but I can also manage that. Am I limited to guessing the right numbers to put in? The driver is JD9365DA-H3, if that helps. This is a strange package with a touchscreen too, but I have no problems with that. Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun Hi @davidpspeedtech , Thanks for the update! However, the issue is that some of your settings aren't consistent. 0xD9000260 → the format latched in hardware is ARGB8888 (32-bit/pixel). So when you set stride = 384 (=128×3, RGB888), the hardware still fetches 128×4 = 512 bytes/row → per-line misalignment, reads past the buffer, and underrun. You changed only the stride or the BPP macro each time, but the hardware actually obeys .pixelFormat , which stayed ARGB8888 — the four values were never consistent. Please make them all consistent as 32-bit ARGB8888 or RGB888 in one shot:   #define SMALL_LAYER_0_BPP 4U #define SMALL_LAYER_0_STRIDE (SMALL_LAYER_0_WIDTH * 4) /* = 512 */ uint8_t smallLayer0_Buffer0[256][512]; .pixelFormat = kLCDIFV2_PixelFormatARGB8888, .strideBytes = SMALL_LAYER_0_STRIDE, /* 512, not 3200*/   CTRLDESCL3 should now read 0x200 (512). A 32-bit framebuffer and a 24-pin RGB888 output are independent — you do not need a 3-byte buffer for a 24-pin link. Also these three lines use eLCDIF bit definitions; LCDIFv2 has no RUN bit and this can disturb the control state:   LCDIFV2->CTRL &= ~LCDIF_CTRL_SFTRST_MASK; LCDIFV2->CTRL &= ~LCDIF_CTRL_CLKGATE_MASK; LCDIFV2->CTRL |= LCDIF_CTRL_RUN_MASK;   Gavin_Jia_0-1788249587860.pngGavin_Jia_0-1788249587860.pngGavin_Jia_0-1788249587860.png please drive it only with standard APIs. To confirm your other points: Stride is based on the RAM buffer width, not the screen width — correct. The background color is stable because it is register-generated (no memory fetch); this proves the output path is fine and isolates the fault to the layer fetch path. The color buffer flickering between primary/secondary colors ("like a byte is lost") is exactly underrun dropping bytes; it should disappear once the format is consistent. Bandwidth is not the bottleneck (OCRAM, 128-wide). If underrun still remains after this, lower the pixel clock or increase HBP/HFP to confirm. Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun Well, that doesn't fix it. Actually whether the stride is 128*3 for RGB888 or whether it's 800*4 setup for ARGB8888 and trying to put the entire screen into RAM, the output looks rather similar with distortion off the edge of the screen and I still get underrun errors. I've tried a lot of settings, not only the text in those files! #define SMALL_LAYER_0_HEIGHT 256U #define SMALL_LAYER_0_WIDTH 128U #define SMALL_LAYER_0_BPP 3U /* RGB888 */ #define SMALL_LAYER_0_STRIDE (SMALL_LAYER_0_WIDTH*SMALL_LAYER_0_BPP) /*384*/ ~debug print~ CTRLDESCL3: 0x 180 (Pitch/Stride = 384 bytes) Again, that also doesn't work. But I'm happy that you can confirm that my layer 0 stride setting should be based on the RAM buffer width and not based on the LCD screen width. Right? Since the interface to LT8918 has a 24 pin parallel connection it really should be RGB888. I am concerned sometimes that DMA or something isn't keeping up, but this is running out of SRAM_OC1 with the tiny buffer size. Perhaps even RGB565 would have similar output because the most significant bits could be output correctly on their RGB pins. I might even try something monochrome. I might be making more mistakes as visible in the sample code with the BPP set to 4 instead of 3 for RGB888. Is there any requirement to have the 'background area' in a different layer and buffered in some other memory? I like that the background setting seems to work correctly and the output color there is stable at whatever solid color I set it to. Some experimenting with non-white RAM buffers allow the screen to flicker between primary (RGB) or secondary colors, like an individual byte is lost, perhaps. Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun Hi @davidpspeedtech , Thanks for your interest in NXP MIMXRT series! I reviewed the attachments you provided, and some of the settings may need to be adjusted. CTRLDESCL3: 0x00000C80 (Pitch/Stride = 3200 bytes) #define SMALL_LAYER_0_BPP 3U /* RGB888 */ #define SMALL_LAYER_0_STRIDE (128 * 3) /* = 384 bytes */ uint8_t smallLayer0_Buffer0[256][384]; --> The PITCH you programmed into CTRLDESCL3 (3200 bytes) does not match your actual buffer layout. Your buffer is 128 x 256 in RGB888, so each row is only 128 x 3 = 384 bytes.   With PITCH = 3200, LCDIFv2 advances 3200 bytes per line instead of 384, so after each row it lands far past the valid data. This single mismatch is enough to produce BOTH symptoms you see: the wrong start address per line gives the distorted/skewed image, and fetching ~8x more (and invalid) data per line starves the output FIFO, which is what raises the underrun errors.   Please make the layer descriptor consistent with the buffer: CTRLDESCL3 (PITCH) = 384 (0x180), i.e. SMALL_LAYER_0_STRIDE = 128 * 3.  Buffer base address 64-byte aligned; keep it non-cacheable (your current setting is correct) or clean the D-cache before display. Best regards, Gavin Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun Hi @davidpspeedtech , The descriptor is now self-consistent: CTRLDESCL5=0xD8000260 (BPP=8=RGB888), CTRLDESCL3=0x300=768=256×3. You read it correctly. But the underlying mismatch is still there; it's just masked by the low clock. The color "changes every row, like a byte is lost" is the proof: your memory dump is all 0xFFFFFFFF and Center Pixel reads one pixel as a single 32-bit word — i.e. the content is still 32-bit/pixel while the hardware fetches 3 bytes. White is 0xFF in every byte so it hides it; green drifts per line. Lowering the pixel clock "removes" the underrun, but not because OCRAM is slow (OCRAM is fast, on-chip memory is not the bottleneck). Underrun depends on LCDIFv2's fetch throughput as an AXI master. You dropped the refresh to ~13.5 Hz (18.85 MHz ÷ (1000×1400)), cutting the fetch demand 3–4×, so it stops — but that's below the panel's minimum. To run fast without underrun, these may helps: Switch to ARGB8888 end-to-end: .pixelFormat=ARGB8888 , BPP=4, stride=256×4=1024, buffer at 4 bytes/pixel, and make sure the pixel-writing code writes 32-bit words. Two reasons: (a) it matches your existing 32-bit content → fixes green; (b) the RM notes packed RGB888 issues bursts of length 15 on the bus (less efficient, more underrun-prone), while ARGB8888 is 32-bit aligned with clean length-16 bursts. Verify with a green dump: it should be a clean repeat, not drifting per row. Raise the LCDIFv2 b_clk (clock root) and restore the pixel clock to ≥22 Hz — that's the correct lever for speed, not lowering the clock. LCDIFv2 does not use eDMA, so "raising DMA priority" doesn't apply; the available levers are b_clk, burst length, outstanding requests, and the THRES dynamic-priority threshold. Take the timing from the JD9365DA-H3 panel datasheet — don't guess — and match the LT8918 input timing to it. ~200 horizontal blanking is fine; larger blanking eases underrun but raises htotal (needing a higher pixel clock), so it's a trade-off — the root fix is a higher b_clk. Vsync/vertical porch must match the panel but have little effect on per-line underrun. Best regards, Gavin Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun I'm an NXP novice, so I should've had it set up correctly in the first place, but actually the easy resolution to this mess was to increase the BUS_CLK_ROOT to 200MHz instead of the default 24MHz. I just completely overlooked those default settings. Not only did the small window display nicely after that, also the entire screen changed to OK, also at the full 60Hz display clock (like 80MHz-ish pixel clock). SDRAM settings are more complex of course, but OCRAM and SDRAM were both limited by bus clocks, makes sense. I also adjusted a bunch of other clocks, possibly those were needed. Looking at EVK examples with the clocks peripheral tool also shows they changed these things for those projects. It's hard to notice when looking at 'clock_config.c'. Anyway, thanks a lot!
View full article
IPCF_Example_S32R47_to_A53_M7_0 构建错误 从 IPCF_Example_S32R47_to_A53_M7_0 SDK 导出的默认程序无法构建,导致编译错误。 初步故障排除表明,问题源于时序配置,其中三个时钟输出设置超出了有效范围(如屏幕截图所示)。请问为什么示例程序中仍然存在这个错误,而理论上不应该出现这种情况?请帮忙核实一下。谢谢你! wxh1_1-1788255373531.png S32K1系列的S32SDK Re: IPCF_Example_S32R47_to_A53_M7_0 build error 你好, 对于 S32R47 产品,请联系分配给您的 NXP 直接支持人员。 petervlna_0-1788264837185.png 可能的根本原因可能是 S32CT 版本不匹配。 顺祝商祺! Peter
View full article
Solution/reference design for bidirectional AC/DC + bidirectional isolated DC/DC system Hello We are assessing a bidirectional digital power system and would like to know if reference designs or nxp solutions are available for a setup like this: Concept of the system: AC/DC stage that is bidirectional PFC topology with a totem pole bridgeless Bidirectional operation (grid-tied inverter mode and PFC mode) Isolated DC/DC stage in both directions Topology of Dual Active Bridge (DAB) Power flow in both directions with digital control The system is designed for applications such energy storage systems, bidirectional power converters, or comparable industrial power platforms, and the goal power level is in the multi-kW range. Would you kindly suggest a reference design or solution? We will begin with a 1.2kW inverter for 4s pack(nominal 12.8V). Re: Solution/reference design for bidirectional AC/DC + bidirectional isolated DC/DC system Totem pole is not a strict requirement, I am flexible with the topology. I am okay with this reference: BIDIRECTIONAL-AC-DC-REF-DESIGN Can you also suggest for DC-DC stage, even DAB is not a strict requirement. So if you can suggest a reference for DC-DC stage, it would be very helpful Re: Solution/reference design for bidirectional AC/DC + bidirectional isolated DC/DC system Hello Sahil, NXP has two relevant reference designs for the AC/DC front-end: 800W Bidirectional AC-DC Conversion Solution (BIDIRECTIONAL-AC-DC-REF-DESIGN) — a fully validated, bidirectional AC/DC converter controlled by the MC56F83783 DSC. It supports both AC-to-DC (PFC mode) and DC-to-AC (grid-tied inverter mode) operation with smooth mode transitions. Key specifications: 800W @ 220Vac, wide input range 85–265Vac, 380V DC bus, peak efficiency >97% @ 220Vac, power factor >0.99. Documentation: UG10208, AN14354. Note that this design uses a full-bridge topology with an LCL filter, not a totem-pole; it is the closest available bidirectional AC/DC reference design from NXP. Totem-Pole Bridgeless PFC Converter (RDPFC56F82748) — implements totem-pole bridgeless PFC using the MC56F83783 / MC56F82748 DSC, achieving PF >0.99 and THDi <5%. Documentation: AN12618, DRM174. This specific reference design operates in rectifier (AC-to-DC) mode only and is rated at 240W / 12V output. It is useful as a starting point for totem-pole PFC implementation, but does not include the bidirectional (inverter) control path out of the box. If bidirectional operation with totem-pole topology is required in the same design, combining the PFC control from RDPFC56F82748 with the bidirectional control framework from BIDIRECTIONAL-AC-DC-REF-DESIGN would be the recommended approach. BRs, Tomas
View full article
MCX 947 Ethernet and Camera not working together even after modification Hi, On your reference manual, it is mentioned that we can connect Ethernet and Camera if we solder this wire from P1_4 to  R58 resister.   However, Neither of component seem to work.   embeddedguru_0-1788271676998.pngembeddedguru_0-1788271676998.png Development Board MCXC Re: MCX 947 Ethernet and Camera not working together even after modification Hi, I had already checked that post before asking in this forum. There it has instructed to rewire 4 different camera signals directly into pads. I would like to do minimum rework as possible and hence i refer to your document.    Since you mentioned previous documentation could not be updated, please have it updated in future because it is misleading.   To conclude,  connecting wire from P1_4 to  R58 resister alone does not allow to use ethernet and camera simultaneously as mentioned in the document. Re: MCX 947 Ethernet and Camera not working together even after modification Hello, Certain pins required for the Camera interface are shared with the Ethernet function, so the Camera interface must be reassigned to alternate pins in order to enable both peripherals simultaneously. Let me redirect you to the Community post workaround to implement simultaneous use of Ethernet and Camera on the MCX N947, also includes how to test an example if you are interested; Kindly refer to these instructions as the article provides more complete guidance on this topic and the previous documentation section could not be updated to cover this. MCX N947: Simultaneous Implementation of Ethernet and Camera Functions Best Regards. Re: MCX 947 Ethernet and Camera not working together even after modification Hi, Thank you for bringing this to our attention, Documentation team will check on the changes to apply. For achieving this functionality is through the workaround from the post. While we understand this requires additional rework on your end, this is currently a tested and known method to implement it. Let me know if by implementing the workaround, is still not operating. Best Regards
View full article
RT1172 LT8918 LCD 并行 LCDIFV2 小层 + 背景欠载 很遗憾,我无法直接将 mipi 输出连接到这个 LCD,所以添加了 LT8918,但似乎没有出现任何问题。测试图案可以顺利传输到该设备上,我的调试日志也显示它已同步并通过了基本设置。 但是我的输出结果有问题。我目前的代码是为一个非常简单的小型内存缓冲区(128x256)设计的,位于 800x1280 屏幕的中间。无需查看实际输出屏幕,但画面看起来非常失真。另外,在打印的诊断信息中,我遇到了很多欠载错误,就好像 DMA 获取数据的速度不够快,无法完成整行写入一样。 所以,我对液晶显示器或恩智浦寄存器并不精通。我是不是在某个地方犯了什么低级错误?存在诸多不确定因素。SRAM_OC1 真的速度很慢吗?或许可以通过调整 AXI 或 DMA 设置来获得正确的时序?我在 MPU 代码中将其重新配置为非缓存模式,但这可能也是一个错误。很遗憾,我看不出默认区域和 ncache 区域之间有什么区别。还有很多其他事情需要考虑,比如我尝试将步长更改为整个 800 像素行,而不是较小的 128 图层 0 大小。RGB 像素时钟比 MIPI 字节时钟慢,但我预计 MIPI 无论如何都会快得多,因为它只有 2 条线,而 RGB 有 24 个并行连接。 另外,我之所以只创建这么小的第 0 层区域,是因为 同步动态随机存取存储器(SDRAM) 可能会出现错误。为了摆脱这种不确定性,我把它简化成一个更小的、可控的部分,但即使在这里,我似乎也找不到到底哪里出了问题。 能走到这一步固然令人欣慰,但同时也让人很沮丧,因为我不知道该如何才能取得更大的进步。背景单色显示一切正常,测试图案也能显示形状良好的条形区域,所以我认为这不是真正的“LCD”问题,而是RAM缓冲区读取或LCDIFv2将其输出到并行输出时存在一些时序问题。 我该如何调试这个问题?谢谢。 Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun 我又尝试了一些方法,现在看来输出确实稳定了,没有出现欠载错误,至少根据我打印的诊断信息来看是这样。我认为最主要的变化是第一个变化,其他变化实际上更难一些,但为了清楚起见,我还是列出来吧。这个设置仍然是 RGB888,我还没想改成 alpha 层绘制来尝试,因为它还不是很好。 1. 将像素时钟频率降低很多,刷新率降至接近 15Hz。DMA或许有额外的工作时间?但正如你所说,OCRAM 的速度应该很快。我在 MPU 配置中也将其设置为该空间中的 NCACHE 区域。 2. 使用的颜色只有黑色和白色。尝试使用绿色背景实际上会引入一些背景问题,绿色可能会偏移到 RGB 图案中,导致每一行都发生变化(偏移 1 个字节?)。 3. 将 RAM 层 0 的宽度更改为 256,以匹配高度 256。实际上,高度为 128 也完全可以,只是这个特定的日志高度为 256,你可以看到步幅也变成了 768。 4. 前廊和后廊的视频设置要大得多。我怀疑这不是主要因素,我也尝试过用更快的速度运行这些设置,但效果并不理想。数据表允许 Hfp + Hbp + Hs 的最大值任意大,有什么理由让总和超过 200 吗?垂直设置总共限制为 250 个。 总之,这很有趣!从技术角度来说,LCD 数据手册上说它应该至少以 22Hz 的频率运行,但我没有看到白色部分出现闪烁。我希望它跑得更快。 我完全没有关注RT1172上的DMA,有什么办法可以加快它的运行速度或者提高它的优先级之类的吗?LCDIFv2还有其他相关设置吗?尤其是考虑到 OCRAM 的速度应该非常快,我很惊讶速度降低这么多竟然会产生这样的效果。 Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun 正确的。非常感谢!我们来尝试更多的事情。这是另一条日志。 我还是想坚持使用RGB888。ARGB8888 有什么理由更适合这个用途吗?我或许会找时间试试 alpha 版本。 CTRLDESCL5: 0xD8000260 我查阅了参考手册,BPP 设置位于第 27-24 位,所以“8”表示我已成功将其设置为 RGB888,至少看起来是这样。最后几个字节似乎无关紧要,alpha 设置似乎也无害地关闭了。 屏幕输出看起来不一样,但并不固定。或许有所改进?虽然仍有环绕效果,但没那么夸张了。 我还尝试过提高像素时钟的速度,但不确定这样做是好是坏。 我可以尝试更改更多视频设置吗?我原以为我设置的 25% Hsync 参数已经非常高了,但话说回来,我以前从未这样做过。什么样的场景才算特别好?垂直同步也相关吗?还有一个 LT8918 桥接器也需要获取这些设置输入,不过我也可以处理它。我只能靠猜来填入正确的数字吗? 驱动程序是 JD9365DA-H3,希望这能有所帮助。这是一个带有触摸屏的奇怪设备,但我对此没有任何意见。 Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun 嗨@davidpspeedtech , 谢谢你的更新!但是,问题在于您的某些设置不一致。 0xD9000260 → 硬件锁定的格式为 ARGB8888(32 位/像素)。 因此,当您设置步长 = 384 (=128×3, RGB888) 时,硬件仍然会读取 128×4 = 512 字节/行 → 每行未对齐,读取超出缓冲区,并发生下溢。 你每次都只更改了步长或 BPP 宏,但硬件实际上遵循 .pixelFormat ,它仍然是 ARGB8888——这四个值从来都不一致。 请一次性将它们全部统一设置为 32 位 ARGB8888 或 RGB888:   #define SMALL_LAYER_0_BPP 4U #define SMALL_LAYER_0_STRIDE (SMALL_LAYER_0_WIDTH * 4) /* = 512 */ uint8_t smallLayer0_Buffer0[256][512]; .pixelFormat = kLCDIFV2_PixelFormatARGB8888, .strideBytes = SMALL_LAYER_0_STRIDE, /* 512,而不是 3200 */   CTRLDESCL3 现在应该读取 0x200 (512)。32 位帧缓冲区和 24 针 RGB888 输出是独立的——24 针连接不需要 3 字节缓冲区。 此外,这三行代码使用了 eLCDIF 位定义;LCDIFv2 没有 RUN 位,这可能会干扰控制状态:   LCDIFV2->CTRL &= ~LCDIF_CTRL_SFTRST_MASK; LCDIFV2->CTRL &= ~LCDIF_CTRL_CLKGATE_MASK; LCDIFV2->CTRL |= LCDIF_CTRL_RUN_MASK;   Gavin_Jia_0-1788249587860.pngGavin_Jia_0-1788249587860.pngGavin_Jia_0-1788249587860.png 请仅使用标准 API 进行驱动。 为了证实你提出的其他几点: 步长是基于 RAM 缓冲区宽度,而不是屏幕宽度——正确。 背景颜色稳定,因为它是由寄存器生成的(无需内存读取);这证明输出路径正常,并将故障隔离到层读取路径。 颜色缓冲区在原色/辅助色之间闪烁(“就像丢失了一个字节”),这恰恰是欠载丢字节造成的;一旦格式一致,这种情况应该就会消失。 带宽不是瓶颈(OCRAM,128 宽)。如果在此之后仍然存在欠载现象,请降低像素时钟频率或增加 HBP/HFP 以确认。 Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun 但这并不能解决问题。实际上,无论是 RGB888 的步长为 128*3,还是 ARGB8888 的步长为 800*4 并尝试将整个屏幕放入 RAM 中,输出看起来都非常相似,屏幕边缘都会出现失真,而且我仍然会遇到欠载错误。我尝试了很多设置,不仅仅是那些文件中的文本! #define SMALL_LAYER_0_HEIGHT 256U #define SMALL_LAYER_0_WIDTH 128U #define SMALL_LAYER_0_BPP 3U /* RGB888 */ #define SMALL_LAYER_0_STRIDE (SMALL_LAYER_0_WIDTH*SMALL_LAYER_0_BPP) /*384*/ ~调试打印~ CTRLDESCL3: 0x 180 (引脚间距/步长 = 384 字节) 这样做也不行。 但我很高兴你能确认我的第 0 层步长设置应该基于 RAM 缓冲区宽度,而不是基于 LCD 屏幕宽度。正确的? 由于 LT8918 的接口是 24 针并联连接,所以它实际上应该是 RGB888。我有时担心 DMA 或其他什么功能跟不上,但由于缓冲区大小太小,SRAM_OC1 已经用完了。或许 RGB565 也能有类似的输出,因为其 RGB 引脚可以正确输出最高有效位。我甚至可能会尝试单色系的作品。 我可能犯了更多错误,如示例代码所示,RGB888 的 BPP 设置为 4 而不是 3。 是否必须将“背景区域”放在不同的层中,并缓冲到其他内存中?我喜欢它的背景设置似乎工作正常,无论我将其设置为哪种纯色,输出颜色都能保持稳定。对非白色 RAM 缓冲区进行一些实验,可以让屏幕在原色(RGB)或二次色之间闪烁,就像丢失了一个字节一样。 Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun 嗨@davidpspeedtech , 感谢您对 NXP MIMXRT 系列产品的关注! 我已查看您提供的附件,其中一些设置可能需要调整。 CTRLDESCL3: 0x00000C80(音高/步幅 = 3200 字节) #define SMALL_LAYER_0_BPP 3U /* RGB888 */ #define SMALL_LAYER_0_STRIDE (128 * 3) /* = 384 字节 */ uint8_t smallLayer0_Buffer0[256][384]; -->您编程到 CTRLDESCL3 中的 PITCH 值(3200 字节)与您的实际缓冲区布局不匹配。您的缓冲区在 RGB888 模式下为 128 x 256,因此每行只有 128 x 3 = 384 字节。   当 PITCH = 3200 时,LCDIFv2 每行推进 3200 字节而不是 384 字节,因此每行结束后都会远远超出有效数据。仅仅这一个不匹配就足以产生你看到的两种症状:每行错误的起始地址导致图像失真/倾斜,而每行获取大约 8 倍的(无效的)数据会使输出 FIFO 容量不足,从而引发下溢错误。   请使层描述符与缓冲区保持一致: CTRLDESCL3 (引脚间距) = 384 (0x180),即SMALL_LAYER_0_STRIDE = 128 * 3。 缓冲区基地址 64 字节对齐;保持不可缓存(您当前的设置是正确的),或者在显示之前清除 数据缓存。 此致, 加文 Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun 嗨@davidpspeedtech , 描述符现在是自洽的:CTRLDESCL5=0xD8000260(BPP=8=RGB888),CTRLDESCL3=0x300=768=256×3。你没看错。 但根本的不匹配仍然存在;只是被低时钟频率掩盖了。颜色“每行都改变,就像丢失了一个字节”就是证据:你的内存转储全是 0xFFFFFFFF ,而 Center Pixel 将一个像素读取为一个 32 位字——也就是说,内容仍然是 32 位/像素,而硬件获取了 3 个字节。白色在每个字节中都是 0xFF,因此会被隐藏;绿色会逐行漂移。 降低像素时钟“消除”欠载,但这并不是因为 OCRAM 速度慢(OCRAM 速度很快,片上内存不是瓶颈)。欠载取决于 LCDIFv2 作为 AXI 主设备的读取吞吐量。你将刷新率降低到 ~13.5 Hz (18.85 MHz ÷ (1000×1400)),使读取需求减少了 3-4 倍,因此停止了——但这低于面板的最低要求。 为了快速运行而不至于半倒,以下方法可能有所帮助: 切换到 ARGB8888 端到端: .pixelFormat=ARGB8888 ,BPP=4,步长=256×4=1024,缓冲区大小为 4 字节/像素,并确保像素写入代码写入 32 位字。两个原因:(a)它与您现有的 32 位内容匹配 → 修复绿色;(b)RM 指出打包的 RGB888 在总线上发出长度为 15 的突发信号(效率较低,更容易出现欠载),而 ARGB8888 是 32 位对齐的,具有干净的长度为 16 的突发信号。使用绿色转储进行验证:应该是一个干净的重复,而不是逐行漂移。 提高 LCDIFv2 b_clk(时钟根),将像素时钟恢复到 ≥22 Hz——这是提高速度的正确方法,而不是降低时钟频率。LCDIFv2 不使用 eDMA,因此“提高 DMA 优先级”不适用;可用的控制手段有 b_clk、突发长度、未完成的请求和 THRES 动态优先级阈值。 从 JD9365DA-H3 面板数据手册中获取时序——不要猜测——并将 LT8918 输入时序与之匹配。~200 水平消隐是可以接受的;更大的消隐可以缓解欠载,但会增加 htotal(需要更高的像素时钟),所以这是一个权衡——根本的解决方法是更高的 b_clk。垂直同步/垂直门廊必须与面板匹配,但对每行欠载影响很小。 此致, 加文 Re: RT1172 LT8918 LCD parallel LCDIFV2 small layer + background underrun 我是 NXP 的新手,所以一开始就应该正确设置,但实际上解决这个问题的简单方法是将 BUS_CLK_ROOT 增加到 200MHz,而不是默认的 24MHz。我完全忽略了这些默认设置。 之后不仅小窗口显示正常,整个屏幕也恢复正常,而且显示频率也达到了 60Hz(像素时钟频率约为 80MHz)。SDRAM 的设置当然更复杂,但 OCRAM 和 SDRAM 都受到总线时钟的限制,这很合理。 我还调整了其他一些时钟,或许这些调整是必要的。查看 EVK 示例以及时钟外设工具,也会发现他们为这些项目更改了这些内容。查看“clock_config.c”时很难注意到这一点。 总之,非常感谢!
View full article
在 KW45B41Z-EVK 上使用 eIQ TSS 和移植的 TFLM 中间件实现 AI/ML NXP社区的各位好, 我正在开发一款适用于KW45B41Z-EVK (Cortex-M33) 的边缘 AI 应用,希望就如何在该板上部署机器学习模型获得一些建议。 由于 KW45 SDK 默认不包含 eIQ/TFLM 中间件,我的计划是: 模型训练:使用eIQ Time Series Studio (eIQ TSS)训练一个用于时间序列数据的 n 类分类模型。由于 eIQ TSS 中未列出 KW45 作为目标平台,因此我选择FRDM-MCXN947 (Cortex-M33) 作为导出模型的目标平台。 运行时部署:将FRDM-MCXN947 SDK中的 中间件/eiq/tensorflow-lite 文件夹移植到我的 KW45 SDK 项目中,并将其与 CMSIS-NN 链接。 我的问题: 将 eIQ TFLM 中间件从 MCXN947 SDK 移植到 KW45 SDK 是否是一种有效且受支持的方法? 在 eIQ TSS 中选择 FRDM-MCXN947 是否适合生成在 KW45 上运行的模型? 在 KW45B41Z-EVK 上实现 AI/ML 是否有其他推荐的或原生工作流程? 感谢您的帮助! Kinetis W系列MCU Re: Implementing AI/ML on KW45B41Z-EVK using eIQ TSS and Ported TFLM Middleware 您好,NXP支持团队和社区, 我写这封信是为了跟进这个询问,因为找到解决方案对我目前的项目时间表来说非常紧迫。 NXP 团队的某位成员能否快速确认一下,将 eIQ/TFLM 中间件从 FRDM-MCXN947 SDK 移植到 KW45 SDK 是否是一种有效且受支持的解决方法?任何关于推荐工作流程的简要指导或确认都将对我非常有帮助,以便我能自信地继续进行开发工作。 感谢您抽出时间提供帮助! KW45B41Z-EVK EIQ-工具包EIQ-TFLITE-MICRO #AI/ML Re: Implementing AI/ML on KW45B41Z-EVK using eIQ TSS and Ported TFLM Middleware 你好@Srushti_Mulimani ,希望你一切都好。   如果您使用的是 eIQ Time Series Studio (TSS),我建议您将项目从 FRDM-MCXW71 移植过来。它是 eIQ TSS 官方支持的目标,并且在软件上与 KW45 兼容。这两个设备都采用相同的 Cortex-M33 内核架构和类似的内存配置,因此生成的库应该与您的硬件更加匹配。 当使用硬件配置差异很大的设备(例如 FRDM-MCXN947)作为移植目标时,可能会生成不兼容的模型,例如,由于两个设备之间的可用 RAM 存在差异,或者生成了专门针对 MCXN947 的 NPU 加速模型。 希望这能帮到你! 此致, 索菲亚。
View full article
S32G399A IIC 配置 您好, 我打算使用S32G399的I2C4来配置外部PMIC。我想请问一下,这个I2C4模块是否可以通过A核进行底层软件配置(比如:时钟频率,上下拉电阻,地址等)?我们暂时不会用到M核。所以想通过A核进行S32G的IO的底层配置。 MichaelTao_0-1788251860175.pngMichaelTao_0-1788251860175.png Re: S32G399A IIC 配置 Hello, @MichaelTao  您好,是可以的,A核可以配置I2C4这个模块 BR Chenyin Re: S32G399A IIC 配置 您可以尝试使用 S32 设计工作室进行 I2C 底层驱动程序配置。
View full article
MPC5777C-DEVB2 的文档? 你好, 我的团队多年来一直成功地使用 MPC5777CEVB,无论是在 S32 还是 GHS 环境中,但是我们不得不购买一些新板,而当时只有 -DEVB2 可用。我们找不到相关的文档,虽然该板在 S32(以及 pemicro Multilink 探针)下工作正常,但在 GHS 下使用与 EVB 相同的 V4 探针时遇到了问题。看来我们在执行 JTAG 连接时遇到了问题,因为从一开始我们就无法读取/写入寄存器(因此,我们无法停止或 RESET 设备)。 在 GHS 下启用 JTAG 调试是否需要进行任何特定的跳线/开关配置?我们找不到DEVB2的任何使用手册,因此我们不知道从哪里开始调查。 谢谢! 里卡多 Re: Documentation for the MPC5777C-DEVB2? 你好, 我看到有 SW18 跳线用于 JTAG / OpenSDA 连接。 petervlna_0-1788336667191.png 这意味着SW18决定这些JTAG信号是否连接到: 板载/OpenSDA调试器路径,或 外部MCU JTAG连接器。 顺祝商祺! Peter
View full article
[Lin Master] [linstack_config]middleware - BaudRate=10417 bps LINバスの顧客は、10417bpsのボーレートを必要とします。 LDF Explorerは10417bpsのボーレートにも対応しています。 CY9_0-1788234587344.png しかし、S32DSに戻ると、LPUART2はこのボーレートをサポートしていません。 CY9_1-1788234668862.png 現在、機器は通信できません。これがLPUARTのボーレート設定によるものかどうかは不明です。 どなたか確認していただけませんか? ありがとう S32K144 EVB + S32DSv3.5+RTM401 S32DS-S32PLATFORM S32SDK-ARMK1 #LIN_BUS #LIN_Master #Lin_Master S32K1用S32 SDK Re: [Lin Master] [linstack_config]middleware - BaudRate=10417 bps RTD 3.0.0へのアップグレードを検討してもいいかもしれません。これはLINボー率においてより柔軟であり、以下を参照してください。 ご使用中のレガシーSDK4.0.1は現在サポートされていませんし、新しいデザインには推奨されていません。 danielmartynek_0-1788261761281.png よろしくお願いいたします。 ダニエル Re: [Lin Master] [linstack_config]middleware - BaudRate=10417 bps しかし、お客様は 奇妙 なボーレートを使いたいと頼みます... そして[LDFエクスプローラー]もこの奇妙なボードレートをサポートしています... このCASEでは問題ないとサポートし、お客様にはすでにこのCASEを手に入れると約束します。 SO, 今私は何ができるのでしょうか? 何かご意見はありますか? ご意見・ご感想、または噂話など、何でもお寄せください。 Re: [Lin Master] [linstack_config]middleware - BaudRate=10417 bps こんにちは、 @CY9 さん。 残念ながら、ドライバーは以下の固定ボーレートのみをサポートしています: danielmartynek_0-1788252200254.png よろしくお願いいたします。 ダニエル
View full article
双方向AC/DC + 双方向絶縁DC/DCシステムのソリューション/リファレンス・デザイン Hello 私たちは双方向デジタル電力システムを評価しており、このようなセットアップに適したリファレンスデザインやnxpソリューションが利用可能かどうかを知りたいです。 システムの概念: 双方向AC/DCステージ トーテムポールブリッジレスのPFCトポロジー 双方向運転(系統連系インバータモードとPFCモード) 両方向とも絶縁型DC/DCコンバータ段 デュアルアクティブブリッジ(DAB)のトポロジー デジタル制御による双方向の電力の流れ このシステムは、エネルギー貯蔵システム、双方向電力コンバータ、または同等のインダストリアル電力プラットフォームなどのアプリケーション向けに設計されており、目標電力レベルは数kWの範囲です。 リファレンス・デザインや解決策を提案していただけませんか? まず、4セルパック(公称12.8V)用の1.2kWインバーターから始めます。 Re: Solution/reference design for bidirectional AC/DC + bidirectional isolated DC/DC system トーテムポールは必須条件ではありません。形状については柔軟に対応します。このリファレンスは問題ありません:BIDIRECTIONAL-AC-DC-REF-DESIGN DC-DCステージについてもおすすめできますか?DABも厳密な必須ではありません。ですので、DC-DCステージの参考文献をご存知いただけるととても助かります Re: Solution/reference design for bidirectional AC/DC + bidirectional isolated DC/DC system こんにちは、サヒルさん。 NXPにはAC/DCフロントエンド用の2つの関連するリファレンスデザインがあります: 800W双方向AC-DC変換ソリューション(BIDIRECTIONAL-AC-DC-REF-DESIGN)— MC56F83783 DSCによって制御される、完全に検証された双方向AC/DCコンバーターです。交流から直流(PFCモード)および直流から交流(グリッドタイインバータモード)の両方の動作をサポートし、スムーズなモード移行が可能です。主な仕様:800W @ 220Vac、広い入力範囲 85~265Vac、380V DCバス、ピーク効率 > 97% @ 220Vac、力率 > 0.99。ドキュメント:UG10208、AN14354。このデザインはトーテムポールではなく、LCLフィルターを用いたフルブリッジトポロジーを使用していることに注意してください。NXPによる最も近い双方向AC/DCリファレンス・デザインです。 トーテムポールブリッジレスPFCコンバーター(RDPFC56F82748) — MC56F83783/MC56F82748 DSCを用いてトーテムポールブリッジレスPFCを実装し、PF >0.99およびTHDi <5%を実現。ドキュメント:AN12618、DRM174。この特定のリファレンス・デザインは整流器(AC-DC)モードでのみ動作し、出力は240W / 12Vです。これはトーテムポール型PFCの実装の出発点として有用ですが、双方向(インバータ)制御パスは標準では含まれていません。 同じ設計でトーテムポールトポロジーを用いた双方向運転が必要な場合は、RDPFC56F82748のPFC制御とBIDIRECTIONAL-AC-DC-REF-DESIGNの双方向制御フレームワークを組み合わせることが推奨されます。 BRs、トーマス
View full article
ソフトウェアライセンスの有効期限が切れました こんにちは: アクティベーションID: 04E9-8F5A-8B1F-F9C8 免許証の有効期間を延長するには、どのような手続きが必要ですか? アクティベーションID: 04E9-8F5A-8B1F-F9C8 免許証の有効期間を延長するには、どのような手続きが必要ですか? Re: 软件许可证过期 こんにちは、 お客様のS32DSライセンスが延長されました。以前のコードを使用して、S32DSを再度有効化してください。
View full article
MCX 947のイーサネットとカメラが改造しても動作しない こんにちは、 参考マニュアルには、この線をP1_4からR58リシスターにはんだ付けすればイーサネットとカメラを接続できると書かれています。しかし、どちらの部品も正常に動作しないようです。 embeddedguru_0-1788271676998.pngembeddedguru_0-1788271676998.png 開発ボード MCX C Re: MCX 947 Ethernet and Camera not working together even after modification こんにちは、 このフォーラムで質問する前に、既にその投稿を確認していました。そこでは、4つの異なるカメラ信号を直接パッドに配線し直すように指示されている。できる限り手戻りを最小限に抑えたい そのため、私はあなたの文書を参照します。以前のドキュメントは更新できないとおっしゃっていましたが、今後は誤解を招く内容なので更新してください。結論として、P1_4からR58抵抗への配線単独では、文書に記載されているようにイーサネットとカメラの両方を同時に使用することはできません。 Re: MCX 947 Ethernet and Camera not working together even after modification こんにちは、 カメラインターフェースに必要な特定のピンはイーサネット機能と共有されるため、両方のペリフェラルを同時に有効化するためにはカメラインターフェースを交互のピンに再割り当てする必要があります。 MCX N947でイーサネットとカメラを同時に使うためのコミュニティの回避策へご案内します。興味があれば、テスト例も含まれています。 この記事はこのトピックについてより詳しいガイダンスを提供しており、前のドキュメントセクションでは更新できなかったため、これらの指示をご参照ください。 MCX N947:Ethernetとカメラ機能の同時実装 よろしくお願いいたします。 Re: MCX 947 Ethernet and Camera not working together even after modification こんにちは、 ご指摘いただきありがとうございます。ドキュメントチームが変更点を確認して申請します。 この機能を実現するには、投稿で紹介されている回避策を用いる必要があります。これはあなたの側で追加の再設計が必要であることは理解していますが、これは現在テスト済みで既知の実装方法です。 回避策を実施してもまだ動作しない場合は、お知らせください。 よろしくお願いいたします。
View full article
软件许可证过期 你好: ActivationId:04E9-8F5A-8B1F-F9C8 延长许可证有效期需要哪些手续 ActivationId: 04E9-8F5A-8B1F-F9C8 What procedures are required to extend the license validity period? Re: 软件许可证过期 您好, 您的S32DS许可证已延期。请使用您之前的激活码重新激活S32DS。
View full article
[Lin Master] [linstack_config]middleware - BaudRate=10417 bps The LIN Bus customer requires a baud rate of 10417 bps. LDF Explorer also supports a 10417 baud rate. CY9_0-1788234587344.png However, returning to S32DS, LPUART2 does not support this baudrate. CY9_1-1788234668862.png The equipment is currently unable to communicate; it's unclear whether this is caused by the LPUART baud rate setting. Can someone help confirm this? thank S32K144 EVB + S32DSv3.5+RTM401 S32DS-S32PLATFORM S32SDK-ARMK1 #LIN_BUS #LIN_Master #Lin_Master S32 SDK for S32K1 Re: [Lin Master] [linstack_config]middleware - BaudRate=10417 bps You could consider upgrading to RTD 3.0.0, which is more flexible in the LIN Baud rate, see below. Please note that the legacy SDK 4.0.1 that you use is no longer supported and is not recommended for new designs. danielmartynek_0-1788261761281.png Regards, Daniel Re: [Lin Master] [linstack_config]middleware - BaudRate=10417 bps But my customer ask to use the strange baudrate ...  And [LDF explorer] support this strange baudrate too...  I support it's ok for this case, and promise the customer on go this case already .  So, What can I do now ?  Any comments?  Thanks for any comments ... or gossip  Re: [Lin Master] [linstack_config]middleware - BaudRate=10417 bps Hello @CY9, Unfortunately, the driver supports these fixed baud rates only: danielmartynek_0-1788252200254.png Regards, Daniel
View full article
MPC5777C-DEVB2のドキュメントはありますか? こんにちは、 私のチームは数年間、S32とGHS環境の両方でMPC5777CEVBをうまく扱ってきましたが、新しいボードを購入しなければならず、入手可能なのは-DEVB2だけでした。ドキュメントは見つからず、ボードはS32(およびPemicroのMultilinkプローブ)では問題なく動作していますが、GHSやEVBで動作する同じV4プローブでは問題が発生しています。JTAG接続の実行に問題が発生しているようで、最初からレジスタの読み書きができず(つまりデバイスの停止やリセットができません)。 GHSでJTAGデバッグを有効にするために、特定のジャンパーやスイッチの設定は必要ですか?DEVB2のマニュアルが見つからないため、どこから調査を始めればよいのか分かりません。 ありがとうございます リカルド Re: Documentation for the MPC5777C-DEVB2? こんにちは、 JTAG/OpenSDA接続用のSW18ジャンパーがあるようですね。 petervlna_0-1788336667191.png つまり、SW18はこれらのJTAG信号が以下に接続されているかどうかを判断します。 オンボード/OpenSDAデバッガーパス、または 外部MCU JTAGコネクタです。 よろしくお願いいたします。 ピーター
View full article