Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
NFC ON KW In the process of practical application, customers often need the combination of ble + NFC. At present, our IOT-DK006 is the only development board with NFC module. But the NFC example is not perfect. So we porting the library of NFC reader- PN7150, to support KW series microcomputer so that KW series can handle the demand of ble + NFC function. Now I will introduce you how to port the NFC lib to KW. 1 PN7150 Introduction PN7150 is the high-performance version of PN7120, the plug’n play NFC solution for easy integration into any OS environment, reducing Bill of Material (BOM) size and cost. PN71xx controllers are ideal for home-automation applications such as gateways and work seamlessly with NFC connected tags. 2 Tools hardware:FRDM-KW36,PN7150 , some wire software:mcuxpresso11.3 package:NXP-NCI MCUXpresso example Project This package contains the nfc library and example that we need. We will refer the ‘NXPNCI-K64F_example’ firstly. Sdk version: 2.2.8, Example: frdmkw36_rtos_examples_freertos_i2c  3 Steps Hardware part:We need connect the PN7150 to KW36 like the picture. Although we can connect the PN7150 to board through the ardunio connector, the pin’s voltage is not enough to drive the PN7150. So we need a wire connected to U1 to get 3.3V.   PN7150 FRDM-KW36 VBAT/PVDD 3.3V VANT 5V GND GND IRQ PTA16 VEN PTC15 SCL PTB0,I2C0 SDA PTB1,I2C0 Software part:We should add the nfc library and directory into our project. You can check the following picture to know what file is necessary. If you want to know how to add directory into our project, you can refer this link. The red line shows what file we need. Please notice that when we add file path into the mcuxpresso configuration, we also need add the path into ‘Path and Symbols’ . We need add some macro into ‘Preprocessor’. We copy the NXPNCI-K64F_example’s main file content into our ‘freertos_i2c.c’. Next, we need modify the file pin_mux.c, tml.c and board.h   In file board.h,add the following macro. Don't forget to enable the pin clock. /* NXPNCI NFC related declaration */ #define BOARD_NXPNCI_I2C_INSTANCE I2C0 #define BOARD_NXPNCI_I2C_BAUDRATE (100000) #define BOARD_NXPNCI_I2C_ADDR       (0x28) #define BOARD_NXPNCI_IRQ_PORTIRQn PORTA_IRQn #define BOARD_NXPNCI_IRQ_GPIO     (GPIOA) #define BOARD_NXPNCI_IRQ_PORT     (PORTA) #define BOARD_NXPNCI_IRQ_PIN      (16U) #define BOARD_NXPNCI_VEN_GPIO     (GPIOC) #define BOARD_NXPNCI_VEN_PORT     (PORTC) #define NXPNCI_VEN_PIN            (5U)     In file pin_mux.c, add head file ‘board.h’. Add the following code in function ’ BOARD_InitPins’. The step is to configure the VEN, IRQ and I2C0. This example contains the I2C1’s code, you can comment them.     /* Initialize NXPNCI GPIO pins below */   /* IRQ and VEN PIN_MUX Configuration */   PORT_SetPinMux(BOARD_NXPNCI_IRQ_PORT, BOARD_NXPNCI_IRQ_PIN, kPORT_MuxAsGpio);   PORT_SetPinMux(BOARD_NXPNCI_VEN_PORT, NXPNCI_VEN_PIN, kPORT_MuxAsGpio);   /* IRQ interrupt Configuration */   NVIC_SetPriority(BOARD_NXPNCI_IRQ_PORTIRQn, 6);   EnableIRQ(BOARD_NXPNCI_IRQ_PORTIRQn);   PORT_SetPinInterruptConfig(BOARD_NXPNCI_IRQ_PORT, BOARD_NXPNCI_IRQ_PIN, kPORT_InterruptRisingEdge); Finally, in file tml.c, modify PORTC_IRQHandler as PORTA_IRQHandler We finished all steps. 4 Results We use ntag to test the reading and writing operation. When the tag is closed to the PN7150, we will get the following message. The text recording is ‘VER=03’. Next, we will modify the text recording We need add the new macro to preprocessor. We can modify the variable NDEF_MESSAGE in function task_nfc_reader to modify the text recording. Then we download the program again. We will see the original text ‘VER=03’ and the text has been modified. Then we read the tag again. We will see the new text. If we want to send the larger text, what should we do? We need modify the macro ‘ADD’. When only 4 characters are sent, ‘ADD’ is 0. And every additional character is added, the ‘ADD’ will add. We modify the tag as ‘Ver=03’, and we have two more characters. So ‘ADD’ needs to be defined as 2 It firstly shows the text ‘Test’. Then it will show the new text ‘Ver=03’. Other tags’ reading and writing operation can be enabled by defining some macro.       BLE Software KW
View full article
尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to integrate Processor Expert code to IAR6.7) 最近有客户问到如何移植PE生成的TSI代码到IAR中,按照常规的方法在把头文件和库文件意义一一包含进来,非常繁琐,于是研究了一下相关的操作。在早期的IAR版本中,需要用户自己手动添加芯片名称,链接文件和包含的路径信息,特别是在PE增加或者删除组件后,需要用户去增减相应的文件,更增加了难度。而在最新版本的 IAR 6.7中集成了对PE工程的链接机制,它可以方便的读取PE工程的XML文件,从而实现移植PE生成的代码到 IAR Embedded Workbench中,相对于早期的IAR版本,主要完成以下几个工作: 自动检测使用的芯片类型; 自动添加PE的LCF连接配置文件; 自动更新包含的头文件路径; PE增加或者删除Component组件后,IAR工程会自动Add 或Delete 相应的组件代码; 尽管IAR完成了一些繁琐的工作,但网上没有太多的资源可以参考,对于首次使用的用户来说还是需要一些探索,为节省大家的时间,下面以一个具体的示例Step By Step的介绍如何在IAR中集成PE的工程。 1. 打开Processor Expert software 新建一个PE的工程并保存生成代码,这个过程比较简单,此处不再赘述,重点讲述一下在IAR中的使用步骤; 2. 在IAR Workbench中"Creat New Project"新建一个空的工程。 3. 保存新建的工程文件到PE工程的文件夹中,需要注意的是此处也可以选择其他路径,但为简便和易维护性上还是建议直接存放到PE工程中。 4. 打开Tools->Options->Project选项,勾选“Enable project connects”,这个选项的目的在于使能 IAR 能够读取Freescale Processor Expert和Infineon DAVE等第三方工具生成.XML文件。 5. 添加PE工程的XML文件,选择Project->Add Project Connection,会弹出链接选择对话框,选择使用Freescale Processor Expert,默认是IAR Project Connection; 6. 点击OK后,选择建立PE工程时生成的工程描述符文件Projectinfo.xml; 7. 完成上面步骤后,在IAR中自动完成以下三方面工作:自动加载PE生成的文件到IAR中,自动安装LCF链接配置文件,自动包含头文件路径。这几个步骤在之前版本的IAR中需要自己手动添加,并且当在PE中重新生成Code时需要重新添加对应的文件; 8. 完成上面步骤之后,需要根据实际情况配置采用的下载/调试器,Project->Options->Debugger->Setup 选择下载Driver,实验中使用的是KL25的FRDM板,所以在PE Macro中选择OpenSDA,点击OK,完成设置; 9. 编译工程,下载Debug; 总结下来,主要完成两个工作:(1)配置使能 Project connection,并导入PE生成的XML文件; (2)配置调试的下载器仿真器; Re: 尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to Integration Processor Expert code to IAR6.7) <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 问题可以在下面回复: 当您在“Libraries(-l)”中添加一个库时,gcc 链接器知道这是一个 gcc 库,因此无需添加“lib”前缀和“.a”后缀。 但是当您在“杂项”中添加库时,如果文件没有“lib”前缀和“.a”后缀,gcc 链接器就不会认为它是 gcc 库。 Re: 尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to integrate Processor Expert code to IAR6.7) 我看了一下.xml配置文件,上面显示的库的路径是在工程文件夹下面的,实际上在Open Containing Folder命令中打开的路径也是工程所在的路径,但是并不是库的路径,是他的上级路径,应该是他没有识别到。 你说的那个选项我勾选了(atuo runtime library selection),仍然不行,但是我在选项下面的Additional libraries 中添加了库的路径之后就可以了。 第二个方法就是上面我说的方法,取消链接之后自己添加一遍库,我注意到自动添加的库是带引号的,自己添加的不带引号,不知道这意味着什么。。 下面是XML的路径片段,路径中没有中文     D:\PE_K60\TEST1.0\Project_Settings\Linker_Files\ProcessorExpert.icf           D:\PE_K60\TEST1.0\Sources\TSS\       C:\Freescale\PExDrv v10.3\eclipse\ProcessorExpert\lib\Kinetis\iofiles\       C:\Freescale\PExDrv v10.3\eclipse\ProcessorExpert\lib\Kinetis\pdd\inc\       D:\PE_K60\TEST1.0\Sources\       D:\PE_K60\TEST1.0\Generated_Code\               D:\PE_K60\TEST1.0\Generated_Code\       D:\PE_K60\TEST1.0\Sources\       D:\PE_K60\TEST1.0\Sources\TSS\               D:\PE_K60\TEST1.0\Sources\TSS\       Re: 尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to integrate Processor Expert code to IAR6.7) 你要查看一下PathName 的路径了,因为默认的路径应该是在TSS的安装目录中,另外在IAR中Linker配置项的library选项配置也需要check一下,需要使能atuo runtime library selection。 Re: 尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to integrate Processor Expert code to IAR6.7) 您好! 我按照你的文章使用PE建立了一个关于TSS库的工程,使用IAR编译文件时出现了错误: Error[Li005]: no definition for "TSS_Init" [referenced from D:\PE_K60\test1\Debug\Obj\TSS1.o] Error[Li005]: no definition for "TSS_SetKeypadConfig" [referenced from D:\PE_K60\test1\Debug\Obj\TSS1.o] Error[Li005]: no definition for "TSS_SetSystemConfig" [referenced from D:\PE_K60\test1\Debug\Obj\TSS1.o] Error[Li005]: no definition for "TSS_GetSystemConfig" [referenced from D:\PE_K60\test1\Debug\Obj\TSS_SensorTSI.o] Error while running Linker 我找到错误的原因是:在 文件中       "TSS_KXX_M4.a"     上述路径在IAR中识别为无效路径,导致库中的函数无法引用, 我在IAR加载文件之后,在你说的地4步《打开Tools->Options->Project选项,勾选“Enable project connects” 》中取消了工程链接,删除了IAR工程中包含的TSS_KXX_M4.a文件,然后重新加载了这个文件,这时候编译通过了。 请问这个应该怎么做呢。 我使用的是IAR6.7.1,PE10.3 Re: 尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to Integration Processor Expert code to IAR6.7) <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 好文档,对我很有用!谢谢!
View full article
MCX Lab MCX Lab: Empowering University Innovation with NXP FRDM-MCXN947 What is MCX Lab? MCX Lab is an NXP initiative designed to foster collaboration with universities, providing students and educators with cutting-edge hardware, software, and educational resources. The program centers around the powerful NXP FRDM-MCXN947 development board, enabling hands-on learning and advanced research in embedded systems, AI/ML, IoT, and more. Key Features of the MCX Lab Program 1. FRDM-MCXN947 Comprehensive Hardware Platform MCXN947 MCU: Dual Arm® Cortex®-M33 cores @150MHz, up to 2MB dual-bank flash, Neural Processing Unit, PowerQuad, Smart DMA, and more. Rich Peripherals: User LEDs, buttons, accelerometer, temperature sensor, touch pad, Ethernet, USB Type-C, CAN-FD, WiFi, and extensive expansion options (Arduino®, FRDM, mikroBUS™, Pmod™, FlexIO/LCD, SmartDMA/Camera headers). Custom Shields: NXP-designed shields for introductory labs, featuring buttons, joystick, DIP switch, rotary encoder, LED ring, potentiometer, IR sensors, OLED display, and more. See MCX Lab Expansion Boards page for more. Add-on Modules: Wide portfolio of sensors, actuators, interfaces, displays, and wireless modules. Explore the Expansion Board Hub for more options. 2. Powerful Software Ecosystem Development IDEs and Build Tools: MCUXpresso IDE MCUXpresso for Visual Studio Code Third-party toolchains from Arm, IAR, Keil Examples and Quick Start Software: MCUXpresso SDK Debugging and Visualization Tools: LinkServer FreeMASTER Software Development Resources: MCUXpresso Config Tools Secure Provisioning Tool Secure Provisioning SDK (SPSDK) Device HSM Trust Provisioning RTOS: Zephyr™ OS AI Software Development: eIQ Toolkit HMI Design Software: GUI Guider Connectivity Software NXP Platform Accelerator 3. Educational Materials Lecture & Lab Content: Tailored for all levels—introductory (embedded basics), medium (GPIO, ADC, timers, serial comms), and advanced (Zephyr, AI/ML, UI/UX). See MCX Lab Educational Materials page for more. Invited Lectures: On-demand sessions by NXP engineers at partner universities. Documentation: Reference manuals, datasheets, getting started guides, application notes, and access to the MCUXpresso Training Hub. 4. Application Examples Application Code Hub: Application software packs, demo apps, code snippets, and integration with GitHub and VS Code for easy access and collaboration. Diverse Domains: AI/ML, audio, graphics, low power, motor control, power conversion, safety, security, networking, touch sensing, vision, voice, wireless connectivity, and more.
View full article
The RT speech recognition system based on VIT to obtain weather information 1.  Abstract NXP EdgeReady solution can use RT106/5 S/L/A/F to achieve speech recognition, but the relevant support software libraries for the RT4-bit series are limited to the S/L/A/F series, if you want to use normal RT chips, how to achieve speech recognition functions? NXP officially launched the VIT software package in the SDK, which can support RT1060, RT1160, RT1170, RT600, RT500 to achieve SDK-based speech recognition functions. For the acquisition of weather information, usually customer can connect with a third-party platform or the cloud weather API, using http client method to access directly, the current weather API platforms, you can register it, then call the API directly, so you can use the RT SDK lwip socket client method to call the corresponding weather API, to achieve real-time specific geographical location weather forecast data.     This article will use MIMXRT1060-EVK to implement customer-defined wake-up word(WW) and voice recognition word recognition(VC) based on SDK VIT lib, and LWIP socket client to achieve real-time weather information acquisition in Shanghai, then print it to the terminal, this article mainly use the print to share the weather information, for the sound broadcasts, it also add the simple method to broadcast the fixed sound with mp3 audio data, but for the freely sound broadcast, it may need to use real-time TTS function, which is not added now.     The system block diagram of this document is as follows:   Fig 1 System Block diagram The VIT custom wake-up word of this system is "小恩小恩", and after waking up, one of the following recognition words can be recognized: ”开灯”("Turn on the lights"),“关灯”("Turn off the lights"),”今天天气”("Today's weather"),“明天天气”("Tomorrow's Weather"),“后天天气”("The day after tomorrow's weather"). Turn on the light or Turn off the lights , that is to control  the external LED red light on the EVK board. ”今天天气” gets today’s weather forecast, it is in the following format:                     "date": "2022-05-27",                     "week": "5",                     "dayweather": "阴",                     "nightweather": "阴",                     "daytemp": "28",                     "nighttemp": "21",                     "daywind": "东南",                     "nightwind": "东南",                     "daypower": "≤3",                     "nightpower": "≤3" “明天天气”,“后天天气” are the same format, but it is 1-2 days after the date of today. To get the weather data, the MIMXRT1060-EVK board needs to connect the network to achieve the acquisition of the Gaode Map(restapi.amap.com) Weather API data. 2.  Related preparations 2.1 Weather API Platform     At present, there are many third-party platforms that can obtain weather on the Internet for Chinese, such as: Baidu Intelligent Cloud, Baidu Map API, Huawei cloud platform, Juhe weather, Gaode Map API, and so on. This article tried several platform, the test results found: Baidu intelligent cloud, the number of daily free calls is small, the need for real-time synthesis of AK, SK, cumbersome to call; Baidu Map API needs to upload ID card information; Several others have a similar situation. In the end, the Gaode Map API with convenient registration, many daily calls and relatively full feedback weather data information was selected.     Here, we mainly talk about the Gaode Map API usage, the link is: https://lbs.amap.com/api/webservice/guide/api/weatherinfo Create the account and the API key, then add the relevant parameters to implement the call of the weather API, the application for API Key is as follows: Fig 2 Gaode map API key The following diagram shows the call volume:   Fig 3 Gaode Map API call volume This is the API calling format:   Fig 4 Weather API calling parameters So, the full Gaode Map API link should like this: https://restapi.amap.com/v3/weather/weatherInfo?key=xxxxxxx&city=xxx&extensions=all&output=JSON If need to test the Shanghai weather, city code is 310000. 2.2 Postman test weather API     Postman is an interface testing tool, when doing interface testing, Postman is equivalent to a client, it can simulate various HTTP requests initiated by users, send the request data to the server, obtain the corresponding response results, and verify whether the result data in the response matches the expected value. Postman download link: https://www.postman.com/   After finding the proper weather API platform and the calling link, use the postman do the http GET operation to capture the weather data, refer to the Fig 4, fill the related parameters to the postman: Fig 5 Postman call weather API Send Get command, we can find the weather information in the position 7, the complete all information is: {     "status": "1",     "count": "1",     "info": "OK",     "infocode": "10000",     "forecasts": [         {             "city": "上海市",             "adcode": "310000",             "province": "上海",             "reporttime": "2022-05-27 17:34:12",             "casts": [                 {                     "date": "2022-05-27",                     "week": "5",                     "dayweather": "阴",                     "nightweather": "阴",                     "daytemp": "28",                     "nighttemp": "21",                     "daywind": "东南",                     "nightwind": "东南",                     "daypower": "≤3",                     "nightpower": "≤3"                 },                 {                     "date": "2022-05-28",                     "week": "6",                     "dayweather": "小雨",                     "nightweather": "中雨",                     "daytemp": "24",                     "nighttemp": "20",                     "daywind": "东南",                     "nightwind": "东南",                     "daypower": "≤3",                     "nightpower": "≤3"                 },                 {                     "date": "2022-05-29",                     "week": "7",                     "dayweather": "大雨",                     "nightweather": "小雨",                     "daytemp": "23",                     "nighttemp": "20",                     "daywind": "南",                     "nightwind": "南",                     "daypower": "≤3",                     "nightpower": "≤3"                 },                 {                     "date": "2022-05-30",                     "week": "1",                     "dayweather": "小雨",                     "nightweather": "晴",                     "daytemp": "27",                     "nighttemp": "20",                     "daywind": "北",                     "nightwind": "北",                     "daypower": "≤3",                     "nightpower": "≤3"                 }             ]         }     ] } We can see, it can capture the continuous 4 days information, with this information, we can get the weather information easily. From the postman, we also can see the Get code, like this: Fig 6 postman API HTTP code     With this API which already passed the testing, it can capture the complete weather information, here, we can consider adding the working http API to the MIMXRT1060-EVK code.    2.3 VIT custom commands     From the maestro code of the RT1060 SDK, we can know that the SDK already supports the VIT library, what is VIT?     VIT's full name: Voice Intelligent Technology, the library provides voice recognition services designed to wake up and recognize specific commands, control IOT, and the smart home. Fig 7 VIT system block diagram     In NXP RT1060 SDK code, the generated wake word and command word have been provided and placed in the VIT_Model.h file. If in the customer's project, how to customize the wake word and command word? With the NXP's efforts, we have made a web page form for customers to choose their own command, and then generate the corresponding VIT_Model.h file for code to call. VIT command word generation web page is: https://vit.nxp.com/#/home     Login the NXP account, choose the RT chip partn umber, wakeup word, voice command. Please note, the current supported RT chip is: RT1060,RT1160,RT1170,RT600,RT500 The following is the example for generating wakeup word and voice command:   Fig 8 Custom VIT configuration Fig 9 generated result Download the generated model, you can get VIT_Model_cn.h, open to see the command word information and related model data stored in the const PL_MEM_ALIGN (PL_UINT8 VIT_Model_cn[], VIT_MODEL_ALIGN_BYTES) array, the command word information is as follows: WakeWord supported : " 小恩 小恩 " Voice Commands supported     Cmd_Id : Cmd_Name       0    : UNKNOWN       1    : 开灯       2    : 关灯       3    : 今天 天气       4    : 明天 天气       5    : 后天 天气 Use the RT1060 SDK maestro_record demo to test this custom command result:   Fig 10 Custom Wakeup word and voice command test From the test result, we can see, both the wakeup word and voice command is detected. 3 Software code 3.1 LWIP socket client code capture weather API From chapter 2.2, we have been able to obtain the weather API and through testing, we can successfully achieve weather acquisition, so we need to add relevant commands in combination with the needs of our own system. For the acquisition of the weather API, the lwip code based on the RT1060 SDK is in the form of socket client. The relevant code is as follows: #define PORT 80 #define IP_ADDR "59.82.9.133" uint8_t get_weather[]= "GET /v3/weather/weatherInfo?key=xxx&city=310000&extensions=all&output=JSON HTTP/1.1\r\nHost: restapi.amap.com\r\n\r\n\r\n\r\n"; if (sys_thread_new("weather_main", weathermain_thread, NULL, HTTPD_STACKSIZE, HTTPD_PRIORITY) == NULL) LWIP_ASSERT("main(): Task creation failed.", 0); static void weathermain_thread(void *arg) { static struct netif netif; ip4_addr_t netif_ipaddr, netif_netmask, netif_gw; ethernetif_config_t enet_config = { .phyHandle = &phyHandle, .macAddress = configMAC_ADDR, }; LWIP_UNUSED_ARG(arg); mdioHandle.resource.csrClock_Hz = EXAMPLE_CLOCK_FREQ; IP4_ADDR(&netif_ipaddr, configIP_ADDR0, configIP_ADDR1, configIP_ADDR2, configIP_ADDR3); IP4_ADDR(&netif_netmask, configNET_MASK0, configNET_MASK1, configNET_MASK2, configNET_MASK3); IP4_ADDR(&netif_gw, configGW_ADDR0, configGW_ADDR1, configGW_ADDR2, configGW_ADDR3); tcpip_init(NULL, NULL); netifapi_netif_add(&netif, &netif_ipaddr, &netif_netmask, &netif_gw, &enet_config, EXAMPLE_NETIF_INIT_FN, tcpip_input); netifapi_netif_set_default(&netif); netifapi_netif_set_up(&netif); PRINTF("\r\n************************************************\r\n"); PRINTF(" TCP client example\r\n"); PRINTF("************************************************\r\n"); PRINTF(" IPv4 Address : %u.%u.%u.%u\r\n", ((u8_t *)&netif_ipaddr)[0], ((u8_t *)&netif_ipaddr)[1], ((u8_t *)&netif_ipaddr)[2], ((u8_t *)&netif_ipaddr)[3]); PRINTF(" IPv4 Subnet mask : %u.%u.%u.%u\r\n", ((u8_t *)&netif_netmask)[0], ((u8_t *)&netif_netmask)[1], ((u8_t *)&netif_netmask)[2], ((u8_t *)&netif_netmask)[3]); PRINTF(" IPv4 Gateway : %u.%u.%u.%u\r\n", ((u8_t *)&netif_gw)[0], ((u8_t *)&netif_gw)[1], ((u8_t *)&netif_gw)[2], ((u8_t *)&netif_gw)[3]); PRINTF("************************************************\r\n"); sys_thread_new("weather", weather_thread, NULL, DEFAULT_THREAD_STACKSIZE, DEFAULT_THREAD_PRIO); vTaskDelete(NULL); } static void weather_thread(void *arg) { int sock = -1,rece; struct sockaddr_in client_addr; char* host_ip; ip4_addr_t dns_ip; err_t err; uint32_t *pSDRAM= pvPortMalloc(BUF_LEN);// host_ip = HOST_NAME; PRINTF("host name : %s , host_ip : %s\r\n",HOST_NAME,host_ip); while(1) { sock = socket(AF_INET, SOCK_STREAM, 0); if (sock < 0) { PRINTF("Socket error\n"); vTaskDelay(10); continue; } client_addr.sin_family = AF_INET; client_addr.sin_port = htons(PORT); client_addr.sin_addr.s_addr = inet_addr(host_ip); memset(&(client_addr.sin_zero), 0, sizeof(client_addr.sin_zero)); if (connect(sock, (struct sockaddr *)&client_addr, sizeof(struct sockaddr)) == -1) { PRINTF("Connect failed!\n"); closesocket(sock); vTaskDelay(10); continue; } PRINTF("Connect to server successful!\r\n"); write(sock,get_weather,sizeof(get_weather)); while (1) { rece = recv(sock, (uint8_t*)pSDRAM, BUF_LEN, 0);//BUF_LEN if (rece <= 0) break; memcpy(weather_data.weather_info, pSDRAM,1500);//max 1457 } Weather_process(); memset(pSDRAM,0,BUF_LEN); closesocket(sock); vTaskDelay(10000); } }  3.2 VIT detect customer command code    Put the generated VIT_Model_cn.h to the maestro_record folder path:   vit\RT1060_CortexM7\Lib    The specific wake word and voice command related code can be viewed from the code vit_pro.c, mainly involving function is: int VIT_Execute(void *arg, void *inputBuffer, int size) The code is modified as follows, mainly to record the wake and wake word number, for specific function control, the command directly controlled here is the local "开灯:turn on the light", "关灯:turn off the light" command, as for the weather command needs to call the socket client API, so in the main lwip call area combined with the command word recognition number to call: if (VIT_DetectionResults == VIT_WW_DETECTED) { PRINTF(" - WakeWord detected \r\n"); weather_data.ww_flag = 1; //kerry } else if (VIT_DetectionResults == VIT_VC_DETECTED) { // Retrieve id of the Voice Command detected // String of the Command can also be retrieved (when WW and CMDs strings are integrated in Model) VIT_Status = VIT_GetVoiceCommandFound(VITHandle, &VoiceCommand); if (VIT_Status != VIT_SUCCESS) { PRINTF("VIT_GetVoiceCommandFound error: %d\r\n", VIT_Status); return VIT_Status; // will stop processing VIT and go directly to MEM free } else { PRINTF(" - Voice Command detected %d", VoiceCommand.Cmd_Id); weather_data.vc_index = VoiceCommand.Cmd_Id;//kerry 1:ledon 2:ledoff 3:today weather 4:tomorrow weather 5:aftertomorrow weather if(weather_data.vc_index == 1)//1 { GPIO_PinWrite(GPIO1, 3, 1U); //pull high PRINTF(" led on!\r\n"); } else if(weather_data.vc_index == 2)//2 { GPIO_PinWrite(GPIO1, 3, 0U); //pull low PRINTF(" led off!\r\n"); } // Retrieve CMD Name: OPTIONAL // Check first if CMD string is present if (VoiceCommand.pCmd_Name != PL_NULL) { PRINTF(" %s\r\n", VoiceCommand.pCmd_Name); } else { PRINTF("\r\n"); } } }  3.3 Voice recognize weather information    In the weather_thread while, check the wakeup word and voice command, if meet the requirement, then create the socket connection, write the API and capture the weather data.   The related code is: while(1) { //add the command request, only cmd == weather flag, then call it. if((weather_data.ww_flag == 1)) { if(weather_data.vc_index >= 3) { // create connection //write API and read API Weather_process(); } memset(weather_data.weather_info, 0, sizeof(weather_data.weather_info)); weather_data.ww_flag = 0; weather_data.vc_index = 0; } vTaskDelay(10000); } void Weather_process(void) { char * datap, *datap1; datap = strstr((char*)weather_data.weather_info,"date"); if(datap != NULL) { memcpy(today_weather, datap,184);//max 1457 if(weather_data.vc_index == 3) { PRINTF("\r\n*******************today weather***********************************\n\r"); PRINTF("%s\r\n",today_weather); return; } } else return; datap1 = strstr(datap+4,"date"); if(datap1 != NULL) { memcpy(tomorr_weather, datap1,184);//max 1457 if(weather_data.vc_index == 4) { PRINTF("\r\n*******************tomorrow weather*******************************\n\r"); PRINTF("%s\r\n",tomorr_weather); return; } } else return; datap = strstr(datap1+4,"date"); if(datap != NULL) { memcpy(aftertom_weather, datap,184);//max 1457 if(weather_data.vc_index == 5) { PRINTF("\r\n*******************after tomorrow weather**************************\n\r"); PRINTF("%s\r\n",aftertom_weather); } } else return; }   Function Weather_process is used to refer to the voice recognized weather number to get the related date’s weather, and printf it. 4 Test result  the test result video: (view in My Videos) Print the log results as shown in Figure 11, after testing, you can see that the wakeup word and voice command can be successfully recognized, in the recognition of word sequence numbers 3, 4, 5 is the weather acquisition, you can successfully call the lwip socket client API, successfully obtain weather information and printf it.   Fig 11 system test print result  evkmimxrt1060_maestro_weather_backup.zip is the project without sound playback, weather information will print to the terminal! 5 Meet issues conclusion 5.1 LWIP failed to get weather    When creating the code, call the postman provided http code: GET /v3/weather/weatherInfo?key=8f777fc7d867908eebbad7f96a13af10& city=310000& extensions=all& output=JSON HTTP/1.1 Host: restapi.amap.com    Add it to the socket API function: uint8_t get_weather[]= "GET /v3/weather/weatherInfo?key=xxx&city=310000&extensions=all&output=JSON HTTP/1.1\r\nHost: restapi.amap.com\r\n\r\n\r\n\r\n";    The test result is:   Fig 12 socket weather API return issues     We can see, server connection is OK, http also return back the data, but it report the parameter issues, after checking, we use the postman C code, and put it to the get_weather: uint8_t get_weather[]= "GET /v3/weather/weatherInfo?key=xxx&city=310000&extensions=all&output=JSON HTTP/1.1\r\nHost: restapi.amap.com\r\n\r\n\r\n\r\n"; Then, it can capture the weather data, the same as postman test result. 5.2 VIT LWIP merger memory is not enough     After combining the maestro_record and lwip socket code together, compile it, it will meet the DTCM memory overflow issues. Fig 13 memory overflow After optimize, still meet the DTCM overflow issues, so, at last, choose to reconfigure the FlexRAM: OCRAM 192K, DTCM 256K, ITCM 64K Compile it, and the memory overflow issues disappear:   Fig 14 FlexRAM recofiguration 5.3 Print Chinese word in tera    Directly use teraterm, when the weather API returns the Chinese word, the print out information is the garbled code, and then after the following configuration, to achieve Chinese printing: Setup  ->  Terminal Locale    : american->chinese Codepage : 65001 ->936 Fig 15 Tera Term Chinese word print In summary, after various data collection and problem solving, in MIMXRT1060-EVK board  combined with the official SDK complete the function of customizing VIT voice commands to obtain real-time weather and local control.So, even if the ordinary RT series which is not S/L/A/F series, you also can use VIT to implement speech recognition functions. 6 Add the sound broadcast    This chapter mainly gives the method how to add the sound broadcast with the mp3 video data which is stored in the memory, but to the realtime weather data playback, it is not very freely, it needs to check the weather data, and use the video mp3 data lib get the correct mp3 data, as it is not the online TTS method.     So, here, just share one example add the sound broadcast, eg: WW : “小恩小恩”    ->   “小恩来了,请吩咐!” VC  :“今天天气”   ->   “温度32.1度” VC playback is fixed now, if need to play real data, it needs to generate the mp3 voice data lib, then according to the feedback weather information, to generate the correct weather mp3 data array, and play it, as this is a little complicated, but not difficult, so here, just use one fixed sound give an example of it. 6.1 MP3 playback audio data preparation     For audio broadcasting which need to convert the Chinese word into MP3 files, you can use some online speech synthesis software, here use Baidu online speech synthesis function, you can view the previous article, chapter 2.2.2 online speech synthesis: https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/RT106L-S-voice-control-system-based-on-the-Baidu-cloud/ta-p/1363295     If use the Baidu online speech synthesis generated mp3 file to convert to the c array directly, it will meet the first audio play issues, so, here we use the Audacity to convert the mp3 file, the convert configuration is like this:  Fig 16 Audacity convert configuration     After the regeneration of mp3, you can use xxd .exe to convert the mp3 file to an array of C files, and then put it into RT-related memory or external flash , xxd .exe can be found at the following link: https://github.com/baldram/ESP_VS1053_Library/issues/18 The convert command like this: xxd -i your-sound.mp3 ready-to-use-header.c Convert the xiaoencoming.mp3 and temptest.mp3 file to the C array, then modify the data to the C file, save file as: xiaoencoming.h and temptest.h. Here, take xiaoencoming.c as an example: #define XIAOEN_MP3_SIZE  6847 unsigned char xiaoencoming_mp3[XIAOEN_MP3_SIZE] = {   0x49, 0x44, 0x33, 0x03, 0x00, 0x00, 0x00, 0x00, 0x00, 0x21, 0x54, 0x58, …   0x55, 0x55, 0x55, 0x55, 0x55, 0x55, 0x55 }; unsigned int xiaoencoming1_mp3_len = XIAOEN_MP3_SIZE;//6847; Until now, the playback audio data is finished.     Copy xiaoencoming.h and temptest.h to project path: evkmimxrt1060_maestro_weather_mp3\source 6.2 Play the MP3 data from memory    Here, share the related code. 6.2.1 app_streamer.c added code    #include "xiaoencoming.h" #include "temptest.h" void *voice_inBuf = NULL; void *voice_outBuf = NULL; status_t STREAMER_file_Create(streamer_handle_t *handle, char *filename, int eap_par) { STREAMER_CREATE_PARAM params; OsaThreadAttr thread_attr; int ret; ELEMENT_PROPERTY_T prop; MEMSRC_SET_BUFFER_T inBufInfo = {0}; SET_BUFFER_DESC_T outBufInfo = {0}; PRINTF("Kerry test begin!\r\n"); if(filename == "temptest.mp3") inBufInfo = (MEMSRC_SET_BUFFER_T){.location = (int8_t *)temptest_mp3, .size = TEMPtest_MP3_SIZE}; else if(filename == "xiaoencoming.mp3") inBufInfo = (MEMSRC_SET_BUFFER_T){.location = (int8_t *)xiaoencoming_mp3, .size = XIAOEN_MP3_SIZE}; /* Create message process thread */ osa_thread_attr_init(&thread_attr); osa_thread_attr_set_name(&thread_attr, STREAMER_MESSAGE_TASK_NAME); osa_thread_attr_set_stack_size(&thread_attr, STREAMER_MESSAGE_TASK_STACK_SIZE); ret = osa_thread_create(&msg_thread, &thread_attr, STREAMER_MessageTask, (void *)handle); osa_thread_attr_destroy(&thread_attr); if (ERRCODE_NO_ERROR != ret) { return kStatus_Fail; } /* Create streamer */ strcpy(params.out_mq_name, APP_STREAMER_MSG_QUEUE); params.stack_size = STREAMER_TASK_STACK_SIZE; params.pipeline_type = STREAM_PIPELINE_MEM; params.task_name = STREAMER_TASK_NAME; params.in_dev_name = "buffer"; params.out_dev_name = "speaker"; handle->streamer = streamer_create(&params); if (!handle->streamer) { return kStatus_Fail; } prop.prop = PROP_DECODER_DECODER_TYPE; prop.val = (uintptr_t)DECODER_TYPE_MP3; ret = streamer_set_property(handle->streamer, prop, true); if (ret != STREAM_OK) { streamer_destroy(handle->streamer); handle->streamer = NULL; return kStatus_Fail; } prop.prop = PROP_MEMSRC_SET_BUFF; prop.val = (uintptr_t)&inBufInfo; ret = streamer_set_property(handle->streamer, prop, true); if (ret != STREAM_OK) { streamer_destroy(handle->streamer); handle->streamer = NULL; return kStatus_Fail; } handle->audioPlaying = false; error: PRINTF("End STREAMER_file_Create\r\n"); PRINTF("Kerry test end!\r\n"); return kStatus_Success; } The code implements the thread build, creates a streamer, defines it as playing from memory, decodes the properties for MP3, and specifies an array of MP3 files in memory. Specify a different array of mp3 files in memory based on the calling file name. 6.2.2 cmd.c added code void play_file(char *filename, int eap_par) { STREAMER_Init(); int ret = STREAMER_file_Create(&streamerHandle, filename, eap_par); if (ret != kStatus_Success) { PRINTF("STREAMER_file_Create failed\r\n"); goto file_error; } STREAMER_Start(&streamerHandle); PRINTF("Starting playback\r\n"); file_playing = true; while (streamerHandle.audioPlaying) { osa_time_delay(100); } file_playing = false; file_error: PRINTF("[play_file] Cleanup\r\n"); STREAMER_Destroy(&streamerHandle); osa_time_delay(100); } Play file, it calls the STREAMER_file_Create API function, start play, and wait the play finished, then release the STREAMER. shellRecMIC API function add the VIT recorded flag, which is used to play feedback audio file. static shell_status_t shellRecMIC(shell_handle_t shellHandle, int32_t argc, char **argv) { … //kerry PRINTF("Kerry MP3 stream data test!\r\n"); PRINTF("---weather_data.ww_flag =%d--\r\n ", weather_data.ww_flag); PRINTF("---weather_data.vc_inde =%d--\r\n ", weather_data.vc_index); PRINTF("---weather_data.mp3_flag =%d--\r\n ", weather_data.mp3_flag); if(weather_data.ww_flag == 1) { play_file("xiaoencoming.mp3", 0); } if(weather_data.vc_index == 3) { play_file("temptest.mp3", 0); } if(weather_data.mp3_flag != 0) { weather_data.ww_flag = 0; weather_data.vc_index = 0; } weather_data.mp3_flag = 0; /* Delay for cleanup */ osa_time_delay(100); return kStatus_SHELL_Success; } If detect the Wakeup Word: “小恩小恩”, play feedback audio: “小恩来了请吩咐”. If detect the voice command: “今天天气”, play feedback audio: “温度32.1度”, please note, this playback just an example, it is the fixed audio, you also can create audio word lib, then according to the received weather information, combine the related word audio together, then playback it. This is a little complicated, but not difficult. So, if need to play the free audio, also can consider the online TTS method in real time. 6.2.3 VIT WW and VC flag VIT_Execute function int VIT_Execute(void *arg, void *inputBuffer, int size) { … if (VIT_DetectionResults == VIT_WW_DETECTED) { PRINTF(" - WakeWord detected \r\n"); weather_data.ww_flag = 1; //kerry weather_data.mp3_flag = 1; } else if (VIT_DetectionResults == VIT_VC_DETECTED) { // Retrieve id of the Voice Command detected // String of the Command can also be retrieved (when WW and CMDs strings are integrated in Model) VIT_Status = VIT_GetVoiceCommandFound(VITHandle, &VoiceCommand); if (VIT_Status != VIT_SUCCESS) { PRINTF("VIT_GetVoiceCommandFound error: %d\r\n", VIT_Status); return VIT_Status; // will stop processing VIT and go directly to MEM free } else { PRINTF(" - Voice Command detected %d", VoiceCommand.Cmd_Id); weather_data.vc_index = VoiceCommand.Cmd_Id;//kerry 1:ledon 2:ledoff 3:today weather 4:tomorrow weather 5:aftertomorrow weather weather_data.mp3_flag = 2; if(weather_data.vc_index == 1)//1 { GPIO_PinWrite(GPIO1, 3, 1U); //pull high PRINTF(" led on!\r\n"); } else if(weather_data.vc_index == 2)//2 { GPIO_PinWrite(GPIO1, 3, 0U); //pull low PRINTF(" led off!\r\n"); } // Retrieve CMD Name: OPTIONAL // Check first if CMD string is present if (VoiceCommand.pCmd_Name != PL_NULL) { PRINTF(" %s\r\n", VoiceCommand.pCmd_Name); } else { PRINTF("\r\n"); } } } return VIT_Status; } Until now, all the code is added. 6.2.4  playback audio test result     This is the audio playback test result: (view in My Videos)   Fig 17 playback audio log   From the test result, we can see, we also can use the mp3 data which is stored in the memory and play it as audio playback.   The code project is: evkmimxrt1060_maestro_weather_mp3.zip. i.MXRT 106x
View full article
S32K混音器 大家好, 最近,我们完成了S32K Sound Mixer的参考代码和演示,很高兴在这里分享这个演示。 此演示的一些主要特点: - 基于 S32K344/S32K148 + 音频编解码器 SGTL5000 + QSPI 闪存 MX25L6433 的演示硬件。 - 基于 S32K3 RTD RTM 2.0.0 和 S32K1 RTD RTM 1.0.0 的演示软件。 - Demo中提供了2种混音算法的实现代码,以及相应的音频素材和codec SGTL5000驱动。 - 演示展示了如何通过音频存储和播放过程对 QSPI 闪存及其 AHB 访问进行编程。 - 演示使用单声道音频作为处理源,并通过 SAI HW FIFO 组合(Line_Mux)功能输出立体声音频(I2S 格式),几乎没有额外成本。 HMI/Cluster 应用程序需要同时播放多个音频源(通常是警告声音),这就带来了混音能力的要求。但是,S32K1/3 缺乏此 HW/SW 功能支持。 结合本地重点客户的需求,并考虑到潜在客户的需求,我们计划启用一个带有预定外设的SW混音器,以增强S32K系列音频混音能力。在 S32K1/3 上使用/移植应该很容易,并使用 QSPI 闪存(AHB 模式读取)来存储音乐。 附件混音器包包括基于 S32K344 EVB 和 S32K148 T-Box RDB 的 2 个混音示例,以及一些介绍此实现和快速入门指南的幻灯片。 谢谢并欢迎您的任何评论。 顺祝商祺! 李帅林 回复: S32K 混音器 你好,S32K3 RTD RTM2.0的下载连接在哪里?我安装的S32K3 RTD 4.4无法打开项目
View full article
将 USB 摄像头与 GStreamer 结合使用 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如果您想在 i.MX6 设备(Linux 内核版本 >= 3.035)上将 USB 摄像头(这些类型的摄像头也称为“网络摄像头”)与 GStreamer 一起使用,您需要动态加载模块或静态编译和链接,并在内核配置中选择(Y)以下配置 设备驱动程序 -> 多媒体支持 -> 视频捕获适配器 -> V4L USB 设备 -> <*> USB 视频类 (UVC) 内核映像构建完成后,将其刷入目标,插入网络摄像头,然后在(目标)终端上运行 gst-启动 v4l2src!mfw_v4lsink 您应该在显示屏上看到相机捕捉到的内容。如果需要对相机源数据进行编码,则需要将编码器放入管道中 gst-launch v4l2src num-buffers=100 !队列!vpuenc编解码器=0!matroskamux!文件接收器位置=输出.mkv 同步=false 我们正在使用某种编解码器(codec=0 表示 mpeg4),使用“gst-inspect vpuenc”检查选项。 i.MX6_全部 多媒体 回复:使用带有 GStreamer 的 USB 摄像头 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 请修复链接!我看不到 最良好的问候! 回复:使用带有 GStreamer 的 USB 摄像头 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 感谢分享,但当编码“无法协商格式”时,这不适用于我的 2 个符合 UVC 1.1 标准的相机。 vpuenc 需要 TNVP、NV12 或 I420 中的原始 uyv,我可以强制原始输出,但我的相机不支持这些(对文件进行测试给出了 YUY2)。可以使用软件中的颜色转换来完成这项工作(至少在 vga 30 fps 中): gst启动v4l2src num缓冲区=100!视频/x-raw-yuv!队列 !ffmpeg色彩空间!队列 !vpuenc编解码器=6!avimux!文件接收器位置=outputh264.avi 同步=false 在 iMX53 上,有 mfw_ipucsc,但我在 12.09 BSP 上发现的只有 ipucsc.imx,它不起作用,可能只有 DP 路径中的 CSC,这应该在图像转换器中是可能的,但我没有找到任何插件。有人有更好的管道吗?
View full article
HOB Quick Start Guide What is HOB? Hob is a graphical user interface for BitBake. Its primary goal is to enable a user to perform common tasks more easily. It basically runs the Bitbake commands on the background while showing a Graphic User Interface. Hob may not work correctly with Daisy metadata as it is getting deprecated in favor of a new web based interface for Yocto under the name Toaster. Here is what you can do with the current version of Hob on the Freescale Community BSP and BSP Release. - Build images - Edit existing image recipes - Create your own image recipes Note: HOB will write the local.conf file and make modifications which may conflict with baking images outside of HOB. In this case you may need to re-run the environment initialization in order to restore the local.conf file. Starting HOB Once the environment has been initialized (using the setup-environment script on the Freescale Community BSP or the fsl-setup-release on the Freescale BSP Release) use the command below. $ hob & The GUI should then appear: You may then select the MACHINE for which you will build and the Layers of your project. HOB  will take and updated the local.conf and bblayers.conf values so the desired BSP layers will already be selected and available MACHINES on these layers will appear on the drop down menu. Once these options are set HOB will parse the recipes and create a dependency tree in order to show available images for that MACHINE. Image File System Types Advance configuration options include image file system types. Please note that HOB does not support the sdcard format so if it is needed it has to be added manually on the local.conf file and then run bitbake outside of HOB. As HOB changed the local.conf file even if the sdcard format was originally available it may be rewrite and no longer available until the following line is added to local.conf. IMAGE_FSTYPES="tar.bz2 ext3 sdcard" Recipes screen On the recipes screen we can see the recipes included on the image and available recipes, then also package groups. Time to bake! After these configurations you may either build the packages using HOB interface or run Bitbake outside of HOB. (In case you wish to have your image on the sdcard format please see the earlier image types clarification) The resulting image will be stored on /tmp/deploy/images/ You may also save your image recipe with the selected customizations. Re: HOB Quick Start Guide Please submit any questions or issues related to this document as a discussion in the community.
View full article
S32K14x SRAM ECC注入示例 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** 详细描述: 此示例显示了 SRAM ECC 注入。 默认情况下,在对 SRAM_U 区域中的位置进行读取访问时会注入双位 ECC 错误。 这可以通过 SRAM_U 和 DOUBLE_BIT 宏来改变。 ERM 和 MCM 模块都可以检测到错误,并可以调用相应的中断。 虽然只需要 ERM,但为了演示目的,MCM 中断也启用了 其优先级低于 ERM 中断。 首次调用的 ERM 中断会禁用注入机制 这样在堆栈读取访问期间就无法检测到后续错误。 默认的 S32 Design Studio start_up 文件将向量表复制到 SRAM_L 区域。 为了能够在此 SRAM 区域注入 ECC 错误并调用中断, 复制被 __flash_vector_table__ 符号禁用 在start_up.h中声明文件并在S32K144_64_flash链接器文件中定义。 -------------------------------------------------------------------------------------------- 测试硬件:S32K144EVB-Q100 单片机:S32K144 0N57U 调试器:S32DSR1 目标:internal_FLASH ********************************************************************************
View full article
iDrive_里程碑_2 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 在这个里程碑中,我们专注于创建控制从设备接收的数据流的基础设施。 我们创建了一个托管在 Google Cloud Platform 中的 Web API 应用程序(ASP .NET),用于存储和解释我们的数据(来自设备),并向移动应用程序发送通知,告知用户汽车被盗(已移动)。 我们还创建了移动应用程序(原生,在 Xamarin.Android 中创建),该应用程序使用 Google Maps API 来嵌入地图片段,用于显示我们设备的位置(以及隐式显示汽车的位置)。 通知系统已准备好投入生产,我们使用 Azure 通知中心作为传递通知的中间件,因为它具有可扩展性、可靠性、包含遥测数据并且安全。 (在 “我的视频” 中查看)
View full article
DES-N1855 PCBおよびシステム環境向けの高速SERDESモデリング <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ネットワーキング デバイスは、10 Gbps を超える高速差動シグナリングを使用します。高速チャネルのトランスミッタ(TX)およびレシーバ(RX)素子の回路設計には、PCBおよびシステムの信号損失をオフセットする機能があります。このセッションでは、高速信号チャネルとその特性を確認し、TX回路とRX回路が一般的に信号損失を相殺するためにどのように使用されているかを説明します。また、これらのTXおよびRX回路を効果的に機能させるために必要なチャネルの主要な特性も示します。このセッションでは、PCBチャネルの最大長、最適化が必要なPCB固有の構造、および5〜10Gbps動作のためのIBIS-AMIモデルの使用についても説明します。NXPのPCB設計からのチャネルの例も含まれます。 ビデオプレゼンテーションを見る <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ネットワーキング デバイスは、10 Gbps を超える高速差動シグナリングを使用します。高速チャネルのトランスミッタ(TX)およびレシーバ(RX)素子の回路設計には、PCBおよびシステムの信号損失をオフセットする機能があります。このセッションでは、高速信号チャネルとその特性を確認し、TX回路とRX回路が一般的に信号損失を相殺するためにどのように使用されているかを説明します。また、これらのTXおよびRX回路を効果的に機能させるために必要なチャネルの主要な特性も示します。このセッションでは、PCBチャネルの最大長、最適化が必要なPCB固有の構造、および5〜10Gbps動作のためのIBIS-AMIモデルの使用についても説明します。NXPのPCB設計からのチャネルの例も含まれます。 ビデオプレゼンテーションを見る デザイン |ソフトウェア&サービス
View full article
QorIQ Layerscape LS2085/88マルチコア通信プロセッサ、ネットワーキングの未来を支援 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> EUF-NET-T1743 - QorIQ LS2085/88は、汎用性の高いLayerscape 2デバイスです。GPP レイヤーには、8 つの A57/A72 ARM® コアが含まれています。APPレイヤーには、AIOP、PME、DCE、およびSECエンジンが含まれています。WRPPレイヤーには、WRIOP、SATA、およびPCIeエンジンが含まれています。このプレゼンテーションでは、QorIQ LS2085/88プロセッサのさまざまなコンポーネントとターゲットの使用例の概要を説明します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> EUF-NET-T1743 - QorIQ LS2085/88は、汎用性の高いLayerscape 2デバイスです。GPP レイヤーには、8 つの A57/A72 ARM® コアが含まれています。APPレイヤーには、AIOP、PME、DCE、およびSECエンジンが含まれています。WRPPレイヤーには、WRIOP、SATA、およびPCIeエンジンが含まれています。このプレゼンテーションでは、QorIQ LS2085/88プロセッサのさまざまなコンポーネントとターゲットの使用例の概要を説明します。
View full article
LS1021A IoT ホストプロセッサと MKW20 zigbee を使用して色相電球を切り替えるためのクイックデモセットアップ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> LS1021A IoTホストプロセッサとMKW20 zigbeeを使用して色相電球を切り替えるためのクイックデモセットアップ。ここでは、2 つのステップのセットアップを通じてライティングのデモを行います。最初のステップは、TWR-KW20 EVBを使用して、テストツールと呼ばれるPCツールを介して色相電球を制御することです。 次のステップは、PCテストツールの代わりにホストプロセッサとしてLS1021に移行することです。 KW20 USBドングル、LS1021A、Hue Bulbを使用しています。KW20 USBドングルは、Beekitを介してZigbeeコーディネーターとして構成され、このKW20 USBドングルを接続しLS1021A、LS1021Aオン/オフコマンドを発行して色相電球を切り替えます。その後、フリースケールのLS1021AとMKW20シリーズを使用して簡単なデモを作成できます <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> LS1021A IoTホストプロセッサとMKW20 zigbeeを使用して色相電球を切り替えるためのクイックデモセットアップ。ここでは、2 つのステップのセットアップを通じてライティングのデモを行います。最初のステップは、TWR-KW20 EVBを使用して、テストツールと呼ばれるPCツールを介して色相電球を制御することです。 次のステップは、PCテストツールの代わりにホストプロセッサとしてLS1021に移行することです。 KW20 USBドングル、LS1021A、Hue Bulbを使用しています。KW20 USBドングルは、Beekitを介してZigbeeコーディネーターとして構成され、このKW20 USBドングルを接続しLS1021A、LS1021Aオン/オフコマンドを発行して色相電球を切り替えます。その後、フリースケールのLS1021AとMKW20シリーズを使用して簡単なデモを作成できます
View full article
斯洛伐克布拉迪斯拉发理工大学 3KD 团队技术报告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 为布拉迪斯拉发斯洛伐克理工大学 3KD 队(斯洛伐克)提交技术报告 - 2015 年 EMEA 总决赛 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 为布拉迪斯拉发斯洛伐克理工大学 3KD 队(斯洛伐克)提交技术报告 - 2015 年 EMEA 总决赛
View full article
Android CTS Verifier The Compatibility Test Suite Verifier is a supplement to the Compatibility Test Suite. The main difference lies in that the verifier is developed for tests that cannot run on their own so they require user input in order to be tested. These tests would include the audio quality, the touchscreen, accelerometer, camera, etc. There is no “best verifier option”, one CTS complements the other. In this document we will focus on how to perform the Verifier test. Requirements: A PC with the Android SDK installed. Your “Device Under Test” (your development board) Optional >> A second android device with compatible Wifi and Bluetooth Setup Steps: Install de Android SDK on your PC Download the appropriate CTS Verifier APK. The list of APK’s can be found here: https://source.android.com/compatibility/downloads.html Make sure that your Device Under Test has its system date and time set correctly. Install the CTS Verifier APK on the Device Under Test* For more information regarding ADB commands, follow this link: https://community.freescale.com/docs/DOC-102514 Initialization: After the setup is done, you should see the application installed: You will see the list of available tests for manual verification: Video Link : 4502 For each test, you will see detailed instructions to run it, and a “pass” and “fail” buttons. Video Link : 4530 Once you run each test, you will have the posibility to choose the outcome. (in some cases, pass/fail outcome will be determined automatically). The list of tests (for CTS Verifier 5.1_r2) is: Camera: FOV Calibration, Formats, ITS, Intents, Orientation, Video. Car: Car Dock Test Clock: Alarms and Timers Test Device Administration: Policy serialization test, screen lock test. Features: Hardware/Software feature summary Hardware: USB Accessory Test Job Scheduler: Charging constraints, connectivity constraints, idle mode constraints. Location: Battery saving mode test, location mode off test Managed provisioning: BYOD managed provisioning, device owner provisioning Networking: Bluetooth test, Wi-Fi direct test Notifications: CA Cert notification, CA Cert notificacion on boot, notification attention management, notification listener, notificacion package priority Other: Data backup, screen pinning, widget framework Projection: Projection cube, projection multitouch, projection offscreen, projection scrolling, projection video playback, projection widget Security: Keyguard password verification, SUID file scanner. Sensors: Accelerometer mearument, CTS Sensor batching, CTS Sensor integration, CTS sensor test, CTS single sensor test, magnetic field measurement, sensor batching. Streaming: Streaming video quality verifier. Exporting test results: Tap the “save disk” icon. A pop-up will show the path of the report that was created. Video Link : 4531 With the board connected to the PC through USB, pull the report using ADB: To download all reports run : adb pull /mnt/sdcard/ctsVerifierReports/ .
View full article
FTF_Austin_FTF-ACC-F1276_2015.pptx This session will explain how Freescale can enable customers to develop 76-81 GHz short and long range radar applications using the MPC577xK MCU, it will explain the concepts of the radar algorithms, including practical aspects such as SDADC or MIPI CSI sampling, Chirp Generation, Data Compression, R,V FFT, Detection and Tracking algorithms, and the benefits of the new Freescale IP that can allow them to improve their system resolution and accuracy. In this session customers will take away a detailed understanding of how to develop fast modulation radar systems using the MPC577xK MCU including the BOM cost advantages it also brings. This session will explain how Freescale can enable customers to develop 76-81 GHz short and long range radar applications using the MPC577xK MCU, it will explain the concepts of the radar algorithms, including practical aspects such as SDADC or MIPI CSI sampling, Chirp Generation, Data Compression, R,V FFT, Detection and Tracking algorithms, and the benefits of the new Freescale IP that can allow them to improve their system resolution and accuracy. In this session customers will take away a detailed understanding of how to develop fast modulation radar systems using the MPC577xK MCU including the BOM cost advantages it also brings. General Re: FTF_Austin_FTF-ACC-F1276_2015.pptx Hi Andrew Robertson I wanted to check to see if you had your final file. I need to do one last review and then convert it to PDF to include it on the FTF App and public community page. Please help to upload this by selecting "Edit" under Actions as soon as possible. Thanks! Re: FTF_Austin_FTF-ACC-F1276_2015.pptx I have loaded the Marcom reviewed version to this link to help document the review cycle. Here are comments after the Marcom review: I have approved this presentation after making minor changes to punctuation. I have other concerns to highlight: Slide 4 says: FMCW operation is independent of the speed or direction of travel of the target high precision. Andrew, is “target high precision” correct? No Summary and Conclusion section exists in this presentation. Andrew, please add a summary/conclusion and upload the final version based on the attached. Hi Andrew Robertson Please take Brian and John's notes into consideration when finalizing your presentation. Please make sure to use the latest version when making any changes. Once you have finalized your presentation please upload the final file here by selecting "Edit" under Actions and click Publish at the bottom of the page no later than Monday, June 15th. Please help to select the Category "4. Final Version - Ready for PDF and Web" when this final version is posted so I know to pull your file for PDF conversion. Re: FTF_Austin_FTF-ACC-F1276_2015.pptx Adding Deactivated user since he will be helping review this file for Lisa Bradley Re: FTF_Austin_FTF-ACC-F1276_2015.pptx Hi andrewrobertson​ I am reviewing a bunch of FTF presentations.  A few comments on yours.... Are you intending to put something after your summary and conclusions?  Can you...   Your closing thoughts, perhaps some URL's like freescale.com/adas or similiar The abstract refers to BOM cost advantages but I don't really see that in the slides (maybe slide 27) but it's a very small reference.  Just wondering if you should call it out more since it was important enough to mention in the abstract. Renee Fortenberry Re: FTF_Austin_FTF-ACC-F1276_2015.pptx Hi Lisa, I just wanted to make sure you were tagged to this file. It is ready for your review. Please let Andy know when you will be pulling the file in case he has additional changes he would like to make before your review. Lisa Bradley Re: FTF_Austin_FTF-ACC-F1276_2015.pptx PPT expert has completed the presentation review. The latest version is posted and ready for Marcom review @Lisa Bradley
View full article
基于wxWidgets的分布式信息与控制系统 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 他们开发的控制器采用i.MX53+Linux。 开发了构建分布式信息和控制系统的解决方案。 Prototmpy 已经运行了一年多。 示例: - 控制电磁搅拌(混合器) http://ontecom.com/en/catalog/ems / Rusal,克拉斯诺亚尔斯克。 - 泵站的监测和管理。 - 气候控制系统的监测和控制。 您可以创建智能家居系统和物联网。有使用 PLC(电力线通信)Qualcomm/Atheros 的经验。 在业余时间,我为 PLC(电力线通信)控制/监控组件智能家居开发了预算解决方案。 基于IEC 61131-3标准开发的软件——分布式信息管理系统。 该解决方案是跨平台的。单个系统中可能存在不同架构和不同操作系统的计算机。 此类信号同步控制器 ARM/Linux 和 x86 服务器(Win、Linux、VMS、...) 使用 wxWidgets。 有关这个主题的文章有,但是用俄语。
View full article
wxWidgets based distributed information and control systems There developed the controller uses i.MX53 + Linux. Has developed a solution for building distributed information and control systems. Prototmpy been in operation for over a year. Examples: - Control Electromagnetic stirring (mixer) http://ontecom.com/en/catalog/ems / Rusal, Krasnoyarsk. - Moniroring and management of pumping stations. - Monitoring and control of climate control systems. You can create a smart home systems and iot. There is experience with PLC (Power Line Communication) Qualcomm/Atheros. In my spare time I develop a budget solution for PLC (Power Line Communication) control / monitoring components smart home. Based on the standard IEC 61131-3 developed software - distributed information management system. The solution is cross-platform. In a single system may be computers of different architectures and various operating systems. Such signals are synchronized controller ARM / Linux, and x86 server (Win, Linux, VMS, ...) Uses wxWidgets. Articles on this subject is, but in Russian.
View full article
AMF-ACC-T1647 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> イーサネットは、自動車の車両通信で最も議論されているテクノロジーの1つになっています。このプレゼンテーションでは、車載イーサネットを網羅する規格の概要を説明します。また、さまざまなアプリケーション間でテクノロジーを実装する際の課題にも対処します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> イーサネットは、自動車の車両通信で最も議論されているテクノロジーの1つになっています。このプレゼンテーションでは、車載イーサネットを網羅する規格の概要を説明します。また、さまざまなアプリケーション間でテクノロジーを実装する際の課題にも対処します。
View full article
S32K344 - FOC integrated with FreeRTOS S32K344 - FOC integrated with FreeRTOS This example demonstrates a 3-phase Permanent Magnet Synchronous Motor (PMSM) vector control (Field Oriented Control - FOC) drive with 2- shunt current sensing with and without position sensor integrated in FreeRTOS environment. This design serves as an example of motor control design using NXP S32K3 automotive family. Example was designed on S32K344 Brushless Direct Current and Permanent Magnet Synchronous Motor Control Development Kit.  C-project based examples are part of MCSPTE1AK344 Development Kit Application Software. An innovative drivers set, Real-Time Drivers (RTD),are used to configure and control the MCU. It complies with Automotive-SPICE, ISO 26262, ISO 9001 and IATF 16949. Production-ready Automotive Math and Motor Control Library set provides essential building blocks for algorithm. FreeMASTER is used as useful run-time debugging tool. Application software contains:  MCSPTE1AK344_PMSM_FOC_2Sh_ll_FreeRTOS - Low-level drivers of RTD and S32 Design Studio Configuration Tools (S32CT) are used to demonstrate non-AUTOSAR approach. Since the motor control structure of the example is similar to dual shunt example, detailed description of the example can be found in application note AN13767 and FreeRTOS related part in AN12881 .
View full article
S32K144 FlexCAN 擬似ネットワーキング STOP モードテストの例 S32DS.ARM.2.2 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** 詳細説明: FlexCAN 0 の Pretended Networking モードを利用し、FlexCAN モジュールが MCU を STOP モードからウェイクアップする方法を示します。 タイムアウト イベントおよびマッチ イベントによるウェイクアップが有効です。 また、ピン割り込みを使用して STOP モードを解除することも可能です。 MCU は SW3 ボタンの押下で STOP モードに移行します。 MCU は次のいずれかが発生すると STOP モードを終了します: - 8 秒間 CAN メッセージが受信されない (CAN PN タイムアウト イベント) - 標準 ID 0x554 または 0x555 のメッセージが受信される (CAN PN マッチ イベント) - SW2 ボタンが押下される (PTC12 割り込み) RUN モードでは青色 LED が減光し、ウェイクアップ要因ごとに減光速度が異なります。 ------------------------------------------------------------------------------ テストハードウェア: S32K144 EVB‑Q100 MCU: FS32K144UAVLL 0N57U Fsys: 160 MHz デバッガ: Lauterbach, OpenSDA ターゲット: internal_FLASH ******************************************************************************** 全般
View full article