Multi Source Translation Content

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

Multi Source Translation Content

讨论

排序依据:
Yocto Project™ Advanced A guide to developing with the Yocto Project for i.MX application processors. Learn how to leverage the Yocto Project in development by adding layers and recipes, customizing images, working with the kernel, and other essential Yocto development tasks. A guide to developing with the Yocto Project for i.MX application processors. Learn how to leverage the Yocto Project in development by adding layers and recipes, customizing images, working with the kernel, and other essential Yocto development tasks. i.MX Applications Processors Re: Yocto Project™ Advanced These slides use the 3.10 Kernel and meta-fsl-arm?  Isn't this stale?  The last commit to meta-fsl-arm was in 2016:  meta-fsl-arm - Layer containing Freescale ARM hardware support metadata  I was very much looking forward to reading about the current tips & tricks for building with i.MX & Yocto, but I don't think this is it. 
查看全文
信息娱乐、连接和安全:适用于 i.MX 8 应用处理器的 AUTOSAR MCAL <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本讲座将向您讲解 NXP 的 i.MX 8 AUTOSAR MCAL 和安全 MCAL 产品的具体信息。由于 ECU 设计方法从编码转向配置,它们为您的产品开发成本和时间带来巨大的好处。对于许多采用 i.MX MPU 的汽车 ECU 产品来说,它们成为 AUTOSAR 分层架构的重要组成部分。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本讲座将向您讲解 NXP 的 i.MX 8 AUTOSAR MCAL 和安全 MCAL 产品的具体信息。由于 ECU 设计方法从编码转向配置,它们为您的产品开发成本和时间带来巨大的好处。对于许多采用 i.MX MPU 的汽车 ECU 产品来说,它们成为 AUTOSAR 分层架构的重要组成部分。 i.MX 应用处理器
查看全文
SD-CPE—A CPE to be Deployed with VM (Docker, etc.) and Managed by Orchestrator Concept of SD-CPE, virtualization of functions/applications on CPE, centralized management of CPE by orchestrator, advantages, and applications scenario in home, enterprise and industry. Concept of SD-CPE, virtualization of functions/applications on CPE, centralized management of CPE by orchestrator, advantages, and applications scenario in home, enterprise and industry.
查看全文
このビデオでは、LPC55S69を AWS に接続する方法を示します <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 詳細については、NXP設計の完全ガイドをご覧ください:https://community.nxp.com/docs/DOC-344585  (マイビデオで視聴) スマートホーム
查看全文
Example MPC5777C External SRAM_test GHS714 ******************************************************************************** * Detailed Description: * Application performs basic initialization then it initializes EBI for external * SRAM connected to MPC5777C-516DS and test it by write and read of block of * data. * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 3N45H * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A * EVB connection:  jumper J4 on position 1-2 (choosing CS0) * ******************************************************************************** ******************************************************************************** * Detailed Description: * Application performs basic initialization then it initializes EBI for external * SRAM connected to MPC5777C-516DS and test it by write and read of block of * data. * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 3N45H * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A * EVB connection:  jumper J4 on position 1-2 (choosing CS0) * ********************************************************************************
查看全文
NXP Technology Form #NXPFTF 2016, we will join! - TechNexion 2016 May 16 - 19 we will again be at the NXP Technology Forum. Formerly called ftf it is now the NXPFTF 2016 TechNexion will be there and show our latest small Modules or chat with you about our Software and where to get it. Of course we are also looking forward to see all the new cool things we are expecting NXP to show. Being exited to have our tiny PICO Module scaling from Cortex-A7 i.MX6 Ultralite over Cortex-A9 single/dual lite/quad or with the NXP i.MX7 solo and dual (both Cortex-A7) but also introducing our other solutions. I'm sure there are a lot of customer which will find our EDM solution the perfect fir for their needs: We are looking forward to meet yo and all the other amazing people and exchange our ideas! For sure it will be a great event, also if now under a slightly different name, but that's still ok  FTF, here we come!! Register here: http://www.nxp.com/support/classroom-training-events/nxp-ftf-tech-forum:NXP-FTF-TECH-FORUM-HOME nxpftftechforum​ General
查看全文
Industry 4.0 Connectivity Demo Industry 4.0 connectivity or Industrial IoT  combines the existing high Level network based on Ethernet type Protocols and the access  to a single sensor data.  IO Link protocol helps in that convergence by providing an easy migration of current of non-connected sensors to networked one. The demonstration show a typical Industrial Network using ModBus and IO Link sensors Features Modbus TCP Slave based on LS1021A Open source stack & Support for Industrial Strength Security Master IOLink Modem  node based on Kinetis KL17 + transceiver Device Node IOlink based on Kinetis KE02 + transceiver NXP Recommends Product Link QorIQ® Layerscape 1021A Dual-Core Communications Processor with LCD Controller https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/layerscape-communication-process/qoriq-layerscape-1021a-dual-core-communications-processor-with-lcd-controller:LS1021A?&lang_cd=en Freedom® Development Platform for Kinetis® KL17 and KL27 MCUs FRDM-KL27Z|Freedom Development Platform|Kinetis® MCU | NXP  Freedom Development Platform for Kinetis KE02 MCUs https://www.nxp.com/design/development-boards/freedom-development-boards/mcu-boards/freedom-development-platform-for-kinetis-ke02-mcus:FRDM-KE02Z40M?&lang_cd=en QorIQ® LS1021A Tower® System Module QorIQ® LS1021A Tower® System Module | NXP  Industrial
查看全文
Team 8 UC Berkeley Freescale Cup Report
查看全文
eMSG インバウンドコンテキスト管理 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
查看全文
How to add support for K60 120MHz part in USB stack ver 4.1.1 Actually the latest FSL USB stack has become part of KSDK , so it is recommended customer design USB application based on KSDK, while there are some old parts like K70, K60F and KL25 are still not supported in KSDK yet, so USB stack ver 4.1.1 is somewhat of help for those who still develop application based on those parts. USB stack ver 4.1.1 supports K70 instead of K60F, but since they are both Kinetis 120MHz parts, so the porting is very easy, here I provide a porting guide for this part. The porting is based on K70 USB examples, either Host or Device. 1. Replace the device header file. Use MK60F12.h instead, which may be extracted from KINETIS_120MHz_SC(Kinetis 120MHz bare metal sample code) , and put this header file in the folder of "C:\Freescale\Freescale USB Stack v4.1.1\Source\Host\source\bsp\P3" for Host or "C:\Freescale\Freescale USB Stack v4.1.1\Source\Device\app\common\kinetis" for device, and modify derivative.h as  below: 2. Macro definition changes in MK60F12.h, MCU_MK60F12 is defined instead of MCU_MK70F12, so in this step we will have to change some code snippet related with MCU_MK70F12. Firstly search MCU_MK70F12 in the project, for example , in the Host demo USB_MSD project based on IAR, you may do that as below: and you may find some macro like "#ifdef MCU_MK70F12" or "#ifndef MCU_MK70F12", and change them as below: #ifdef MCU_MK70F12 ----> #if (defined MCU_MK60F12) || (defined MCU_MK70F12) #ifndef MCU_MK70F12 ----> #if (!defined MCU_MK60F12) && (!defined MCU_MK70F12) 3. IO driver modification. Since TWR-K70F120 has almost the same hardware as TWR-K60F120, there is no need to change the driver code after replacing the header file, except the serial port driver, referring to USB_MSD demo, the serial driver is in sci_kinetis.c, TWR-K70F120M uses PTE16 and PTE17(UART2) as the console, while TWR-K60F120M use PTE8 and PTE9(UART5) instead, so you have to change the driver as below to make printf work properly. void sci2_init(){ #if (defined MCU_MK60F12) || (defined MCU_MK70F12)     register uint_16 sbr, brfa;     uint_8 temp; #ifdef MCU_MK70F12     /* Enable the UART2_TXD function on PTD3 */     PORTE_PCR16 = PORT_PCR_MUX(0x3); // UART is alt3 function for this pin     /* Enable the UART2_RXD function on PTD2 */     PORTE_PCR17 = PORT_PCR_MUX(0x3); // UART is alt3 function for this pin     /* Enable the clock  */     SIM_SCGC4 |= SIM_SCGC4_UART2_MASK;     /* Make sure that the transmitter and receiver are disabled while we      * change settings.      */     UART_C2_REG(UART2_BASE_PTR) &= ~(UART_C2_TE_MASK | UART_C2_RE_MASK);     /* Configure the UART for 8-bit mode, no parity */     UART_C1_REG(UART2_BASE_PTR) = 0;    /* We need all default settings, so entire register is cleared */     /* Calculate baud settings */     sbr = (uint_16)((SYSCLK*1000)/(UART_BAUDRATE * 16));     /* Save off the current value of the UARTx_BDH except for the SBR field */     temp = UART_BDH_REG(UART2_BASE_PTR) & ~(UART_BDH_SBR(0x1F));     UART_BDH_REG(UART2_BASE_PTR) = temp |  UART_BDH_SBR(((sbr & 0x1F00) >> 8));     UART_BDL_REG(UART2_BASE_PTR) = (uint_8)(sbr & UART_BDL_SBR_MASK);     /* Determine if a fractional divider is needed to get closer to the baud rate */     brfa = (((SYSCLK*32000)/(UART_BAUDRATE * 16)) - (sbr * 32));     /* Save off the current value of the UARTx_C4 register except for the BRFA field */     temp = UART_C4_REG(UART2_BASE_PTR) & ~(UART_C4_BRFA(0x1F));     UART_C4_REG(UART2_BASE_PTR) = temp |  UART_C4_BRFA(brfa);       /* Enable receiver and transmitter */     UART_C2_REG(UART2_BASE_PTR) |= (UART_C2_TE_MASK    | UART_C2_RE_MASK); #else   //MCU_MK60F12         /* Enable the UART2_TXD function on PTE8 */     PORTE_PCR8 = PORT_PCR_MUX(0x3); // UART is alt3 function for this pin     /* Enable the UART2_RXD function on PTE9 */     PORTE_PCR9 = PORT_PCR_MUX(0x3); // UART is alt3 function for this pin                /* Enable the clock  */     SIM_SCGC1 |= SIM_SCGC1_UART5_MASK;     /* Make sure that the transmitter and receiver are disabled while we      * change settings.      */     UART_C2_REG(UART5_BASE_PTR) &= ~(UART_C2_TE_MASK | UART_C2_RE_MASK);     /* Configure the UART for 8-bit mode, no parity */     UART_C1_REG(UART5_BASE_PTR) = 0;    /* We need all default settings, so entire register is cleared */     /* Calculate baud settings */     sbr = (uint_16)((SYSCLK*1000)/(UART_BAUDRATE * 16));     /* Save off the current value of the UARTx_BDH except for the SBR field */     temp = UART_BDH_REG(UART5_BASE_PTR) & ~(UART_BDH_SBR(0x1F));     UART_BDH_REG(UART5_BASE_PTR) = temp |  UART_BDH_SBR(((sbr & 0x1F00) >> 8));     UART_BDL_REG(UART5_BASE_PTR) = (uint_8)(sbr & UART_BDL_SBR_MASK);     /* Determine if a fractional divider is needed to get closer to the baud rate */     brfa = (((SYSCLK*32000)/(UART_BAUDRATE * 16)) - (sbr * 32));     /* Save off the current value of the UARTx_C4 register except for the BRFA field */     temp = UART_C4_REG(UART5_BASE_PTR) & ~(UART_C4_BRFA(0x1F));     UART_C4_REG(UART5_BASE_PTR) = temp |  UART_C4_BRFA(brfa);        /* Enable receiver and transmitter */     UART_C2_REG(UART5_BASE_PTR) |= (UART_C2_TE_MASK    | UART_C2_RE_MASK); #endif        #endif } #ifdef __CC_ARM int sendchar (int ch) #else void TERMIO_PutChar (char ch) #endif { #if (!defined MCU_MK60F12) && (!defined MCU_MK70F12)     #if (defined MCU_MK20D5) || (defined MCU_MK20D7) || (defined MCU_MK40D7)         /* Wait until space is available in the FIFO */         while(!(UART1_S1 & UART_S1_TDRE_MASK)){};                /* Send the character */         UART1_D = (uint_8)ch;       #elif(defined MCU_MK21D5)         while(!(UART2_S1 & UART_S1_TDRE_MASK)){};                /* Send the character */         UART2_D = (uint_8)ch;       #elif(defined MCU_MKL25Z4) || (defined MCU_MKL46Z4)         /* Wait until space is available in the FIFO */         while(!(UART0_S1 & UART_S1_TDRE_MASK)){};        /* Send the character */        UART0_D = (uint_8)ch;       #else         /* Wait until space is available in the FIFO */         while(!(UART3_S1 & UART_S1_TDRE_MASK)){};                /* Send the character */         UART3_D = (uint_8)ch;     #endif   #else #ifdef MCU_MK70F12     /* Wait until space is available in the FIFO */     while(!(UART2_S1 & UART_S1_TDRE_MASK)){};     /* Send the character */     UART2_D = (uint_8)ch; #else      /* Wait until space is available in the FIFO */     while(!(UART5_S1 & UART_S1_TDRE_MASK)){};     /* Send the character */     UART5_D = (uint_8)ch; #endif #endif } 4. Set the correct device type in IDE settings. For IAR, change the device family in view of project options. Now, you can start to run the USB demos on TWR-K60F120M, please note the above steps is ok for USB device stack, but USB Host stack has some code issue , as mentioned in [USB stack ver 4.1.1] a code issue in msd_mfs_generic host demo , so please fix the issue before going further. Hope that helps, Best Regards, Kan USB Re: How to add support for K60 120MHz part in USB stack ver 4.1.1 Hi, I made these changes but ran into an error due to this function not being defined when compiling: void USB_ISR(void); In usb_dci_kinetis.h, this function is only defined for #if !HIGH_SPEED_DEVICE  Is this portion of the code different for a HIGH_SPEED_DEVICE? I am trying to use HS for my application. Thanks for any insights!!
查看全文
Kinetis M series VREF module trim function linearity Analysis VREF module provide one input pin VREF, this pin can provide reference voltage for both external circuit but also for internal Sigma Delta ADCs, AFE and DAC.  Also it includes trim function in it. In this document, I would like to use my testing to do a linearity analysis. From figure1 and 2, you can find how to make VREF as reference voltage of different analog module. For example, you can find when S1 switches down, S0 closes and S2 select VREF, VREF will be voltage resource of SAR ADC.                                               Figure 1: Voltage reference function configuration                                   Figure 2: Voltage reference module diagramming I do a testing for VREF trim value linear analysis. The process is connecting the voltmeter to VREFH pin, then record measure result for each setting of VREF trim. There will be 64 records for every different setting. Testing chip is MKM34Z256. Please find my testing result from testing data table. From testing result, you can get the formula that y = kx + x0, where k is about 0.005 (5mV) and x0 is about 1.1881, x is trim value.  You can find there is only a little offset from offset curve.                                         Table 1: Trim voltage testing date                                                                 Figure 3: Offset curve
查看全文
RIoTboard <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> RIoTboard是一个开源单板平台,基于采用 ARM ® Cortex ® -A9 架构的 i.MX 6Solo 处理器,旨在帮助设计师和业余爱好者加快开发速度。     •更快的上市时间 •成本低 •支持 Linux 和 Android Jelly Bean •开放平台参考设计   •开源 •以开发者为中心的社区 RIoTboard.org •参考设计可作为知识共享 (点击放大) • 采用 NXP 的设计 i.MX 6Solo处理器 基于ARM ® Cortex ® -A9 Core ®架构,运行速度高达1 GHz。 使用 Kinetis K20 MCU 的 集成调试电路 PMIC(电源管理集成芯片)(MMPF0100)   在R IoT board.org开始你的革命   概述 回复:RIoTboard <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好: 我对这块主板很感兴趣,因为 i.MX6 SOLO 芯片最适合我们的应用。不幸的是,这款主板似乎不再生产或出售。如果有人能验证我的结论是否正确和/或提供任何其他结论,我将不胜感激。 此致,
查看全文
飞思卡尔 iMX6 处理器 - Garz & Fricke SANTARO 10.4 盒装 PCT/电阻 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Garz & Fricke 产品 SANTARO 将在即将于纽伦堡举行的嵌入式世界展会期间在飞思卡尔展位上展出。 SANTARO 使用飞思卡尔 iMX6 处理器。单核、双核和四核。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Garz & Fricke 产品 SANTARO 将在即将于纽伦堡举行的嵌入式世界展会期间在飞思卡尔展位上展出。 SANTARO 使用飞思卡尔 iMX6 处理器。单核、双核和四核。
查看全文
Garz & Fricke - 适用于 iMX 6 产品的 Bootloader Flash N Go <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
查看全文
i.MX25 参考手册 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 这是当前发布的 i.MX25 参考手册的副本,用于输入社区评论。请随意在此参考手册中添加内嵌注释。您可以指出哪里需要更多信息或者哪里现有信息不正确。您还可以根据您使用该设备的经验,在评论中输入扩展文档中现有信息的信息。如果您指出某个段落或章节需要更多信息,请具体说明,而不是“需要更多信息”。您在本手册中的评论可能会对其他成员有所帮助,并将推动本文档和未来文档的改进。 注意:文档查看器不支持直接转到指定页面。您无需手动逐页翻阅,而是可以搜索页面上的字符串(例如“重置类型”),或者转到内联注释中列出的章节链接。为此,请向下翻页到文档视图下方的注释,选择“内联注释”,按“页面”对注释进行排序,然后选择要查看的章节。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 这是当前发布的 i.MX25 参考手册的副本,用于输入社区评论。请随意在此参考手册中添加内嵌注释。您可以指出哪里需要更多信息或者哪里现有信息不正确。您还可以根据您使用该设备的经验,在评论中输入扩展文档中现有信息的信息。如果您指出某个段落或章节需要更多信息,请具体说明,而不是“需要更多信息”。您在本手册中的评论可能会对其他成员有所帮助,并将推动本文档和未来文档的改进。 注意:文档查看器不支持直接转到指定页面。您无需手动逐页翻阅,而是可以搜索页面上的字符串(例如“重置类型”),或者转到内联注释中列出的章节链接。为此,请向下翻页到文档视图下方的注释,选择“内联注释”,按“页面”对注释进行排序,然后选择要查看的章节。 回复:i.MX25参考手册 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 应该是 表 23-26 中的“写入水印级别的最大合法值为 128” 反而 msgstr "写入 水印 级别 的 最大 合法 值为 127 " . 突发长度字段(WR_BRST_LEN 和 RD_BRST_LEN)的默认/重置值为 0b00100 是正确的(而不是 0b01000)
查看全文
i.MX27 ADS 添加 USB Host2 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 在 i.MX27ADS 上添加对 USB 主机高速的支持 首先,确保已应用以下补丁: usbh2_cspi1_ss2.补丁 usbh2_set_ulpi_xcvr.补丁 取消选择SPI2: 设备驱动程序 ---> SPI支持---> [ ] CSPI2 选择 USB 主机 2: USB支持---> EHCI HCD(USB 2.0)支持 [*] 支持飞思卡尔控制器上的 Host2 端口 i.MX2x
查看全文
Kinetis K53 Medical Teaching Lab from the University of Brasov The Technical University in Brasov (Romania) has set up a Medical Teaching lab featuring the Freescale Tower Kit K53 with Oximeter MED-SPO2 and 2 electrode system EKG MED-EKG. Find below the material associated to this lab led by Prof. Sorin-Aurel Moraru from the Faculty of Engineering. He can be contacted at [email protected] The course is in Romanian and include an overview of the hardware and exercises
查看全文
IMX27 PDK NAND Flashing RedBoot Flashing Kernel and Root File System using RedBoot Creating an image A kernel image and a root file system can be created using All Boards LTIB or compiling the kernel and setting the correct set of files. Create a root file system image from a set of files converting the files to a jffs2 file system. For this, install the package mtd-tools. In Ubuntu type apt-get install mtd-tools For making an root file system for flash, use the jffs2 file system like: mkfs.jffs2 -r rootfs -e 0x20000 -s 0x800 –n -o rootfs.jffs2 Where rootfs/ is the original set of file for the file system and rootfs.jffs2 is the output image file. Flashing Some connections errors can be avoided by Configuring RedBoot. The process below uses TFTP to copy the files between host and target. See All Boards TFTP for detail in configurations. Copy the kernel image and the root file system image to the TFTP dir. For example, in LTIB dir, type sudo cp ./rootfs/boot/zImage /tftpboot sudo cp rootfs.jffs2 /tftpboot/ Where /tftpboot is the dir configured for TFTP The next steps are performed in a Minicom session, and happens on the board. Formatting the flash: Format the flash redboot> fis init -f Make a Bad Block Table redboot> nand scan Flashing kernel Load kernel image (zImage) using the command below. Remember to modify the host IP address: redboot> load -r -b 0x100000 /tftpboot/zImage -h 10.29.244.99 The address 0x100000 is used as a temporary location Create the kernel at the right address (0x100000, for IMX27PDK) redboot> fis create -f 0x100000 kernel Flashing root file system Load root file system image (rootfs.jffs2) to the temporary address. Remember to modify the host IP address: redboot> load -r -b 0x100000 /tftpboot/rootfs.jffs2 -h 10.29.244.99 Create the root file system in the right address (0x600000, for IMX27PDK) redboot> fis create -f 0x600000 root Testing This step can be omitted! You can now load your kernel in the flash by typing: fis load kernel To know if the root file system written in the flash was correctly saved, execute the NFS file system and mount the flash. For load the the root file system by NFS, type: exec -c "noinitrd console=ttymxc0,115200 root=nfs nfsroot= : ip=dhcp" Wait the system go up, then mount the flash at /mnt. Reminde that the flash has a jffs2 file system. mount -t jffs2 /dev/mtdblock4 /mnt ls /mnt List the /mnt contents. The output must be the right file system. For testing root file system on NAND, type exec -c "noinitrd console=ttymxc0,115200 root=/dev/mtdblock4 rw rootfstype=jffs2 ip=dhcp" Modifying the initial script Reset the board and press CTRL-C. Type fc to modify the configurations and insert the initialization script. RedBoot> fc Run script at boot: true Boot script: Enter script, terminate with empty line >> fis load kernel >> exec -c "noinitrd console=ttymxc0,115200 root=/dev/mtdblock4 rw rootfstype=jffs2 ip=dhcp" >> Boot script timeout (1000ms resolution): 1 Use BOOTP for network configuration: false Gateway IP address: 10.29.241.254 Local IP address: 10.29.241.6 Local IP address mask: 255.255.254.0 Default server IP address: 10.29.244.99 Board specifics: 0 Console baud rate: 115200 Set eth0 network hardware address [MAC]: false GDB connection port: 9000 Force console for special debug messages: false Network debug at boot time: false Update RedBoot non-volatile configuration - continue (y/n)? y ... Read from 0x07ee0000-0x07eff000 at 0x00080000: . ... Erase from 0x00080000-0x000a0000: . ... Program from 0x07ee0000-0x07f00000 at 0x00080000: . RedBoot> Remember to save the configuration in the flash by typing y Reset the system. To certify that the board is loading the system from flash, remove the ethernet cable. i.MX2x
查看全文
Adeneo Embeddedは、i.MX53上のLinuxとWEC7のベンチマーク比較をリリース <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 多くのお客様が特定のプラットフォームで次の製品のオペレーティングシステムを選択するのが難しいと感じているため、Adeneo Embeddedは、i.MX53プラットフォーム上のLinuxとWEC7の非常に詳細な比較をまとめました。この比較では、プラットフォームのセットアップ、最初のビルドの作成にかかる時間から、パフォーマンスと消費電力のベンチマークまで、すべてを文書化しています。以下は、ドキュメントの内容のスナップショットです。   完全なドキュメントにアクセスするには、Adeneo Embedded([email protected])にお問い合わせください 全般
查看全文
Adeneo Embedded releases a benchmark comparison of Linux and WEC7 on i.MX53 As many customers find it difficult selecting an Operating system for their next product on a given platform Adeneo Embedded put together a very detailed comparison between Linux and WEC7 on the i.MX53 platform. This comparison documents everything from the time it takes to setup the platform, create the first builds to performance and power consumption benchmarks. Below is a snapshot of the contents of the document.   To get access to the complete document, please contact Adeneo Embedded at [email protected] General
查看全文