Multi Source Translation Content

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

Multi Source Translation Content

讨论

排序依据:
i.MXRT1052和FPGA通讯用SRAM AADM模式,有些信号没有输出 i.MXRT1052和FPGA通讯用SRAM AADM模式,有些信号没有输出。 我现在用的AADM模式。但是在实际配置的时候没有看到WE#,OE#。还是配置的SEMC_ADDR11/SEMC_ADDR12。现在这两个信号在FPGA端没有变化。但是数据和地址是有变化的,ADV#也是有变化的。SEMC_CS0没有变化。 这是为什么?我看到手册上的SEMC Pin Mux。SEMC_ADDR11是WE#,SEMC_ADDR12是OE#,但是在MCUXpresso Config Tools 26.06里面配置的时候没有OE#和WE#。 还是其他什么原因导致没有信号。 Re: i.MXRT1052和FPGA通讯用SRAM AADM模式,有些信号没有输出 Hi @SDFDSFSF ,    请注意,不要用SEMC_CS0做FPGA SRAM的片选。SEMC_CS0是SDRAM CS0, SRAM应该使用SEMC_CSX[3:0], 并在SEMC->IOCR里把对应的MUX_CSXx配置成SRAM CE#。      另外,确认外设初始化后,寄存器SRAMCR0.AM= 01 (AADM)。当SRAM工作在AADM模式下,SEMC会自动将SEMC_ADDR11定义为WE#,SEMC_ADDR12定义为OE#。 Best Regards, Shelly
查看全文
Himiway: Mid-Drive vs Hub Motor: Pros and Cons If you're shopping for an electric bike, one of the biggest decisions is choosing between a mid-drive motor and a hub motor. Neither design is automatically better. Mid-drive motors are especially good at using the bike's gears to handle steep hills and technical terrain, while hub motors are simpler, usually more affordable, and require less drivetrain maintenance. For many everyday riders, a good hub motor provides more than enough performance. Riders dealing with serious hills, mountain trails, or demanding cargo use may benefit more from a mid-drive system. Here's a practical comparison. Mid-Drive vs Hub Motor at a Glance Feature Mid-Drive Motor Hub Motor Motor Location Around the crank/pedals Front or rear wheel hub Best For Hills, trails, technical riding Commuting, leisure, mixed everyday riding Hill Performance Excellent Good to excellent depending on torque Weight Distribution Very balanced More weight at one wheel Drivetrain Wear Higher Lower Maintenance More involved Generally simpler Flat Tire Repair Usually easier Motor-wheel removal can be harder Pedaling Feel Often very natural Depends heavily on sensor tuning Price Usually higher Usually more affordable What Is a Mid-Drive Motor? A mid-drive motor is positioned near the bottom bracket, where the pedals and crankset meet the frame. Instead of directly turning a wheel, the motor sends power through the bicycle's drivetrain. That means the motor can take advantage of the bike's gears in much the same way the rider does. Shift into a lower gear for a steep climb, for example, and the motor can operate at a more favorable speed while producing strong climbing assistance. This is the biggest reason mid-drive systems are popular on performance-oriented electric mountain bikes and other bikes designed for demanding terrain. Pros of Mid-Drive Motors 1. Excellent Hill-Climbing Performance This is probably the strongest argument for a mid-drive. Because motor power passes through the bicycle's gears, you can select a lower gear when climbing. This helps the motor operate efficiently instead of forcing it to pull the bike uphill at very low motor RPM. For riders living in extremely hilly areas, this can make a noticeable difference. However, don't assume that every mid-drive automatically climbs better than every hub motor. Motor torque, controller tuning, rider weight, gearing, tire size, and total bike weight all matter. A strong 750W geared hub motor with high torque can still be an excellent hill climber for normal roads and moderate trails. 2. Better Weight Distribution A mid-drive motor places its weight low and near the center of the bicycle. That generally gives the bike more neutral handling because there isn't a large motor concentrated inside the front or rear wheel. The advantage becomes especially noticeable during technical mountain biking, quick direction changes, and riding over uneven terrain. 3. Efficient Use of Motor Power Because the motor can use the bicycle's gears, a mid-drive system can keep the motor operating in a more efficient RPM range. This can improve efficiency on routes involving frequent elevation changes. It doesn't necessarily mean a mid-drive will always have longer range, though. Battery capacity, speed, tire pressure, rider weight, temperature, elevation, wind, and assist level can easily have a larger effect on real-world range. 4. Natural Pedaling Experience Many higher-end mid-drive systems are paired with torque sensors. A torque sensor measures how hard you're pushing on the pedals and adjusts motor assistance accordingly. Push harder and you receive more assistance. Pedal gently and the motor responds more gently. The result can feel surprisingly similar to riding a normal bicycle—except that you suddenly have much stronger legs. Cons of Mid-Drive Motors 1. More Drivetrain Wear The same feature that gives a mid-drive its climbing advantage also creates one of its biggest disadvantages. Both the rider and motor are sending power through components such as the: Chain Chainring Cassette Derailleur system High motor torque combined with poor shifting habits can accelerate drivetrain wear. If you regularly shift gears while the motor is delivering maximum power, chains and cassette teeth may wear substantially faster. 2. More Expensive Mid-drive systems generally cost more. The motor must be integrated around the crank area, and the frame often needs to be designed specifically around that drive unit. For riders who mainly travel on pavement or relatively gentle terrain, paying the premium may not provide enough practical benefit. 3. Shifting Technique Matters Mid-drive riders need to think more carefully about gears. Starting a steep hill in a very high gear and then shifting under heavy motor load isn't ideal. Good riding technique involves selecting an appropriate gear before the drivetrain becomes heavily loaded. For experienced cyclists, this quickly becomes natural. For beginners, there can be a learning curve. 4. A Broken Chain Can Become a Bigger Problem Because a mid-drive transfers motor power through the chain, drivetrain failure can potentially leave you unable to use the motor to drive the rear wheel. A throttle-equipped hub-drive bike can have an advantage here because its motor operates independently from the bicycle chain. What Is a Hub Motor? A hub motor is built directly into the center of the front or rear wheel. Rear hub motors are particularly common on modern electric bikes. Instead of sending power through the chain and cassette, the motor directly rotates the wheel. This makes the system mechanically straightforward and separates motor power from the traditional bicycle drivetrain. Several Himiway models use powerful hub-drive configurations. Bikes such as the Himiway D5 2.0 Series demonstrate why hub motors remain popular on practical fat-tire e-bikes: they can combine substantial torque with relatively straightforward operation. Pros of Hub Motors 1. Simple and Low-Maintenance Design One of the biggest advantages is simplicity. The motor doesn't normally send its power through the bicycle chain or cassette. Your drivetrain therefore only has to handle your pedaling force rather than your pedaling force plus motor output. For riders who want an e-bike for commuting, weekend rides, errands, or recreation, this simplicity is valuable. 2. Strong Everyday Performance It's outdated to think that hub motors are only suitable for flat roads. Modern geared hub motors can produce substantial torque. For example, the Himiway D5 2.0 uses a 750W geared hub motor rated at 90 Nm of torque. That's the kind of specification designed to provide strong acceleration and useful climbing assistance rather than simply cruising along perfectly flat bike paths. The D5 2.0 20" combines the same general idea with 20-inch fat tires and full suspension, giving riders a compact platform designed around comfort and maneuverability. For normal hills, neighborhood streets, gravel roads, and recreational trails, a well-designed hub motor can be more than capable. 3. Lower Purchase Cost Hub motors are generally less complicated and less expensive for manufacturers to integrate into an e-bike. That can allow more of the bike's budget to go toward other features such as: Larger batteries Hydraulic brakes Better suspension Integrated lighting Fat tires Higher payload capacity This is one reason hub-drive bikes can offer very attractive specifications for the money. 4. Less Stress on the Chain and Cassette Since motor power goes directly to the wheel, the chain doesn't have to transmit the motor's full torque. That can mean longer drivetrain component life compared with a powerful mid-drive bike, assuming both bikes are maintained properly. 5. Throttle Operation Can Be Useful On compatible hub-drive e-bikes equipped with a throttle, motor operation doesn't necessarily depend on the bicycle drivetrain. This can be convenient when starting from a stop, briefly moving through an intersection, or getting the bike moving when carrying a load. It also provides an important mechanical advantage: a broken chain doesn't necessarily prevent the motor from moving the bicycle. Cons of Hub Motors 1. Less Efficient on Extreme Climbs A conventional hub motor can't take advantage of the bicycle's cassette in the same way a mid-drive can. On a long and very steep climb, the motor may be forced to operate at low speed under heavy load. That can increase heat generation and energy consumption. For occasional hills this might not matter much. For riders climbing steep mountain roads every day, it becomes much more important. 2. Heavier Rear or Front Wheel The motor adds substantial mass to whichever wheel contains it. Most powerful e-bikes use rear hub motors, so the rear of the bicycle can feel heavier when lifting or servicing it. You may notice this more when carrying the bike upstairs than when actually riding it. 3. Flat Tire Repairs Can Be More Complicated A hub-motor wheel isn't quite as easy to remove as an ordinary bicycle wheel. You may need to disconnect the motor cable and deal with a significantly heavier wheel. For that reason, maintaining correct tire pressure and using puncture-resistant tires can be particularly worthwhile on hub-drive e-bikes. What About Himiway eBikes? Himiway ebikes is a useful example because many of its bikes emphasize powerful hub-drive systems rather than automatically using a mid-drive simply because it sounds more premium. Models such as the Himiway D5, D5 Pro, D5 2.0, D5 2.0 ST, D5 2.0 Camo, D5 2.0 20", C3, A7, A7 Pro, D7, and D7 Pro target different types of riding, so the important point is to look at the complete bike rather than judging it solely by motor location. For example, a rider considering a D5 2.0 may care about strong torque, fat-tire traction, suspension comfort, range, and everyday reliability more than achieving the lightest possible drivetrain. The D5 2.0 20" is particularly interesting for riders who value easier maneuverability and comfort. Its smaller 20-inch wheels, 4-inch tires, full suspension, and low center of gravity create a very different riding experience from a traditional large-wheel mountain e-bike. The A7 and A7 Pro, meanwhile, are more relevant to riders prioritizing urban transportation and everyday usability. And the C1 Kids belongs in a completely different category. For younger riders, controllability, appropriate sizing, speed management, braking, and adult supervision are far more important than chasing maximum motor torque. This highlights an important lesson: Don't choose an e-bike based on the motor alone. What Riders Actually Notice Specifications are useful, but everyday riding tends to make the differences much simpler. A well-tuned hub-drive bike often feels effortless during normal commuting. You pedal, assistance arrives, and you keep moving without constantly thinking about gears. A good mid-drive tends to reward riders who actively use their gears. When approaching a hill, shifting down allows the motor and rider to work together efficiently. On technical terrain, the centered weight can also make the bicycle feel more balanced. The difference becomes much less dramatic when you're cruising at moderate speeds on a flat bike path. That's why paying substantially more for a mid-drive isn't automatically worthwhile for every rider. Which Motor Is Better for Hills? Mid-drive wins for serious climbing. If your normal rides include long, steep mountain climbs, a mid-drive's ability to use the bike's gearing is a major advantage. But there's an important distinction between "hills" and "extreme hills." Most people aren't climbing mountain passes every morning. A high-torque geared hub motor can handle typical neighborhood hills, rolling countryside, gravel roads, and moderate trail climbs very well. That's why bikes such as the Himiway D5 2.0 can make sense for riders who want climbing ability without moving to a more expensive mid-drive platform. Which Is Better for Commuting? For typical commuting, I'd give the advantage to the hub motor. It's simple, relatively inexpensive, puts less motor-related stress on the bicycle drivetrain, and provides plenty of assistance for normal urban riding. If your commute involves extremely steep terrain, however, a mid-drive becomes more attractive. Which Is Better for Mountain Biking? For serious technical mountain biking, I'd choose a mid-drive. The centered motor position improves weight distribution, while access to the bike's gearing helps during steep and technical climbs. For gravel roads, forest paths, dirt roads, camping trips, and relatively moderate recreational trails, a powerful fat-tire hub-drive bike can still be an excellent choice. Which Is Better for Beginners? For many beginners, a hub-drive e-bike makes more sense. There's less need to think about keeping the motor in the correct gear, drivetrain maintenance is straightforward, and prices are often more approachable. However, motor type isn't the only factor affecting ease of use. Frame geometry, wheel size, bike weight, standover height, throttle behavior, torque or cadence sensing, brakes, and suspension can make an even bigger difference to rider confidence. Mid-Drive vs Hub Motor: Final Verdict There isn't a universal winner. Choose a mid-drive motor if you: Regularly climb very steep hills Ride technical mountain trails Want balanced weight distribution Prefer a natural, performance-oriented riding feel Don't mind additional drivetrain maintenance Are comfortable paying more Choose a hub motor if you: Commute or ride recreationally Mostly encounter flat to moderately hilly terrain Want lower maintenance Want better value for your budget Prefer a mechanically simpler system Want motor operation independent of the bicycle drivetrain For many everyday riders, a quality geared hub motor offers the better balance of power, simplicity, reliability, and price. A properly designed 750W, high-torque hub-drive e-bike can handle far more than just flat city streets. Mid-drives become particularly valuable when terrain gets genuinely demanding. So instead of asking, "Which motor is better?", ask: "Where will I actually ride this bike?" If the answer is steep mountain trails and demanding climbs, look closely at mid-drives. If it's commuting, weekend rides, gravel roads, errands, and moderate hills, a good hub-drive e-bike—such as several models in Himiway's lineup—may give you everything you need without paying for complexity you won't use.
查看全文
BDM driver cw v6.3 my P&E USB multilink Universal Interface MC908JB8 chip needs a BDM driver to download my code to my MCS08QG8 chip. Otherwise I need a P&E USB multilink Universal board to load my MC9S08QG8 chip. And the board runs about $200. I would prefer to get a BDM driver for my Lenovo USB port. U say the BDM driver is in the CW v6.3 dvelopment software code! I loaded the CW v6.3 code but it will not install, because the "OS is wrong". the orginal OS was for my xp computer, but i am running windows 11 now and the cw v6.3 will not install on that OS. HELPPPPPPPPP!!!!!!!!! Re: BDM driver cw v6.3 你好,   CodeWarrior v6.3 与 Windows 11 不兼容;要在 Windows 11 中使用 CodeWarrior,请更新到 v11.1,这就是您无法在 Windows 11 中安装 CW v6.3 的原因。   能否分享一下您的 P&E USB Multilink 连接在设备管理器 > Jungo Connectivity 中显示的内容? 它在其他地方出现过吗?或者有警告标志吗? 例如,我的 P&E USB 多链路设置如下:   在USB Multilink Universal 和 USB Multilink Universal FX 技术概要 [USBMLUNIVERSALFX]文档的第 6 章“驱动程序安装”中提到,如果需要更新驱动程序,可以从 P&E 页面“支持中心”>“下载”下载驱动程序安装程序的副本。   顺祝商祺!
查看全文
MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Hi Team, I am working with the MIMXRT1040-EVK and using MCUXpresso IDE with LinkServer/SWD. I am facing an issue where my application works correctly when linked and executed from RAM, but when configured to execute from external FlexSPI NOR Flash, the debugger does not reach main(). Current behavior RAM build: "Link application to RAM" enabled Application downloads successfully Application executes correctly Debugger reaches main() I can debug the application normally Flash/XIP build: "Link application to RAM" disabled Application is linked to external Flash starting at 0x60000000 Build completes successfully .axf is generated When I start debugging, the debugger does not reach main() The CPU does not appear to execute from the expected 0x600xxxxx XIP address range Linker/map information The generated .map file shows the expected XIP layout: .boot_hdr 0x60000000 .boot_hdr.conf 0x60000000 .boot_hdr.ivt 0x60001000 .boot_hdr.boot_data 0x60001020 .text 0x60002000 .isr_vector 0x60002000 ResetISR 0x6000231C main 0x60004EF4 So the application appears to contain the expected FlexSPI NOR boot header, IVT, boot data, vector table, ResetISR, and application code. I also have: XIP_EXTERNAL_FLASH = 1 XIP_BOOT_HEADER_ENABLE = 1 Important observation After attempting to debug/program the Flash image, I checked the memory at: 0x60000000 0x60001000 0x60002000 and the memory window shows 0x00000000/empty data rather than the expected application contents. For example, at: 0x60002000 I expected the application vector table, but the memory appears to contain zeros. The CPU registers after the failed debug attempt also showed: PC = 0x0020E368 SP = 0x20200F70 LR = 0x0020ED49 rather than a PC in the expected 0x600xxxxx XIP region. Debug configuration I am using: Debug Connection: SWD Connect script: RT1040_connect.scp The Debug configuration has: Load image: enabled Use project binary: igpio_led_output.axf Load symbols: enabled Use project binary: igpio_led_output.axf Set breakpoint at: main Request hardware breakpoint: enabled The LinkServer Debug configuration is being used. Project contents The project contains the standard XIP-related files: xip/ ├── evkmimxrt1040_flexspi_nor_config.c ├── evkmimxrt1040_flexspi_nor_config.h ├── fsl_flexspi_nor_boot.c └── fsl_flexspi_nor_boot.h The generated linker script also places the boot header and application into the BOARD_FLASH region beginning at 0x60000000. My question Could someone please help me determine why the external FlexSPI NOR Flash is not being programmed with the generated XIP image when launching the LinkServer debug session? Specifically: Does the MIMXRT1040-EVK + LinkServer require a specific FlexSPI NOR Flash driver/configuration for debugging XIP applications? Is RT1040_connect.scp sufficient for both connecting and programming the external NOR Flash? Is there any additional Flash programming configuration required in the MCUXpresso Debug Configuration? Should the Debug configuration use a specific flexspi_nor Flash driver or Flash Tool configuration? Is there a known issue with LinkServer + MIMXRT1040 + external FlexSPI NOR + XIP debugging where the .axf is loaded as symbols but the external Flash is not actually programmed? Is there a recommended NXP example project/configuration that I can compare against for a working MIMXRT1040-EVK FlexSPI NOR XIP debug session? I would appreciate any guidance on what I should check next. Thank you. Re: MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Thank you for the response. I checked the MCU Settings → Memory details as you suggested. I have attached the screenshot. The BOARD_FLASH memory is configured as: Location: 0x60000000 Size: 0x800000 Flash Driver: MIMXRT1040_SFDP_QSPI.cfx So, it appears that the specific external Flash driver is already configured for BOARD_FLASH. I also tried the Serial Download Mode + MCU Provisioning Tool procedure. I was able to successfully Build Image and Write Image using the MCU Provisioning Tool. However, after that, I was still unable to get the application programmed/debugged from Flash through the normal MCUXpresso + LinkServer debug flow. Interestingly, when I tried flashing/debugging the code one more time later, it suddenly worked and the application was successfully running from Flash. I did not intentionally change the project configuration, Flash driver, linker configuration, or boot settings between the failed and successful attempts. So, at this point, I suspect there may be some intermittent issue related to the Flash programming/initialization/reset sequence rather than the application/linker configuration itself. Could you please advise what could cause this behavior on the MIMXRT1040-EVK? In particular: Is MIMXRT1040_SFDP_QSPI.cfx the correct Flash driver for the EVK's external FlexSPI NOR? Is the fact that the Default LinkServer Flash Driver field is blank significant, even though BOARD_FLASH has MIMXRT1040_SFDP_QSPI.cfx assigned in the Driver column? Could the external Flash remain in an unexpected state after a previous failed programming/debug attempt, requiring a specific reset or power cycle? Could RT1040_connect.scp or the LinkServer reset/connection sequence cause intermittent Flash programming behavior? Is there any known issue with the MIMXRT1040-EVK, LinkServer and MIMXRT1040_SFDP_QSPI.cfx where Flash programming may fail intermittently? Since the same configuration eventually worked without any intentional change, I would like to understand what could have caused the previous failure so that we can make the Flash debugging/programming reliable. Thank you. Re: MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Hi @Prashanth1 , Based on the screenshot you provided, the Flash driver configuration appears to be fine. Could you first try putting the board into serial download mode and using the MCUXpresso Secure Provisioning Tool to download the image to Flash by usb/uart? This method isolates the influence of the debugger and can be used to check whether the board has any flash hardware issues. Additionally, please provide me with the log of the failed download attempt using the debugger. On my end, I’ll arrange for an RT1040-EVK as soon as possible and try to reproduce the issue using the project package you previously attached. Best regards, Gavin Re: MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Hi Gavin Sir, Thank you for the response. I checked the MCU Settings → Memory details as you suggested. I have attached a screenshot. In my project, the BOARD_FLASH memory is configured as: Location: 0x60000000 Size: 0x800000 Driver: MIMXRT1040_SFDP_QSPI.cfx So, it appears that the FlexSPI NOR Flash driver is already associated with the BOARD_FLASH memory region. However, I noticed that the “Default LinkServer Flash Driver” field at the top of the MCU Settings is blank, while the driver column for BOARD_FLASH shows MIMXRT1040_SFDP_QSPI.cfx. Could you please confirm: Is this configuration correct for the MIMXRT1040-EVK? Should I also select MIMXRT1040_SFDP_QSPI.cfx in the Default LinkServer Flash Driver field? Or is the driver shown in the BOARD_FLASH row sufficient for LinkServer to program the external FlexSPI NOR? My main issue is that the application is correctly linked for XIP at 0x60000000, but after launching the LinkServer debug session, I don't see the application contents at 0x60000000 / 0x60002000 in the Memory window. RAM debugging works correctly with the same application. I have attached the MCU Settings screenshot for reference. Thank you.     Re: MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Hi @Prashanth1 , Thanks for your interest in NXP MIMXRT series! When using an external Flash, a specific Flash driver is required. Please check whether the Flash driver has been loaded correctly in the IDE: (My screenshot uses the RT1170 as an example; the process is similar for the RT1040.) Best regards, Gavin Re: MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Hi @Prashanth1 , Based on the described phenomenon, the most likely cause is that there was dirty data/image in the Flash memory previously. Whether it is an incorrect FCB header or an image that causes the MCU to enter an error state upon execution, such issues can lead to failure when attempting to re-flash the image. The standard recovery method in this scenario is to enter serial download mode. You may want to consult this article: https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/RT-board-recovery-for-debugger-connect-issues/ta-p/1635260 Regarding the selection of the flash loader, you simply need to select the appropriate flash driver in the "Flash" row within the IDE. The *.scp file is provided with the SDK and is used for pre-configuring the link server; You can go into the file to learn more about each line of command. Best regards, Gavin
查看全文
MC9S08QG8 CODE WARRIOR WELL, I WILL HAVE TO SAY GOOD BYE, IF THE DERIVATIVE MC9S08QG8 CAN NOT BE SEEN IN CW V6.3 OR CW 11.1. I HAVE WORKED AT GETTING THIS CODE TO WORK FOR 40 DAYS NOW. U SAID IT WAS OK, BUT I CAN NOT FIND ANY CW V6.3 WINDOWS 11 THAT WILL RUN AND DEBUG IN CW 11.1 OR CD 6.3. IF I AM WRONG , PLEASE LET ME KNOW.  Re: MC9S08QG8 CODE WARRIOR Hello, The MC9S08QG8 device is available in CodeWarrior v11.1 under the section S08>HCS08Q Family>MC9S08QG8 I tested with the following setup: OS: Windows 11 CodeWarrior: 11.1 Device: MC9S08QG8 in board DEMO9S08QG8 Debug Connection: Via the connection in board DEMO9S08QG8 (USB-to-BDM interface) Best Regards,
查看全文
Cloud lab Guide Visit Cloud Lab official websites: NXP Cloud Lab | NXP Semiconductors Find answers to common questions along with troubleshooting techniques related to using Cloud lab. 1. Registration How to register a cloud lab account? No additional account is required, you can just use your NXP account to sign in Cloud lab. Learn more about NXP account My NXP Account FAQs | NXP Semiconductors. 2. Sign in How to  log in Cloud lab.com Log in with your NXP Email address and password. Once logged-in, you should be able to access the cloud lab home page 3. Book your favorite EVKs How to book your favorite EVKs? You can book the HARDWARE Take “hardware” for example, all hot hardware will be shown by clicking “HARDWARE”, You can also click on the filter button-“view all boards”, to see all the EVKs in the Cloud Lab. Select one EVK and click “BOOK NOW”. Here, you can use it now by clicking on “USE NOW” or book the time to make an appointment. USE NOW: means you can immediately use this EVK, just need to select an end time and click “CONFIRM BOOK” Reserve an EVK: select the date and time  and click “CONFIRM BOOK” After booked,  pop-up windows will take you to “my book” page. Please note that user can only book one EVKs  in the same period. How can I check my reservation? You can manage your booking in “MY BOOK” page.  Let’s click the “debug” button and experience the cloud lab. 4. Debugging Is there any manual or guide for new cloud lab users? Scroll down to click the  “Download cloud lab manual” button to find more instructions about the cloud lab.  How can I watch the video  during debugging? You can watch the video of EVK board and see the light status. But please note that , the video will be closed in 30s. Pls click “ ” to play the video again. How can I debug my EVK board?  The command line will automatically connect the board serial port, when the camera is turned on. All EVK boards are Linux system, pls login with root.  Can I reset my EVK board when I facing some errors? Sure. Please click “Power Reset EVK” to hard reboot the board and wait several second, the board will be rebooted. Can I reinstall my EVK when I facing some errors? Sure. You can click the “Reinstall the system” button to recover the default setting. (It will take several minutes to reinstall the system , this action will also delete the files you created or modified. Pls save your copy before you reinstall the system.) How  can I upload/download files  during debugging? Click the “upload files to EVK” to upload the file you need. Please note that If you would like to upload files to board's Network File System(NFS),  you will find your files in board's /home/root path. If you would like to upload your own Image or dtb file,  use "TFTP" tab. 5. Support How  can I get supports from NXP engineers? Please go to Cloud lab Forum to raise a ticket for supports. https://community.nxp.com/t5/Cloud-Lab-Forums/ct-p/Cloud-Lab 6. Connect us If you any concern or any suggestion about our cloud lab, please don’t be hesitate to email us [email protected] Cloud Lab-Hardware Cloud Lab-Software Cloud Lab-Solution
查看全文
クラウドラボのログインと使用ガイド NXP Cloud Labsのウェブサイトをご覧ください: NXP Cloud Labs|組み込み設計を容易に行えるワンストップのクラウド開発プラットフォーム。 クラウドラボの利用に関する質問への回答や、クラウドラボ利用中に発生する問題のトラブルシューティングに関するヒントやコツをご覧ください。 1. 登録 クラウドラボのアカウントを登録するにはどうすればよいですか? NXP Cloud Labsにログインするために、追加のアカウント登録は必要ありません。NXPアカウントをお持ちであれば、ログインしてCloud Labsをご利用いただけます。 NXPアカウント登録について| NXPアカウントに関するよくある質問 | NXPセミコンダクターズ 2. ログイン クラウドラボにログインするにはどうすればよいですか? NXP.COMに登録したメールアドレスとパスワードを入力してください。 ログインに成功すると、次のページが表示されます。「ログイン」をクリックすると、Cloud Experimentのホームページに移動します。 3. 予約 興味のある開発ボードを予約するにはどうすればよいですか? 興味のあるハードウェア/ソフトウェア/システムソリューション/アプリケーションの例をクリックしてください。「ハードウェア」を例にとると、現在人気のハードウェアが表示されます。また、クラウド実験で現在オンラインになっているすべての開発ボードを表示することもできます。 興味のある開発ボードを1つ選択し、「今すぐ予約注文」をクリックしてください。すぐに使用するか、試用期間を設定するかを選択できます。 今すぐ利用:現在時刻からサービスをご利用いただけます。終了時刻を選択後、「予約確定」をクリックしてください。 利用予約をするには、希望の日付、開始時間、終了時間を選択し、「予約を確定」をクリックしてください。   予約が完了すると、予約ページに移動します(ただし、お客様お一人につき、デバッグ用の開発ボードは同時に1枚のみ予約可能ですのでご注意ください)。 注文した開発ボードを確認するにはどうすればよいですか? 「マイオーダー」ページでは、ご注文いただいたすべての開発ボードが表示され、注文内容を管理できます。下の「デバッグ」をクリックして、早速お試しください! 4. デバッグ デバッグ画面に入ったら、何をすればいいですか? コマンドボックスの一番下までマウスをドラッグすると、「クラウドラボマニュアルをダウンロード」という項目が表示されます。それをクリックすると、クラウドラボの操作ガイドがダウンロードされます。 デバッグ画面に入った後、どのようにビデオを視聴すればよいですか? 開発ボードのライブ映像を見ると、ボードの状態とインジケーターランプが表示されます。なお、映像は30秒後に自動的に終了します。再生するには、映像右上隅の再生ボタンをクリックしてください。 デバッグ方法は? カメラの電源を入れると、画面下部のコマンドラインが自動的に開発ボードのシリアルポートに接続されます。現在、すべての開発ボードはLinux 6.1.36を使用しており、ネットワークブートに対応しています。 デバッグ中は、Linuxファイルシステムに「root」ユーザーとしてログインしてください。  デバッグ中にいくつか問題が発生しました。予約注文した開発ボードを再起動することはできますか? はい、コマンドラインの右上隅にある「PowerReset EVK」ボタンをクリックすると、開発ボードの電源をオフにして再起動できます。 デバッグ中に、プリインストールされている開発ボードでポートが使用中と表示された場合、どうすればよいですか? 再接続するには、右上隅にある「再接続」ボタンをクリックしてください。 デバッグ中に問題が発生しました。予約注文した開発ボードにシステムを再インストールしたり、 Image/dtb/ファイルシステムを元のバージョンに復元したりすることは可能でしょうか? はい。「システムを再インストール」ボタンをクリックしてください。(この操作には時間がかかりますので、ご注意ください。この操作を行うと、使用中に作成または変更したファイルはすべて削除されます。このボタンをクリックする前に、必要なファイルはすべて保存してください。) デバッグプロセス中に 必要なファイルを アップロード / ダウンロードするにはどうすればよいですか? デバッグプロセス中に必要なすべてのファイルをアップロードするには、「EVKにファイルをアップロード」をクリックしてください。  ご注意ください:テストファイルを開発ボードのネットワークファイルシステム(NFS)にアップロードする場合、アップロードが成功すると、アップロードされたファイルは開発ボードの/home/rootパスに保存されます。独自のコンパイル済みイメージまたはdtbファイルを使用する場合は、TFTPボタンを選択してください。 5. テクニカルサポート NXPのエンジニアから技術サポートを受けるにはどうすればよいですか? ユーザーは、NXPコミュニティのクラウドラボセクション( https://community.nxp.com/t5/Cloud-Lab/bd-p/Cloud-Lab )にログインするか、デバッグウィンドウをクリックすることで、質問をしたり、サポートを受けたりすることができます。「コミュニティQ&A」セクションをクリックすると、NXPコミュニティクラウドラボのエリアに移動し、そこで質問を投稿できます。 6. お問い合わせ クラウドラボのご利用中に問題が発生した場合、またはご提案がございましたら、メールにてご連絡ください。( [email protected] ) クラウドラボ用ハードウェア クラウドラボソフトウェア クラウドラボソリューション
查看全文
云实验室登录使用指南 访问云实验室网站:恩智浦云实验室 | 一站式云上开发平台,助力轻松开展嵌入式设计 查找云实验室使用等相关问题的解答以及在云实验室使用过程中相关的疑难解答技巧。 1. 注册 如何注册云实验室账号? 恩智浦云实验室登录并不需要额外注册账号,拥有恩智浦账号即可登录体验云实验室 了解恩智浦账号的注册 恩智浦账号常见问题解答 | NXP 半导体 2. 登录 如何登录云实验室? 输入您在NXP.COM 注册的电子邮箱地址及密码 登录成功后会有如下的页面提示,点击“登录”后您将进入到云实验的首页。 3. 预定 如何预定您感兴趣的开发板? 点击您感兴趣的硬件/软件/系统方案/应用范例 以“硬件”举例,您将看到当前热门的硬件, 同时您可以点击查看当前云实验所有上线的开发板 选择其中一款您感兴趣的开发板,点击“立即预定”,在这里您可以选择立即使用和预约使用 立即使用:即从当前时间开始使用,选择好结束时间后,点击“确认预定” 预约使用:选择需要使用的日期,开始时间及结束时间,点击“确认预定”   预定成功后,将根据提示前往我的预定界面(请注意,同一时间段,同一客户只能预定一块开发板进行调试。) 如何查看我所预定的开发板? 在“我的预定”页面中,您将看到所有的您预定过的开发板并且管理您的预定,下面点击“调试”开始体验吧 4. 调试 进入调试界面后,我应该如何操作? 将鼠标拖到命令框最下方,可以看到Download cloud lab manual, 点击可下载云实验操作指南 进入调试界面后,如何观看视频? 观看当前开发板的实时视频,可以看到开发板的状态以及指示灯亮灭。需要注意的是,视频30s会自动取消,如果需要重新播放,需要点击视频右上角的播放按键, 如何进行调试? 摄像头打开后下方的命令行会自动进入开发板串口,目前所有开发板系统均为Linux6.1.36,支持网络启动。 调试时请使用“root” 登录Linux 文件系统  在调试过程中,我遇到了一些问题,我可以重启我预定的开发板么? 可以,点击命令行右上角“PowerReset EVK”按钮可以实现开发板的掉电及重启 在调试过程中,如果我预定的开发板能显示端口被占用,我应该如何操作? 点击右上角“Reconnection”按键即可重新连接。 在调试过程中,我遇到了问题,我可以将我预定的开发板进行重装系统或者将将Image/dtb/文件系统恢复为原始版本么? 可以。点击“Reinstall system”按钮。(此操作需要花费较长时间,请谨慎操作。 此操作会删除您在使用过程中新建/ 修改的文件,请在点击此按键前保存您所需要的文件信息)   在调试过程中,我如何上传/下载我所需要的文件? 点击“upload files to EVK”,可以上传您在调试过程中所有需要的文件,  需要注意的是:如果您想上传测试文件到开发板的网络文件系统(NFS),上传成功后,您会在开发板的/home/root路径下找到您上传的文件;如果您想使用自己编译的Image或dtb文件,选择TFTP 按键。 5. 技术支持 如何获得恩智浦工程师的技术支持? 用户可以通过登录恩智浦社区云实验室专区(https://community.nxp.com/t5/Cloud-Lab/bd-p/Cloud-Lab)提问获取帮助,或者点击调试窗口的 “Community Q&A” 跳转到恩智浦社区云实验室专区进行提问。       6. 联系我们 如果您在使用过程中有任何的问题或者您对我们的云实验室有任何的建议,你可以通过邮件的方式联系我们。([email protected]) Cloud Lab-Hardware Cloud Lab-Software Cloud Lab-Solution
查看全文
Cloud Lab Overview Welcome to use the Cloud lab.com. The Cloud lab is NXP’s first global platform where allows users to explore the latest NXP hardware, software or solutions online. Here users can remotely connect an evaluation board and do code debugging or technical evaluation online. All these EVKs are set in our onsite lab, each one is equipped with a high-definition camera, which monitors its status in real time. Users simply book the resource they are interested in, then they can use it within the predetermined period of time. After each usage period ending, the platform will automatically reinstall the system and clear the history to protect the privacy of each user. Our vision is to provide users with open resources, convenient and secure services and a cost-saving and resource-saving R&D experience. The Cloud Lab is willing to be a new fertile ground for every developer to test their ideas on new hardware platforms in time, experience the changes brought about by the latest NXP technologies, and receive real-time and professional technical support from NXP engineers. Let’s go! Explore the Cloud Lab and unlock your potential!  Click to visit :NXP Cloud Lab | NXP Semiconductors 欢迎使用云实验室官网。云实验室是恩智浦在全球范围内第一个可供用户线上使用恩智浦最新硬件、软件或解决方案的平台。 在这里,用户可以远程访问开发板进行线上调试和开发。这些开发板都安装在线下的实验室中,每块板子上方配有一个高清摄像头,可实时监控板子的状态。 用户只需在网站简单的预定其感兴趣的资源,就可在预定时间内尽情使用。每当一段预定时间结束,平台会自动重装系统、清理历史记录来保护每位用户的隐私。 我们的愿景是为用户提供开放的资源、便捷又安全的服务以及节约成本和资源的研发体验。 云实验室愿作每一位开发者的新沃土,让大家可以及时在新的硬件平台上测试他们的想法,体验最新恩智浦技术带来的变化,并获得恩智浦工程师实时和专业的技术支持。 来吧,让我们开启云实验室的大门,解锁无限之可能! 点击访问:恩智浦云实验室 | 一站式云上开发平台,助力轻松开展嵌入式设计 Cloud Lab-Hardware Cloud Lab-Software Cloud Lab-Solution
查看全文
Cloud Lab Login and Usage Guide Visit the NXP Cloud Labs website: NXP Cloud Labs | A one-stop cloud development platform to help you easily conduct embedded design. Find answers to questions related to using the cloud lab, as well as tips and tricks for troubleshooting related problems during the use of the cloud lab. 1. Registration How do I register a cloud lab account? No additional account registration is required to log in to NXP Cloud Labs; you can log in and experience the Cloud Labs with an NXP account. Understanding NXP Account Registration | NXP Account FAQs | NXP Semiconductors 2. Log in How do I log in to the cloud lab? Enter the email address and password you registered with NXP.COM After successfully logging in, you will see the following page prompt. Click "Log in" and you will be taken to the homepage of Cloud Experiment. 3. Reservation How can I reserve the development board that interests me? Click on the hardware/software/system solution/application example that interests you. Taking "hardware" as an example, you will see currently popular hardware. You can also click to view all the development boards currently online in the cloud experiment. Select one of the development boards that interests you and click "Pre-order Now". Here you can choose to use it immediately or schedule a trial period. Use Now: Start using the service from the current time. After selecting the end time, click "Confirm Reservation". To reserve a use: Select the desired date, start time, and end time, then click "Confirm Reservation".   After successful reservation, you will be directed to your reservation page (please note that each customer can only reserve one development board for debugging at the same time). How can I check the development board I ordered? On the "My Orders" page, you will see all the development boards you have ordered and be able to manage your orders. Click "Debug" below to start experiencing it! 4. Debugging Once I enter the debugging interface, what should I do? Drag your mouse to the bottom of the command box, and you'll see "Download cloud lab manual." Click it to download the cloud lab operation guide. How do I watch the video after entering the debugging interface? Watching the live video of the development board will show its status and the indicator lights. Note that the video will automatically cancel after 30 seconds. To replay it, click the play button in the upper right corner of the video. How to debug? Once the camera is turned on, the command line at the bottom will automatically enter the development board's serial port. Currently, all development boards use Linux 6.1.36 and support network boot. Please log in to the Linux file system as "root" during debugging.  During the debugging process, I encountered some problems. Can I restart my pre-ordered development board? Yes, clicking the "PowerReset EVK" button in the upper right corner of the command line can power off and restart the development board. During debugging, if my pre-installed development board shows that the port is occupied, what should I do? Click the "Reconnection" button in the upper right corner to reconnect. During the debugging process, I encountered a problem. Can I reinstall the system on my pre-ordered development board or restore the Image/dtb/ file system to its original version? Yes. Click the "Reinstall system" button. (This operation will take a long time, please proceed with caution. This operation will delete any files you create/modify during use, please save any necessary files before clicking this button.) How do I upload / download the files I need during the debugging process ? Click "upload files to EVK" to upload all the files you need during the debugging process.  Please note: If you want to upload test files to the development board's Network File System (NFS), you will find the uploaded files in the /home/root path of the development board after a successful upload; if you want to use your own compiled Image or dtb files, select the TFTP button. 5. Technical Support How can I get technical support from NXP engineers? Users can ask questions and get help by logging into the NXP Community Cloud Lab section ( https://community.nxp.com/t5/Cloud-Lab/bd-p/Cloud-Lab ), or by clicking the debug window. The "Community Q&A" section will redirect you to the NXP Community Cloud Labs area to ask your questions. 6. Contact Us If you encounter any problems during use or have any suggestions for our cloud lab, please contact us via email: ( [email protected] ) Cloud Lab-Hardware Cloud Lab-Software Cloud Lab-Solution
查看全文
Compilation Error on imx-95-FRDM unknown base path for fd 4, path include couldn't allocate absolute path for 'include'. tar: ./usr/include: Cannot mkdir: Bad address tar: ./usr/include/xen/gntdev.h: Cannot open: No such file or directory got *at() syscall for unknown directory, fd 4 unknown base path for fd 4, path include couldn't allocate absolute path for 'include'. got *at() syscall for unknown directory, fd 4 unknown base path for fd 4, path include couldn't allocate absolute path for 'include'. tar: ./usr/include: Cannot mkdir: Bad address tar: ./usr/include/xen/evtchn.h: Cannot open: No such file or directory Re: Compilation Error on imx-95-FRDM Hi @Asadeds  What is your BSP version? I checked it on my Imx95 FRDM and there are no problems. B.R
查看全文
What kind of port does the T Embed have? I have the standard model T Embed, but i have no Idea what kind of port it has (the other port, not usb c), because the official site says its a grove port, the lilygo Wiki site says its a qwiic port. Can anyone help me please?
查看全文
I.MX93 boot waiting for known usb device Bought IMX93 from Mouser  for NXPLinux summer school program, I used there the automated script to boot the board,  ./scripts/ loss.py boot command . After executing the command I keep getting waiting  for known usb device. Will appreciate all the help to enable me progress Ias am stuck . FRDM-i.MX93  Re: I.MX93 boot waiting for known usb device @Fidelbanks thanks a lot for your interest in i.MX FRDM board. I think your problem is similar with  https://community.nxp.com/t5/i-MX-Processors/I-MX93-UUU-emmc-sdcard-LIBUSB-ERROR-TIMEOUT-Error/td-p/2402801 @pengyong_zhang Linux kernel summer school is a project that wants to help people getting started with learning linux kernel by using the i.MX93 frdm board.  https://nxp-research.github.io/lkss-main/2026/about.html#getting-started We provided a script that helps users boot the board using the serial download mode Re: I.MX93 boot waiting for known usb device Hi @Fidelbanks  What project are you referring to? If you want to get started with the development board, you can directly use the demo image from the NPX website. I'm not familiar with how your summer school program is implemented. B.R
查看全文
PPF0900AMBA1ES Hi NXP team, I'm working on a custom board based on the i.MX95 (MIMX9596, 19x19 package, LPDDR5), using the PPF0900AMBA1ES PMIC. Could you please confirm: 1.Does this part number ship with OTP already programmed, or is it a non-programmed engineering sample? 2.If it is non-programmed, what is the recommended procedure to program (or emulate) the OTP configuration for bring-up and evaluation purposes? 3.Is a reference OTP configuration file (.CFG) available for an i.MX95 + LPDDR5 (19x19) implementation that we could use as a starting point? For context, our schematic closely follows the i.MX95 EVK reference design (PF09 + PF5301 + PF5302), and we're currently doing initial power-on bring-up. Thank you. PMIC Re: PPF0900AMBA1ES  PPF0900AMBA1ES is OTP part which mean had already done OTP. https://www.nxp.com/docs/en/supporting-information/MPF0900AMBA1ES.zip OTP file please download from above link.
查看全文
S32G2 Enabling Multicore Application Hi, nxp fellows: We are preparing to use multi-core to run programs in the S32G274A chip, using A53 to run Linux and M7 to run LLCE_CAN. We referred to "Enabling Multicore Application on S32G2 using S32G2 Platform Software Integration", according to 5.2. Configure the bootloader, installed the recommended software packages, and configured them following the steps. There is an error in 5.3. Build The Bootloader during compilation. The launch.bat file was edited. An error occurred after running launch.bat.  After commenting out the relevant code. I found the CryptoDal.h file in the installation directory. Where could there be any mistakes? Thanks. Re: S32G2 Enabling Multicore Application Hi,zhipeng Is Secure Boot enabled in the configuration? Try to enable the Secure boot, check if the issue will disappear. BR Joey Re: S32G2 Enabling Multicore Application Hi, @Joey_z  Yes, after adding, it will show "undeclared" on the third image. Commenting out will show "No such file or directory", on the fifth image. "CryptoDal.h" is located in D:\NXP\Integration_Reference_Examples_S32G2_2022_06\code\framework\realtime\bsw\dal\cryptodal\generic\include "Hse_Ip.h" is located in D:\NXP\SW32G_RTD_4.4_3.0.2_HF01\eclipse\plugins\Crypto_TS_T40D11M30I2R0\include I have found both files in their respective folders, and the file paths are also written in launch.bat. The current problem feels like the plugin path was not included during the compilation process. BR Re: S32G2 Enabling Multicore Application Hi,zhipeng For your issue, will there be an error if the following contents are added? Is it commenting out won't cause an error? BR Joey
查看全文
Skid-steer robot state space modelling???? Hey everyone! I'm a beginner and just started working at a decently big lab with a bunch of people and I needed to figure a few things out. We're working on a skid-steer robot. I understand the dynamic and kinematic equations mathematically, but I don't know HOW exactly to convert them into state space. (which was the requirement) My team has the CAD model and they need to extract the Inertial Mass Parameters. They're a very chaotic group and I tried asking them, but they themselves don't have it together.😭 There's no well put resource for this kinda stuff either, and I'm genuinely at a loss of how to proceed with anything meaningful. Any pointers, help, and resources are appreciated! Cheers. Re: Skid-steer robot state space modelling???? Hello @prash, Could you please, provide me the following information? -Which NXP product are you currently using? Are you working with one of our EVKs, a custom board based on NXP MCU/MPU product, or another hardware solution? -Which IDE you are using? BR Habib
查看全文
Compatibility of Camera module with OX05B1S Sensor and in-built ISP with i.MX95 FRDM Hi All, Want to know if camera module with ox05b1s sensor and in-built ISP (similar to 5MP RGB-IR Global Shutter GMSL2 Camera for NVIDIA Jetson AGX Orin would be compatible with i.MX95 FRDM board). I do understand that i.MX95 only have MIPI_CSI2 port hence I need to find GMSL2 to MIPI_CSI2 converter, however my question is specifically related to compatibility of existing driver that is part of NXP Linux BSP. Will driver Camera driver of NXP Linux release directly work with this camera module? Do I need to make modification in dtb file? Any other modifications would or additional work that I need to plan for?
查看全文
Whether USB serial download mode can work or not Hi Sir, In our current project, our product has only “one” “USB-C” port, running USB 2.0 High Speed. Our target application is to use this USB port as USB host role to connect USB stick or solid state drives for local recording. However, our next revision PCB circuitry is to pull up 56K Ohm to VCC_5V0 on both CC pins of USB-C, as shown below. That is, we hardwire fixed the USB port to USB host based on CC configuration definition. There is no separate Jumper / Switch / Type-C Controller(DRP(Dual Role Port) logic IC) circuitry that can switch the CC pin between host and device. We would like to know, based on this circuitry, can i.MX8M+ USB Serial Download Mode still work? We understand when i.MX8M+ Boot ROM activates USB Serial Download mode, the port is automatically configured as a USB device(for USB Serial Download mode to work), but that should mean the chip's ROM code only controls the internal USB PHY to be device mode, it cannot override the hardware's external CC resistor states(Type-C Port role). As a result, the PC is entirely unable to enumerate the i.MX 8M Plus via USB(both cannot finish handshaking(Type-C Attach) from USB physical layer point of view), which causes the UUU programming to fail. If the above statement is correct, the USB Serial Download Mode will become inoperable before boot(i.e. will not work at all), resulting in the loss of factory production flashing and system unbricking capabilities. Is our understanding correct? Best regards Re: Whether USB serial download mode can work or not Hi @Esther_Liu  You are right, If you force CC to be a pull-up, it will remain in HOST mode, and UUU will likely malfunction. B.R
查看全文
S32K324 write DFlash by FEE Hello, There is a question about S32K324 write DFlash by FEE: I plan to write approximately 50 bytes of data into the DFalsh of S32K324 using the FEE method. Since the hardware power supply on the circuit board has a backup time of around 0.743ms, I need to save the critical data within this time frame. Is it feasible to write to the DFlash using the FEE method? If it is not feasible, are there any other options? Thanks. Re: S32K324 write DFlash by FEE Hi@mmyjh_123 For a power-off backup window of 0.743 milliseconds, FEE is not safe. Even "close to 1 millisecond," the write execution time for a single Fls_MainFunction block already exceeds your available hold time. You could try using C40_Ip. Using Quad-page (1024 bits) program time, a 50-byte write would theoretically take 450 microseconds. However, within 0.743 milliseconds, any erase operation during an emergency hold is impossible; erasing an 8 KB sector could take up to 30 milliseconds. Therefore, when implementing this functionality using C40_Ip, always erase the DFLASH address to be programmed during idle periods. Furthermore, if the board can detect input voltage drops before the MCU power failure, commit operations should begin at the earliest possible threshold. Otherwise, add a large capacity capacitor/backup power to ensure the guaranteed window covers the worst-case software path and flash programming margin. The above is only a theoretical analysis; multiple real-world tests are recommended, ensuring sufficient design margins. Re: S32K324 write DFlash by FEE Ok, thanks a lot.
查看全文
I.MX93 - UUU emmc/sdcard LIBUSB_ERROR_TIMEOUT Error Hi NXP Team, We are trying to flash an i.MX93 board using a .wic image file provided by our team. We have two i.MX93 boards with the same hardware revision (SCH-96411 REV_B2). On one board, we are able to successfully flash the .wic image. However, when attempting to flash the same image on the second board, we encounter an error. We have tested both: emmc_all (for eMMC flashing) sd_all (using an SD card) In both cases, the same issue occurs on the second board. We would appreciate your support in troubleshooting and resolving this issue. Please let us know if you need any additional logs, error messages, or board information. Providing both uuu command and debugProviding both uuu command and debugProviding both uuu command and debugProviding both uuu command and debug uuu supported listuuu supported listuuu supported listuuu supported list i.mx93 usb identifiedi.mx93 usb identifiedi.mx93 usb identifiedi.mx93 usb identified Re: I.MX93 - UUU emmc/sdcard LIBUSB_ERROR_TIMEOUT Error Hi, Thank you for your interest in NXP Semiconductor products, It's good to have schematic identification, I would recommend confirming i.MX 93 top marking though. Confirm that they share TOP marking. Please download latest prebuilt image release from Linux. Finally, you are trying to flash both of them in serial download and do they have any fuses blown? Regards Re: I.MX93 - UUU emmc/sdcard LIBUSB_ERROR_TIMEOUT Error Hi Please find the attached images. We noticed some changes in the IC part numbers. We also tried flashing the SD card externally and then inserting it into the i.MX93 board, but we are still encountering the same issue. Additionally, we would like to bring to your attention that an image is already present in the eMMC, and the board is able to boot successfully from it. However, when we attempt to flash a new image, we encounter errors. Please find the attached debug logs below. One observation is that the preloaded image that came with the board is showing U-Boot SPL 2025.04, whereas the image we are attempting to use shows U-Boot SPL 2024.04. We downloaded the latest Linux 6.18.20_2.0.0 (i.MX93 EVK, FRDM) release. However, we could only find the 14x14 EVK WIC image and were unable to locate an 11x11 FRDM WIC image package. Could you please confirm whether the 14x14 image is the correct one to use for our board, or if there is a separate 11x11 FRDM image available? SD Card Boot: U-Boot SPL 2024.04+gde16f4f1722+p0 (Sep 02 2024 - 10:44:35 +0000) SOC: 0xa1009300 LC: 0x2040010 PMIC: PCA9451A PMIC: Over Drive Voltage Mode DDR: 3733MTS DDR: 3733MTS M33 prepare ok eMMC Boot: U-Boot SPL 2025.04-g99518e6b6f20 (Feb 02 2026 - 05:52:54 +0000) PMIC: PCA9451A PMIC: Over Drive Voltage Mode DDR: 3733MTS found DRAM 2CS_2GB DRAM matched M33 prepare ok Normal Boot Trying to boot from BOOTROM Boot Stage: Primary boot image offset 0x8000, pagesize 0x200, ivt offset 0x0 Load image from 0x57800 by ROM_API NOTICE: TRDC init done NOTICE: BL31: v2.12.0(release):lf-6.18.2-1.0.0 NOTICE: BL31: Built : 07:53:18, Feb 10 2026 /****************************************************/ Regarding the fuse being blown, could you please let us know how we can verify whether the fuses have been programmed or blown on the board? Thank you. Issue board - imx93Issue board - imx93Issue board - imx93 Working board - imx93Working board - imx93Working board - imx93 Re: I.MX93 - UUU emmc/sdcard LIBUSB_ERROR_TIMEOUT Error I've got similar issues and per my understanding, the Chinese manufacturer who is behind FRDM series changed DDR RAM IC. This requires re-training DDR and update to u-boot, which was done for the board software, committed to nxp's u-boot repo, but the BSPs, Yocto layers and binary images on web site wasn't updated. Basically newer boards work with built-in u-boot only, everything your developers build with BSPs (and u-boot from 2024) will not even start due to invalid ddr configuration. You could confirm this issue by booting from board's u-boot, stop it using keyboard and then manually load your custom linux kernel and DT from the SD card.
查看全文