Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
DES-N1931 i.MX 6QuadPlus 和 i.MX 6DualPlus 应用处理器 - 性能层多核,适用于视觉震撼的图形中心应用 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 新的i.MX 6DualPlus和i.MX 6QuadPlus处理器集成了多个ARM® Cortex®-A9内核,采用第一代i.MX 6Dual和i.MX 6Quad处理器,使图形性能提高1倍,存储器利用率提高50%以上。 了解3D、2D的增强版本和组合GPU(一个新优化的64位DDR3/LVDDR3/LPDDR2-1066存储器接口,可以增加总线带宽)、更多的嵌入式SRAM以及添加的预取和解析引擎。这些新的处理器非常适用于汽车仪表板和车载信息娱乐系统,以及医疗设备、工业HMI、数字签名和媒体流应用。 观看视频演示 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 新的i.MX 6DualPlus和i.MX 6QuadPlus处理器集成了多个ARM® Cortex®-A9内核,采用第一代i.MX 6Dual和i.MX 6Quad处理器,使图形性能提高1倍,存储器利用率提高50%以上。 了解3D、2D的增强版本和组合GPU(一个新优化的64位DDR3/LVDDR3/LPDDR2-1066存储器接口,可以增加总线带宽)、更多的嵌入式SRAM以及添加的预取和解析引擎。这些新的处理器非常适用于汽车仪表板和车载信息娱乐系统,以及医疗设备、工业HMI、数字签名和媒体流应用。 观看视频演示 设计 | 软件与服务
View full article
Session 13: Memory Services This video presentation is the thirteenth installment of the Essentials of MQX RTOS Application Development training course. In this session, you will be introduced to Memory Services. This training was created by Embedded Access Inc., a Freescale sponsored training provider and proven partner. Session 13 Course Line Lab Outline Different uses for RAM in an Embedded System Where different types of data are stored Creating memory pools Allocating memory from a memory pool Creating partitions Allocating memory from a partition Light Weight Memory Manager vs Full Featured Memory Manager Adding a queue to be used for logging health records Adding a timer and a timer ISR Adding the Health Record structure Processing messages sent to the Health Task to fill in the Health Record entries and store them in the queue Adding a new UI command to print out the Health Records First, watch the video for Session 13: Memory Services​. Then, follow through with the interactive lab assignment below. SESSION 13: LAB ASSIGNMENT INTRODUCTION In this lab we will add the logging of data to memory that is allocated from the system memory pool. We will continue to flesh out our application in this lab and we will focus on the Health Task. The Health Task receives data from various tasks through Message Passing. When a periodic timer expires the Health Task will place the data it has received onto a queue and the UI Task will print out that data. Queue structures have not been covered so far in the course so you may want to review this in the MQX Reference Manual briefly, but it should be quite quick for you to pick this up. A queue is simply a sequential list of data which you can read from and add to. Note that our implementation does not put a cap on the amount of data that could eventually be allocated, so eventually the system will run out of memory and additional health records will not be logged. For a system that you intend to deploy to the field it would obviously be good practice to not exhaust the available memory and an ideal way to do this is with a partition. This lab can be updated on your own to allocate memory from a partition you define instead of allocating memory directly from the system pool. OBJECTIVE The objective of this lab is to use Memory Services to support the logging of health data for our application. We will also cover the use of queues and will implement a timer. Light Weight Timers were covered in session 8. ASSIGNMENT ADDING A QUEUE The first thing we need to do is to add a Queue Structure and the best place to locate this is in main.c where our other global structures are located. Add the following line, and make sure that it is also declared as an extern in main.h.            QUEUE_STRUCT     log_queue; In the Health Task, add the following init function for our log_queue. The '0' parameter indicates that the queue is unbounded and will grow to any size, assuming the system has the memory.            _queue_init(&log_queue, 0 ); ADDING A TIMER In order to set up a timer we'll need a structure to be declared in the Health Task of type LWTIMER_PERIOD_STRUCT and another one of type LWTIMER_STRUCT. In the initialization section of the Health Task create the periodic queue with the _lwtimer_create_periodic_queue() function that has a period of 1 second and no wait time. Note that for this BSP of MQX the define BSP_ALARM_FREQUENCY is set to 200 ticks and each tick is 5 msec, so it represents 1 second. Then add a timer to the queue using the _lwtimer_add_timer_to_queue() function. You do not need an offset and the timer should call a 'health_timer' ISR function that will be defined later. The parameter to pass is the Health Task Queue ID. Note that the 'my_qid' variable isn't valid until after the _msgq_open() function so these new lines should go after the _msgq_open() call. CREATING THE TIMER FUNCTION At the top of HealthTask.c create the 'health_timer' function that will be called when the timer expires. It will receive the Health Task's queue ID as its only parameter, which will have to be converted into a '_queue_id' type. This function will send a message to the Health Task essentially to let it know that it's time to write a log entry of the current values. As was done elsewhere in the application, declare a message of type 'APPLICATION MESSAGE *', set the target queue id, set the message type to be 'LOG_TICK_MESSAGE' and then send the message. That's all that this function needs to do. This new message type needs to be added to the 'APPLICATION_MESSAGE_TYPE_T' data structure in main.h. HEALTH INFORMATION STRUCTURE The Health Task needs a structure to hold all of its health data so in main.h declare a structure as shown below. Since this is going to be copied to a queue, the first element should be of type QUEUE_ELEMENT_STRUCT which MQX uses to manage queue entries. The structure should also have a number to indicate which entry it is in the queue, the temperature, the voltage, and the accelerometer x, y, and z data. typedef struct {    QUEUE_ELEMENT_STRUCT    QE;      uint32_t               NUM;      uint32_t               TEMP;      uint32_t               MV;      uint16_t               X;      uint16_t               Y;      uint16_t               Z; } HEALTH_RECORD; Declare a pointer of type 'HEALTH_RECORD *' at the top of the Health Task. In the Initialization section of the Health Task (ie before the while(1) loop) uses the _mem_alloc_system_zero() function to allocate memory for an instance of "HEALTH_RECORD" from the system pool that is set to zero. For now you don't need to check if this was successful or not, we'll do that later. Declare a 32 bit variable that will be used to count the number of health records, and after the first one has been created (in step 9 above), set this variable to 1. UPDATE THE PROCESSING OF MESSAGES In the while(1) loop of the Health Task it checks if an incoming message is from the Temp Task, and if there is an over temperature condition a message is sent to the Display Task. The Health Task now needs to be processing several types of messages so it would make sense that a switch statement on the received message type is used. Add a case to the switch to handle messages of type TEMP_MESSAGE that will contain the same functionality that is already in the while(1) loop for messages of type TEMP_MESSAGE. And add another case for messages of type LOG_TICK_MESSAGE which for now won't do anything, we'll fix that later. When a TEMP_MESSAGE is received we need to store the passed in temperature, so in the case that handles TEMP_MESSAGEs update the "TEMP" parameter of the health record to be the passed in temperature in this message. Here is where it would be a good idea to first check if our health record != NULL. Add in a case for ACCEL_MESSAGEs which will record the passed in x, y, and z axis motion values into the health record, assuming it's valid. Add in a case for ADC_MESSAGEs which will record the passed in voltage into the health record, assuming it's valid. We are now ready to add the handling of a LOG_TICK_MESSAGE. Since the health record has been updated when the other messages were processed we only need to save the record number (count) into the health record, increment the record number for next time, and then add this health record to the queue using the _queue_enqueue() function like this: _queue_enqueue(&log_queue, &health_record->QE) The Health Task is done with the health record since it just put it on the queue so the 'health_record' pointer should be set to NULL so the rest of your code doesn't try to use it. A valid health_record pointer is required for the next record of course and it is required now so its fields can be filled in as new messages arrive. Use the _mem_alloc_system_zero() function as was done before to allocate memory for another record. Currently, at the end of the while(1) loop all received messages are being passed on to the Display Task. However, we don't want to pass on messages of type LOG_TICK_MESSAGE so the code needs to be updated such that it only passes on the other types of messages. This could be done with a test for msg->MESSAGE_TYPE != LOG_TICK_MESSAGE condition, but to be more generic and accommodating of future message types that shouldn't be passed on to the Display Task it might be better for the handling of the LOG_TICK_MESSAGEs to free the message using the _msg_free() function and to set the 'msg' pointer to NULL. Then at the end of the while loop check that only non-NULL messages are sent to the Display Task. UPDATING THE UI TASK It is intended that the health records can be printed out using the UI Task. This is a menu driven interface and so we need to add a new command to read the log file. In UiTask.c add a case for the user pressing the letter 'l' (lower case L) for the log file and get the health record from the queue using the queue_dequeue() function. It can be a good idea to us a small function for items like this since there can be multiple places in your code that need to do a similar task. Such a function could look like this: HEALTH_RECORD  *      get_log_record(void) {       return (HEALTH_RECORD * )   _queue_dequeue(&log_queue); } Add print statements for the record number and all other data that is in the health record. Free up the memory of the health record once you're done with it to avoid a memory leak. This will cover the printing of the first record but the intention is for this UI command to print out all health records that are stored on the queue. Use a while loop to fetch records from the log using our new get_log_record() function until this function returns a NULL entry indicating that there are no more records to fetch from the queue. Note that the function returns a pointer to a HEALTH_RECORD, so a variable in the UI_TASK of this type will have to be declared. Compile and run your code. Use the user interface to request the health logs to be printed out and confirm that the data is correct. You can adjust the potentiometer and move the tower board to change the data. You may also want to comment out the print messages from the Health Task and Display Task so these messages don't interfere. Need more help? The full source code for this lab can be found in the 'Lab Source Code' folder here​.
View full article
例MPC5777C GHS714 外部SRAM_test ******************************************************************************** *詳細な説明: *アプリケーションは基本的な初期化を実行し、次に外部のEBIを初期化します * SRAMをMPC5777C-516DSに接続し、ブロックの書き込みと読み出しでテストします。 *データ。 * * ------------------------------------------------------------------------------ ※テストHW:MPC5777C-512DS Rev.A + MPC57xx マザーボード Rev.C ※MCU:PPC5777CMM03 3N45H * Fsys: PLL1 = core_clk = 264MHz, PLL0 = 192MHz *デバッガ:Lauterbach Trace32 * 対象:internal_FLASH *端末:19200-8-パリティなし-1ストップビット-eSCI_Aのフロー制御なし * EVB接続:位置1-2のジャンパーJ4(CS0を選択) * ******************************************************************************** ******************************************************************************** *詳細な説明: *アプリケーションは基本的な初期化を実行し、次に外部のEBIを初期化します * SRAMをMPC5777C-516DSに接続し、ブロックの書き込みと読み出しでテストします。 *データ。 * * ------------------------------------------------------------------------------ ※テストHW:MPC5777C-512DS Rev.A + MPC57xx マザーボード Rev.C ※MCU:PPC5777CMM03 3N45H * Fsys: PLL1 = core_clk = 264MHz, PLL0 = 192MHz *デバッガ:Lauterbach Trace32 * 対象:internal_FLASH *端末:19200-8-パリティなし-1ストップビット-eSCI_Aのフロー制御なし * EVB接続:位置1-2のジャンパーJ4(CS0を選択) * ********************************************************************************
View full article
RT106L/S voice control system based on the Baidu cloud RT106L_S voice control system based on the Baidu cloud 1 Introduction     The NXP RT106L and RT106S are voice recognition chip which is used for offline local voice control, SLN-LOCAL-IOT is based on RT106L, SLN-LOCAL2-IOT is a new local speech recognition board based on RT106S. The board includes the murata 1DX wifi/BLE module, the AFE voice analog front end, the ASR recognition system, the external flash, 2 microphones, and the analog voice amplifier and speakers. The voice recognition process for SLN-LOCAL-IOT and SLN-LOCAL2-IOT is different and the new SLN-LOCAL2-IOT is recommended.     This article is based on the voice control board SLN-LOCAL/2-IOT to implement the following block diagram functions: Pic 1 Use the PC-side speed model tool (Cyberon DSMT) to generate WW(wake word) and VC(voice command) Command related voice engine binary files , which will be used by the demo code. This system is mainly used for the Chinese word recognition, when the user says Chinese word: "小恩小恩", it wakes up SLN-LOCAL/2-IOT, and the board gives feedback "小恩来了,请吩咐". Then system enter the voice recognition stage, the user can say the voice recognition command: “开红灯”,“关红灯”,“开绿灯”,“关绿灯”,“灯闪烁”,“开远程灯”,“关远程灯”, after recognition, the board gives feedback "好的". Among them, “开红灯”,“关红灯”,“开绿灯”,“关绿灯”,“灯闪烁”,the five commands are used for the local light switch, while the 开远程灯”,“关远程灯“two commands can through network communication Baidu cloud control the additional MIMXRT1060-EVK development board light switch. SLN-LOCAL/2-IOT through the WIFI module access to the Internet with MQTT protocol to achieve communication with Baidu cloud, when dectect the remote control command, publish the json packets to Baidu cloud, while MIMRT1060-EVK subscribe Baidu cloud data, will receive data from the IOT board and analyze the EVK board led control. PC side can use MQTT.fx software to subscribe the Baidu cloud data, it also can send data to the device to achieve remote control function directly.  Now, will give the detail content about how to use the SLN-LOCAL/2-IOT SDK demo realize the customized Chinese wake command and voice command, and remote control the MIMXRT1060-EVK through the Baidu Cloud.     2 Platform establish 2.1 Used platform SLN-LOCAL-IOT/SLN-LOCAL2-IOT MIMXRT1060-EVK MQTT.fx SDK_2_8_0_SLN-LOCAL2-IOT MCUXPresso IDE Segger JLINK Baidu Smart Cloud: Baidu cloud control+ TTS Audacity:audio file format convert tool WAVToCode:wav convert to the c array code, which used for the demo tilte play MCUBootUtility: used to burn the feedback audio file to the filesystem Cyberon DSMT: wake word and voice detect command generation tool DSMT is the very important tool to realize the wake word and voice dection, the apply follow is: Pic 2 2.2 Baidu Smart cloud 2.2.1 Baidu cloud IOT control system Enter the IoT Hub: https://cloud.baidu.com/product/iot.html     Click used now. 2.2.1.1 Create device project Create a project, select the device type, and enter the project name. Device types can use shadows as images of devices in the cloud to see directly how data is changing. Once created, an endpoint is generated, along with the corresponding address: Pic 3 2.2.1.2 Create Thing model The Thing model is mainly to establish various properties needed in the shadow, such as temperature, humidity, other variables, and the type of value given, in fact, it is also the json item in the actual MQTT communication.    Click the newly created device-type project where you can create a new thing model or shadow: Pic 4    Here create 3 attributes:LEDstatus,humid,temp It is used to represent the led status, humidity, temperature and so on, which is convenient for communication and control between the cloud and RT board. Once created, you get the following picture: Pic 5 2.2.1.3 Create Thing shadow In the device-type project, you can select the shadow, build your own shadow platform, enter the name, and select the object model as the newly created Thing model containing three properties, after the create, we can get the details of the shadow:   Pic 6 At the same time will also generate the shadow-related address, names and keys, my test platform situation is as follows: TCP Address: tcp://rndrjc9.mqtt.iot.gz.baidubce.com:1883 SSL Address: ssl://rndrjc9.mqtt.iot.gz.baidubce.com:1884 WSS Address: wss://rndrjc9.mqtt.iot.gz.baidubce.com:443 name: rndrjc9/RT1060BTCDShadow key: y92ewvgjz23nzhgn Port 1883, does not support transmission data encryption Port 1884, supports SSL/TLS encrypted transmission Port 8884, which supports wesockets-style connections, also contains SSL encryption. This article uses a 1883 port with no transmission data encryption for easy testing. So far, Baidu cloud device-type cloud shadow has been completed, the following can use MQTTfx tools to connect and test. In practice, it is recommended that customers build their own Baidu cloud connection, the above user key is for reference only. 2.2.2 Online TTS    SLN-LOCAL/2-IOT board recognizes wake-up words, recognition words, or when powering on, you need to add corresponding demo audio, such as: "百度云端语音测试demo ", "小恩来啦!请吩咐“,"好的". These words need to do a text-to-wav audio file synthesis, here is Baidu Smart Cloud's online TTS function, the specific operation can refer to the following documents: https://ai.baidu.com/ai-doc/SPEECH/jk38y8gno   Once the base audio library is opened, use the main.py provided in the link above and modify it to add the Chinese field you want to convert to the file "TEXT" and add the audio file to be converted in "save_file" such as xxx .wav, using the command: python main.py to complete the conversion, and generate the audio format corresponding to the text, such as .mp3, .wav. Pic 7 After getting the wav file, it can’t be used directly, we need to note that for SLN-LOCAL/2-IOT board, you need to identify the audio source of the 48K sample rate with 16bit, so we need to use the Audioacity Audio tool to convert the audio file format to 48K16bit wav. Import 16K16bit wav files generated by Baidu TTS into the Audioacity tool, select project rate of 48Khz, file->export->export as WAV, select encoding as signed 16bit PCM, and regenerate 48Khz16bit wav for use. Pic 8 “百度云端语音测试demo“:Used for power-on broadcasting, demo name broadcasting, it is stored in RT demo code, so you need to convert it to a 16bit C code array and add it to the project. "小恩来啦!请吩咐",“好的“:voice detect feedback, it is saved in the filesystem ZH01,ZH02 area. 2.3 playback audio data prepare and burn   There are two playback audio file, it is "小恩来啦!请吩咐",“好的“,it is saved in the filesystem ZH01,ZH02 area. Filesystem memory map like this: Pic 9 So, we need to convert the 48K16bit wav file to the filesystem needed format, we need to use the official tool::Ivaldi_sln_local2_iot Reference document:SLN-LOCAL2-IOT-DG chapter 10.1 Generating filesystem-compatible files Use bash input the commands like the following picture: Pic10 Use the convert command to get the playback bin file: python file_format.py -if xiaoencoming_48k16bit.wav -of xiaoencoming_48k16bit.bin -ft H At last, it will generate the file: "小恩来啦!请吩咐"->xiaoencoming_48k16bit.bin,burn to flash address 0x6184_0000 “好的”->OK_48k16bit.bin, burn to flash address 0x6180_0000 Then, use MCUBootUtility tool burn the above two file to the related images. Here, take OK_48k16bit.bin as an example, demo enter the serial download mode(J27-0), power off and power on. Flash chip need to select hyper flash IS26KSXXS, use the boot device memory windows, write button to burn the .bin file to the related address, length is 0X40000 Pic11 Pic12 xiaoencoming_48k16bit.bin can use the same method to download to 0x6184_0000,Length is 0X40000. 2.4 Demo audio prepare and add The prepared baiduclouddemo_48K16bit.wav(“百度云端语音测试demo “) need to convert to the 16bit C array code, and put to the project code, calls by the code, this is used for the demo mode play. The convert need to use the WAVToCode, the operation like this: Pic 13 The generated baiducloulddemo_48K16bit.c,add it to the demo project C files: sln_local_iot_local_demo->audio->demos->smart_home.c。 2.5 WW and VC prepare Wake-up word are generated through the cyberon DSMT tool, which supports a wide range of language, customers can request the tool through Figure 2. The Chinese wake-up words and voice command words in this article are also generated through DSMT. DSMT can have multiple groups, group1 as a wake-up word configuration, CmdMapID s 1. Other groups act as voice command words, such as CMD-IOT in this article, cmdMapID=2. Pic 14 Pic 15 Wake word continuously detects the input audio stream, uses group1, and if successfully wakes up, will do the voice command detection uses group2, or other identifying groups as well as custom groups. The wake-up words using the DSMT tool, the configuration are as follows: Pic 16 The WW can support more words, customer can add the needed one in the group 1. Use the DSMT configure VC like this: Pic 17 Then, save the file, code used file are: _witMapID.bin, CMD_IOT.xml,WW.xml. In the generated files, CYBase.mod is the base model, WW.mod is the WW model, CMD_IOT.mod is the VC model. After Pic 16,17, it finishes the WW and VC command prepare, we can put the DSMT project to the RT106S demo project folder: sln_local2_iot_local_demo\local_voice\oob_demo_zh 3 Code prepare Based on the official SLN-LOCAL2-IOT SDK local_demo, the code in this article modifies the Chinese wake-up words and recognition words (or you can build a new customer custom group directly), add local voice detect the led status operations, Then feedback Chinese audio, demo Chinese audio, Wifi network communication MQTT protocol code, and Baidu cloud shadow connection publish. Source reference code SDK path: SDK_2_8_0_SLN-LOCAL2-IOT\boards\sln_local2_iot\sln_voice_examples\local_demo   SDK_2_8_0_SLN-LOCAL2-IOT\boards\sln_local2_iot\sln_boot_apps SLN-LOCAL2-IOT and SLN-LOCAL-IOT code are nearly the same, the only difference is that the ASR library file is different, for RT106S (SLN-LOCAL2-IOT) using SDK it’s own libsln_asr.a library, for RT106L (SLN-LOCAL-IOT) need to use the corresponding libsln_asr_eval.a library.    Importing code requires three projects: local_demo, bootloader, bootstrap. The three projects store in different spaces. See SLN-LOCAL2-IOT-DG .pdf, chapter 3.3 Device memory map    This is the 3 chip project boot process: Pic 18 This document is for demo testing and requires debug, so this article turns off the encryption mechanism, configures bootloader, bootstrap engineering macro definition: DISABLE_IMAGE_VERIFICATION = 1, and uses JLINK to connect SLN-LOCAL/2-IOT's SWD interface to burn code. The following is to add modification code for app local_demo projects. 3.1 sln-local/2-iot code Sln-local-iot, sln-local2-iot platform, the following modification are the same for the two platform. 3.1.1 Voice recognition related code 1)Demo audio play Play content:“百度云端语音测试demo“ sln_local2_iot_local_demo_xe_ledwifi\audio\demos\ smart_home.c content is replaced by the previously generated baiducloulddemo_48K16bit.C. audio_samples.h,modify: #define SMART_HOME_DEMO_CLIP_SIZE 110733 This code is used for the main.c announce_demo API play:         case ASR_CMD_IOT:             ret = demo_play_clip((uint8_t *)smart_home_demo_clip, sizeof(smart_home_demo_clip)); 2)command print information #define NUMBER_OF_IOT_CMDS      7 IndexCommands.h static char *cmd_iot_en[] = {"Red led on", "Red led off", "Green led on", "Green led off",                              "cycle led",        "remote led on",         "remote led off"}; static char *cmd_iot_zh[] = {"开红灯", "关红灯", "开绿灯", "关绿灯", "灯闪烁", "开远程灯", "关远程灯"}; Here is the source code modification using IOT, you can actually add your own speech recognition group directly, and add the relevant command identification. 3)sln_local_voice.c Line757 , add led-related notification information in ASR_CMD_IOT mode. oob_demo_control.ledCmd = g_asrControl.result.keywordID[1];     The code is used to obtain the recognized VC command data, and the value of keywordID[1] represents the number. This number can let the code know which detail voice is detected. so that you can do specific things in the app based on the value of ledcmd. The value of keywordID[1] corresponds to Command List in Figure 17. For example, “开远程灯“, if woke up, and recognized "开远程灯", then keywordID[1] is 5, and will transfer to oob_demo_control.ledCmd, which will be used in the appTask API to realize the detail control. 4) main.c void appTask(void *arg) Under case kCommandGeneric: if the language is Chinese, then add the recognition related control code, at first, it will play the feedback as “好的”. Then, it will check the voice detect value, give the related local led control. else if (oob_demo_control.language == ASR_CHINESE) { // play audio "OK" in Chinese #if defined(SLN_LOCAL2_RD) ret = audio_play_clip((uint8_t *)AUDIO_ZH_01_FILE_ADDR, AUDIO_ZH_01_FILE_SIZE); #elif defined(SLN_LOCAL2_IOT) ret = audio_play_clip(AUDIO_ZH_01_FILE); #endif //kerry add operation code==================================================begin RGB_LED_SetColor(LED_COLOR_OFF); if (oob_demo_control.ledCmd == LED_RED_ON) { RGB_LED_SetColor(LED_COLOR_RED); vTaskDelay(5000); } else if (oob_demo_control.ledCmd == LED_RED_OFF) { RGB_LED_SetColor(LED_COLOR_OFF); vTaskDelay(5000); } else if (oob_demo_control.ledCmd == LED_BLUE_ON) { RGB_LED_SetColor(LED_COLOR_BLUE); vTaskDelay(5000); } else if (oob_demo_control.ledCmd == LED_BLUE_OFF) { RGB_LED_SetColor(LED_COLOR_OFF); vTaskDelay(5000); } else if (oob_demo_control.ledCmd == CYCLE_SLOW) { for (int i = 0; i < 3; i++) { RGB_LED_SetColor(LED_COLOR_RED); vTaskDelay(400); RGB_LED_SetColor(LED_COLOR_OFF); RGB_LED_SetColor(LED_COLOR_GREEN); vTaskDelay(400); RGB_LED_SetColor(LED_COLOR_OFF); RGB_LED_SetColor(LED_COLOR_BLUE); vTaskDelay(400); } } … } In addition to local voice recognition control, this article also add remote control functions, mainly through wifi connection, use the mqtt protocol to connect Baidu cloud server, when local speech recognition get the remote control command, it publish the corresponding control message to Baidu cloud, and then the cloud send the message to the client which subscribe this message,  after the client get the message, it will refer to the message content do the related control. 3.1.3 Network connection code 1)sln_local2_iot_local_demo_xe_ledwifi\lwip\src\apps\mqtt     Add mqtt.c 2)sln_local2_iot_local_demo_xe_ledwifi\lwip\src\include\lwip\apps Add mqtt.h, mqtt_opts.h,mqtt_prv.h The related mqtt driver is from the RT1060 sdk, which already added in the attachment project. 3)sln_tcp_server.c   Add MQTT application layer API function code, client ID, server host, MQTT server port number, user name, password, subscription topic, publishing topic and data, etc., more details, check the attachment code.    The MQTT application code is ported from the mqtt project of the RT1060 SDK and added to the sln_tcp_server.c. TCP_OTA_Server function is used to initialize the wifi network, realize wifi connection, connect to the network, resolve Baidu cloud server URL to get IP, and then connect Baidu cloud server through mqtt, after the successful connection, publish the message at first, so that after power-up through mqttfx to see whether the power on network publishing message is successful. TCP_OTA_Server function code is as follows: static void TCP_OTA_Server(void *param) //kerry consider add mqtt related code { err_t err = ERR_OK; uint8_t status = kCommon_Failed; #if USE_WIFI_CONNECTION /* Start the WiFi and connect to the network */ APP_NETWORK_Init(); while (status != kCommon_Success) { status_t statusConnect; statusConnect = APP_NETWORK_Wifi_Connect(true, true); if (WIFI_CONNECT_SUCCESS == statusConnect) { status = kCommon_Success; } else if (WIFI_CONNECT_NO_CRED == statusConnect) { APP_NETWORK_Uninit(); /* If there are no credential in flash delete the TPC server task */ vTaskDelete(NULL); } else { status = kCommon_Failed; } } #endif #if USE_ETHERNET_CONNECTION APP_NETWORK_Init(true); #endif /* Wait for wifi/eth to connect */ while (0 == get_connect_state()) { /* Give time to the network task to connect */ vTaskDelay(1000); } configPRINTF(("TCP server start\r\n")); configPRINTF(("MQTT connection start\r\n")); mqtt_client = mqtt_client_new(); if (mqtt_client == NULL) { configPRINTF(("mqtt_client_new() failed.\r\n");) while (1) { } } if (ipaddr_aton(EXAMPLE_MQTT_SERVER_HOST, &mqtt_addr) && IP_IS_V4(&mqtt_addr)) { /* Already an IP address */ err = ERR_OK; } else { /* Resolve MQTT broker's host name to an IP address */ configPRINTF(("Resolving \"%s\"...\r\n", EXAMPLE_MQTT_SERVER_HOST)); err = netconn_gethostbyname(EXAMPLE_MQTT_SERVER_HOST, &mqtt_addr); configPRINTF(("Resolving status: %d.\r\n", err)); } if (err == ERR_OK) { configPRINTF(("connect to mqtt\r\n")); /* Start connecting to MQTT broker from tcpip_thread */ err = tcpip_callback(connect_to_mqtt, NULL); configPRINTF(("connect status: %d.\r\n", err)); if (err != ERR_OK) { configPRINTF(("Failed to invoke broker connection on the tcpip_thread: %d.\r\n", err)); } } else { configPRINTF(("Failed to obtain IP address: %d.\r\n", err)); } int i=0; /* Publish some messages */ for (i = 0; i < 5;) { configPRINTF(("connect status enter: %d.\r\n", connected)); if (connected) { err = tcpip_callback(publish_message_start, NULL); if (err != ERR_OK) { configPRINTF(("Failed to invoke publishing of a message on the tcpip_thread: %d.\r\n", err)); } i++; } sys_msleep(1000U); } vTaskDelete(NULL); } Please note the following published json data, it can’t be publish directly in the code. {   "reported": {     "LEDstatus": false,     "humid": 88,     "temp": 22   } } Which need to use this web https://www.bejson.com/ realize the json data compression and convert: {\"reported\" : {     \"LEDstatus\" : true,     \"humid\" : 88,     \"temp\" : 11    } } 4)main appTask Under case kCommandGeneric: , if the language is Chinese, then add the corresponding voice recognition control code. "开远程灯": turn on the local yellow light, publish the “remote led on” mqtt message to Baidu cloud, control remote 1060EVK board lights on. "关远程灯": turn on the local white light, publish the “remote led off” mqtt message to Baidu cloud, control the remote 1060EVK board light off. Related operation code: else if (oob_demo_control.ledCmd == LED_REMOTE_ON) { RGB_LED_SetColor(LED_COLOR_YELLOW); vTaskDelay(5000); err_t err = ERR_OK; err = tcpip_callback(publish_message_on, NULL); if (err != ERR_OK) { configPRINTF(("Failed to invoke publishing of a message on the tcpip_thread: %d.\r\n", err)); } } else if (oob_demo_control.ledCmd == LED_REMOTE_OFF) { RGB_LED_SetColor(LED_COLOR_WHITE); vTaskDelay(5000); err_t err = ERR_OK; err = tcpip_callback(publish_message_off, NULL); if (err != ERR_OK) { configPRINTF(("Failed to invoke publishing of a message on the tcpip_thread: %d.\r\n", err)); } } 3.2 MIMXRT1060-EVK code The main function of the MIMXRT1060-EVK code is to configure another client in the cloud, subscribe to the message published by SLN-LOCAL/2-IOT which detect the remote command, and then the LED on the control board is used to test the voice recognition remote control function, this code is based on Ethernet, through the Ethernet port on the board, to achieve network communication, and then use mqtt to connect baidu cloud, and subscribe the message from local2, This enables the reception and execution of the Local2 command. the network code part is similar to SLN-LOCAL2-IOT board network code, the servers, cloud account passwords, etc. are all the same, the main function is to subscribe messages. See the code from attachment RT1060, lwip_mqtt_freertos.c file. When receives data published by the server, it needs to do a data analysis to get the status of the led light and then control it. Normal data from Baidu cloud shadow sent as follows Received 253 bytes from the topic "$baidu/iot/shadow/RT1060BTCDShadow/update/accepted": "{"requestId":"2fc0ca29-63c0-4200-843f-e279e0f019d3","reported":{"LEDstatus":false,"humid":44,"temp":33},"desired":{},"lastUpdatedTime":{"reported":{"LEDstatus":1635240225296,"humid":1635240225296,"temp":1635240225296},"desired":{}},"profileVersion":159}" Then you need to parse the data of LEDstatus from the received data, whether it is false or true. Because the amount of data is small, there is no json-driven parsing here, just pure data parsing, adding the following parsing code to the mqtt_incoming_data_cb function: mqtt_rec_data.mqttindex = mqtt_rec_data.mqttindex + len; if(mqtt_rec_data.mqttindex >= 250) { PRINTF("kerry test \r\n"); PRINTF("idex= %d", mqtt_rec_data.mqttindex); datap = strstr((char*)mqtt_rec_data.mqttrecdata,"LEDstatus"); if(datap != NULL) { if(!strncmp(datap+11,strtrue,4))//char strtrue[]="true"; { GPIO_PinWrite(GPIO1, 3, 1U); //pull high PRINTF("\r\ntrue"); } else if(!strncmp(datap+11,strfalse,5))//char strfalse[]="false"; { GPIO_PinWrite(GPIO1, 3, 0U); //pull low PRINTF("\r\nfalse"); } } mqtt_rec_data.mqttindex =0; It use the strstr search the “LEDstatus“ in the received data, and get the pointer position, then add the fixed length to get the LED status is true or flash. If it is true, turn on the led, if it is false, turn off the led. 4 Test Result    This section gives the test results and video of the system. Before testing the voice function, first use MQTTfx to test baidu cloud connection, release, subscription is no problem, and then test sln-local2-iot combined with mimxrt1060-evk voice wake-up recognition and remote control functions.    For SLN-LOCAL2-IOT wifi hotspot join, enter the command in the print terminal: setup AWS kerry123456 4.1 MQTT.fx test baidu cloud connection MQTT.fx is an EclipsePaho-based MQTT client tool written in the Java language that supports subscription and publishing of messages through Topic.    4.1.1 MQTT fx configuration     Download and install the tool, then open it, at first, need to do the configuration, click edit connection: Pic19 Profile name:connect name Profile type: MQTT broker Broker address: It is the baidu could generated broker address, with 1883 no encryption transfer. Broker port:1883 No encryption Client ID: RT1060BTCDShadow, here need to note, this name should be the same as the could shadow name, otherwise, on the baidu webpage, the connection is not be detected. If this Client ID name is the same as the shadow name, then when the MQTT fx connect, the online side also can see the connection is OK. User credentials: add the thing User name and password from the baidu cloud. After the configuration, click connect, and refresh the website. Before conection: Pic 20 After connection: Pic 21 4.1.2 MQTT fx subscribe When it comes to subscription publishing, what is the topic of publishing subscriptions?  Here you can open your thing shadow, select the interaction, and see that the page has given the corresponding topic situation: Pic 22 Subscribe topic is: $baidu/iot/shadow/RT1060BTCDShadow/update/accepted  Publish topic is: $baidu/iot/shadow/RT1060BTCDShadow/update Pic 23 Click subscribe, we can see it already can used to receive the data. 4.1.3 MQTT fx publish Publish need to input the topic: $baidu/iot/shadow/RT1060BTCDShadow/update It also need to input the content, it will use the json content data. Pic 24 Here, we can use this json data: {   "reported" : {     "LEDstatus" : true,     "humid" : 88,     "temp" : 11    } } The json data also can use the website to check the data: https://www.bejson.com/jsonviewernew/ Pic 25 Input the publish data, and click pubish button: Pic 26 4.1.4 Publish data test result   Before publish, clean the website thing data: Pic 27 MQTT fx publish data, then check the subscribe data and the website situation: Pic 28 We can see, the published data also can be see in the website and the mqttfx subscribe area. Until now, the connection, data transfer test is OK. 4.2 Voice recognition and remote control test This is the device connection picture: Pic 29 4.2.1 voice recognition local control Pic 30 This is the SLN-LOCAL2-IOT print information after recognize the voice WW and VC. Red led on: (view in My Videos) led cycle: (view in My Videos) 4.2.2 voice recognition remote control   Following test, wakeup + remote on, wakeup+remote off, and also give the print result and the video. Pic 31 remote control: (view in My Videos) i.MXRT 106x
View full article
i.MX51 EVK Compiling U-boot Changing Freescale's BSP U-boot using LTIB This quick recipe demonstrates how to compile U-boot using Freescale BSP. 0. After installing i.MX51 BSP: 1. Extract u-boot source: ./ltib -m prep -p u-boot 2. (optional) If you wish to apply changes to the code, the source is located at: /rpm/BUILD/u-boot-2009.08 3. Compile u-boot for the i.MX51 EVK ./ltib -m scbuilb -p u-boot 4. Copy the compiled file to a SD card on your host machine, insert the SD card and: $ sudo dd if=rpm/BUILD/u-boot-2009.08/u-boot.bin of=/dev/mmcblk0 bs=512 /dev/mmcblk0 should replaced according to your host, use "dmesg" after inserting the SD to find out where is the SD on your host. Unmount it before issuing the dd command.   5. Insert the SD on the i.MX 51 EVK, set the switches for SD Card boot and power on the board. i.MX51
View full article
i.MX7ULP Register Programming Aids Important: If you have any questions or would like to report any issues with the DDR tools or supporting documents please create a support ticket in the i.MX community. Please note that any private messages or direct emails are not monitored and will not receive a response. These are detailed programming aids for the registers associated with DRAM initialization (LPDDR3 and LPDDR2). The last work sheet tab in the tool formats the register settings for use with the ARM DS5 debugger. It can also be used with the windows executable for the DDR Stress Test (note the removal of debugger specific commands in this tab). These programming aids were developed for internal NXP validation boards.   This tool serves as an aid to assist with programming the DDR interface of the i.MX 7ULP and is based on the DDR initialization scripts developed for NXP boards and no guarantees are made by this tool.   The following are some general notes regarding this tool: The default configuration for the tool is to enable bank interleaving. Refer to the "How To Use" tab in the tool as a starting point to use this tool. The tool can be configured for one of the two memory types supported by the i.MX 7ULP.  Nevertheless, two separate programming aids are provided based on the DRAM type: LPDDR3 and LPDDR2.  Therefore, you may use the tool pre-configured for your desired memory type as a starting point. Some of the CCM programming at the beginning of the DRAM initialization script (in the "DStream .ds file" tab) were automatically generated and in very few cases may involve writing to reserved bits, however, these writes to reserved bits are simply ignored. Note that in the "DStream .ds file" tab there are DS5 debugger specific commands that should be commented out or removed when using the DRAM initialization for non-debugger specific applications (like when porting to bootloaders). This tool may be updated on an as-needed basis for bug fixes or future improvements.  There is no schedule for aforementioned maintenance. For questions or additional assistance using this tool, please contact your local sales or FAE. i.MX7ULP
View full article
Example S32K144 FlexCAN0 RXFIFO DMA nonSDK S32DS13 ******************************************************************************** Detailed Description: Configures the FlexCAN 0 to transmit and receive message into RXFIFO. LOOPBACK mode is enabled. Two IDs are set into RXFIFO ID table. DMA is configured to read the message from RXFIFO. Within DMA major interrupt the new message is send according to which Identifier Acceptance Filter was hit. ------------------------------------------------------------------------------  Test HW:         S32K144 EVB-Q100  MCU:             PS32K144HFVLL 0N77P  Fsys:            160MHz  Debugger:        Lauterbach  Target:          internal_FLASH ******************************************************************************** Revision History: 1.0     Sep-4-2017     Petr Stancik    Initial Version ******************************************************************************* General Re: Example S32K144 FlexCAN0 RXFIFO DMA nonSDK S32DS13 where did you added the above code ..I am also facing the same issue  Re: Example S32K144 FlexCAN0 RXFIFO DMA nonSDK S32DS13 solved after aligning the CAN software buffer memory. union {  uint8_t buffer[64];  struct  {   uint32_t Buff1;   uint32_t Buff2;   uint32_t Data1;   uint32_t Data2;  }MBS[8]; }CAN_RxData __attribute__((aligned(64)));; Re: Example S32K144 FlexCAN0 RXFIFO DMA nonSDK S32DS13 I have the same problem as you. Have you solved it yet Re: Example S32K144 FlexCAN0 RXFIFO DMA nonSDK S32DS13 Hi,     I am trying to do CAN using DMA in the s32K144 Eval kit. Softyware triggered DMA works fine but it is not working fine when I configured it for CAN RX FIFO. No DMA major loop complete interrupt is received. I am using SDK's and processor expert generated code to initialize the CAN and DMA. Did you have sample code with SDK's? The attached code is not working for me...it is entering the default ISR.
View full article
How to change package on S32DS Processor Expert This document explains how to change the package of a processor expert project, for example, from S32K144 100LQFP to S32K144 64LQFP.  It does NOT explain how to change processor derivatives (e.g. S32K144 to S32K142). 1. Assuming that the project is opened and active, go to Components Library View and click on Processors     2. Expand the repository folders and double click on your processor (e.g. S32K144) 3. Select new package (e.g.S32K144_64) and click on finish. Now the new variant will be added to your project 4. Go to PinSettings component and click on Switch Configuration. This action will change the pins configuration for new package and will discard the original pin configuration. General SDKs Re: How to change package on S32DS Processor Expert Wanna collect this page. Re: How to change package on S32DS Processor Expert Problem resolved! Re: How to change package on S32DS Processor Expert Cool!
View full article
MHW-N1921デジタル高効率AC / DC共振電源 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 共振AC/DC電源は、高出力で優れた効率を発揮します。TEA1916は、共振LLC設計の複雑さを簡素化し、簡単なチューニングを提供するデジタルコントローラーです。これは、多くの共振スイッチモード電源で使用されている非常に一般的なTEA1716を継承します。PCやテレビですが、TEA1916は実際には75W>あらゆる電源に非常に適しています。医療、産業用、サーバー用電源。このTEA1916は、新しいデジタル・サイクル・バイ・サイクル・アーキテクチャ(Vcap制御)を使用して、低電力負荷での新しいタイプの動作を可能にします。これにより、正確に制御されたバーストモード動作を使用して、低出力電力での効率が向上します。また、このTEA1916は、スタンバイ状態またはオフ状態で非常に低い消費電力を実現します。競合他社と差別化するための主要なパフォーマンスパラメータです。最高の効率を得るために、TEA1916はNXPのTEA1995同期整流器と一緒に優れた働きをします。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 共振AC/DC電源は、高出力で優れた効率を発揮します。TEA1916は、共振LLC設計の複雑さを簡素化し、簡単なチューニングを提供するデジタルコントローラーです。これは、多くの共振スイッチモード電源で使用されている非常に一般的なTEA1716を継承します。PCやテレビですが、TEA1916は実際には75W>あらゆる電源に非常に適しています。医療、産業用、サーバー用電源。このTEA1916は、新しいデジタル・サイクル・バイ・サイクル・アーキテクチャ(Vcap制御)を使用して、低電力負荷での新しいタイプの動作を可能にします。これにより、正確に制御されたバーストモード動作を使用して、低出力電力での効率が向上します。また、このTEA1916は、スタンバイ状態またはオフ状態で非常に低い消費電力を実現します。競合他社と差別化するための主要なパフォーマンスパラメータです。最高の効率を得るために、TEA1916はNXPのTEA1995同期整流器と一緒に優れた働きをします。 セキュアモバイル |ヘルスケア&ウェアラブル
View full article
FTF-MHW-N1920 智能交流/直流电源解决方案 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> AC/DC 转换器需要从交流电源提供确定且安全的电源电压,范围从 90 至 264 V AC。关键要求是效率、空载功耗和尺寸。壁式充电器的一项新要求是与手机通信,通过改变电压或电流实现更快的充电。最常见的 AC/DC 拓扑结构是反激式和谐振式。反激式转换器具有成本最低的特点,但输出功率越高,磁性元件尺寸就越大。在这种情况下,谐振转换器是首选,尽管在低负载时效率较低。NXP 发明了一种谐振概念来解决这个问题。演讲将介绍上述AC/DC技术和NXP的产品优势。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> AC/DC 转换器需要从交流电源提供确定且安全的电源电压,范围从 90 至 264 V AC。关键要求是效率、空载功耗和尺寸。壁式充电器的一项新要求是与手机通信,通过改变电压或电流实现更快的充电。最常见的 AC/DC 拓扑结构是反激式和谐振式。反激式转换器具有成本最低的特点,但输出功率越高,磁性元件尺寸就越大。在这种情况下,谐振转换器是首选,尽管在低负载时效率较低。NXP 发明了一种谐振概念来解决这个问题。演讲将介绍上述AC/DC技术和NXP的产品优势。 安全移动 | 医疗保健和可穿戴设备
View full article
MPC5xxx I2C 通信驱动程序 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本文档总结了 MPC5xxx 设备的简单 I2C 驱动程序实现。 代码遵循参考手册的典型 I2C 中断程序流程图。 概述
View full article
DES-N1835 实践研讨会:使用 QorIQ LS 系列上的跟踪和性能工具调试和优化 Linux 应用程序的性能 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> QorIQ LS 系列的 CodeWarrior 开发套件包含各种用于分析多核 Linux 系统的操作和性能的工具。工具利用硬件跟踪和系统日志来监控操作和性能。CodeWarrior 开发套件包括使用 Hierarchical Profiler、Flat Profiler 和 CodeCoverage 进行性能分析的工具;使用 Timeline 和 CallTree 进行路径分析的工具;除了间隔分析之外,还使用 DebugPrint 和 TraceCommander 进行实时监控的工具。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> QorIQ LS 系列的 CodeWarrior 开发套件包含各种用于分析多核 Linux 系统的操作和性能的工具。工具利用硬件跟踪和系统日志来监控操作和性能。CodeWarrior 开发套件包括使用 Hierarchical Profiler、Flat Profiler 和 CodeCoverage 进行性能分析的工具;使用 Timeline 和 CallTree 进行路径分析的工具;除了间隔分析之外,还使用 DebugPrint 和 TraceCommander 进行实时监控的工具。 设计 | 软件与服务
View full article
MHW-N1907 NXP 智能天线解决方案 - 连接设备的射频前端解决方案 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 近几年来,联网设备的射频含量急剧增加。不断增长的带宽需求推动了射频链的要求达到更高的水平。NXP 智能天线解决方案的 RF MMIC 使连接设备的设计人员可以自由放置天线,同时实现更高的性能。本课程将展示日益增长的需求和复杂性以及恩智浦对这一挑战的回应。 观看视频演示 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 近几年来,联网设备的射频含量急剧增加。不断增长的带宽需求推动了射频链的要求达到更高的水平。NXP 智能天线解决方案的 RF MMIC 使连接设备的设计人员可以自由放置天线,同时实现更高的性能。本课程将展示日益增长的需求和复杂性以及恩智浦对这一挑战的回应。 观看视频演示 安全移动 | 医疗保健和可穿戴设备
View full article
NXP Technology Days 2015 - DWF Designing with Freescale January DwF Tel Aviv - 2015-01-27 DwF Kinetis MCUs Based on ARM® Technology - Shenzhen - 2015-01-27 DwF DwF Digital Networking - Shenzhen - 2015-01-28 March DwF Kinetis MCUs Based on ARM® Technology - Nanjing - 2015-03-12 DwF IoT Multicore Technologies and Enablement Software Solutions - Porto Alegre - 2015-03-19 DwF MCU and Automotive Solutions - Tianan - 2015-03-19 DwF Kinetis MCUs Based on ARM® Technology - Tianjin - 2015-03-19 DwF Silicon Valley - 2015-03-26 DwF MCU Solutions - Zhengzhou - 2015-03-31 April DwF RF Solutions - Chengdu - 2015-04-09 DwF Kinetis MCUs Based on ARM® Technology - Jinan - 2015-04-22 DwF IoT Wireless Module Solutions - Jinan - 2015-04-23 May DwF Kinetis and i.MX Solutions Based on ARM® Technology - Zhuhai - 2015-05-07 DwF Taipei - 2015-05-07 DwF Istanbul - 2015-05-12 DwF Ankara - 2015-05-14 DwF Digital Networking - Nanjing - 2015-05-21 DwF Kinetis MCUs Based on ARM® Technology - Wuhan - 2015-05-27 DwF IoT Wireless Module Solutions - Wuhan - 2015-05-28 June DwF Kinetis MCUs Based on ARM® Technology - Guangzhou - 2015-06-10 DwF IoT Wireless Module Solutions - Guangzhou - 2015-06-11 DwF Warsaw - 2015-06-18 DwF Shenzhen - 2015-06-25 DwF Kinetis MCUs Based on ARM® Technology - Xiamen - 2015-06-30 July DwF TechDay Toulouse - 2015-07-02 DwF Singapore - 2015-07-03 DwF RF Solutions - Quanzhou - 2015-07-07 DwF Shanghai - 2015-07-14 DwF Digital Networking - Fuzhou - 2015-07-21 DwF Kinetis MCUs Based on ARM® Technology - Suzhou - 2015-07-23 DwF Kinetis MCUs Based on ARM Technology - Wuxi - 2015-07-30 August DwF Hangzhou - 2015-08-05 DwF Digital Networking - Wuhan - 2015-08-12 DwF RF Solutions - Wuhan - 2015-08-13 DwF MCU and Automotive Solutions - Kaohsiung - 2015-08-14 DwF Automotive Solutions - Chongqing - 2015-08-19 DwF MCU Solutions Based on ARM® Technology - HCMC - 2015-08-26 September DwF Beijing - 2015-09-09 DwF Hsinchu - 2015-09-17 DwF Kinetis and i.MX Solutions Based on ARM® Technology - Changsha - 2015-09-22 DwF Detroit - 2015-09-23 October DwF Rochester - 2015-10-01 DwF Paris - 2015-10-01 DwF Kinetis and i.MX Solutions Based on ARM® Technology - Chengdu - 2015-10-14 DwF Digital Networking - Taipei - 2015-10-15 DwF Toronto - 2015-10-29 November DwF Ottawa - 2015-11-03
View full article
BAN-N1899 实践研讨会:4 小时内获得 EMVCo 对 NFC 支付终端的认可 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 任何支付解决方案,无论是移动销售点 (mPOS)、笔记本电脑、平板电脑、可穿戴设备还是嵌入式模块,都需要安全、可扩展且易于通过互操作性认证。本课程解释了非接触式 POS 终端设计的一般考虑因素,解决了最常见的挑战,例如 NFC 天线的尺寸和位置以及 EMVCo L1 模拟和数字兼容性。此外,还将解释最新的 NFC 控制器 PN5180 如何支持 PCI 要求。本次会议将概述恩智浦适用于支付应用的产品以及取决于物理终端设计和开发目标的选择标准。参与者将能够避免开发 NFC 支付终端过程中的常见障碍,从而降低设计风险并加快产品上市时间。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 任何支付解决方案,无论是移动销售点 (mPOS)、笔记本电脑、平板电脑、可穿戴设备还是嵌入式模块,都需要安全、可扩展且易于通过互操作性认证。本课程解释了非接触式 POS 终端设计的一般考虑因素,解决了最常见的挑战,例如 NFC 天线的尺寸和位置以及 EMVCo L1 模拟和数字兼容性。此外,还将解释最新的 NFC 控制器 PN5180 如何支持 PCI 要求。本次会议将概述恩智浦适用于支付应用的产品以及取决于物理终端设计和开发目标的选择标准。参与者将能够避免开发 NFC 支付终端过程中的常见障碍,从而降低设计风险并加快产品上市时间。 智能银行和智能零售
View full article
KSDK list of documents Documentation for current KSDK 1.3 is located under C:\Freescale\KSDK_1.3.0\doc Application Notes and another documents are located under Software Development Kit for Kinetis MCUs|NXP   There are more documents, which were created:   KSDK 2.0 How to: install KSDK 2.0 Introducing Kinetis SDK v2 Using Kinetis Design Studio v3.x with Kinetis SDK v2.0   KSDK 1.3 How to add SD card support in the composite msd_cdc demo[KSDK 1.3] KSDK Clock configurations and Low Power modes with Processor Expert New Kinetis SDK Project Generator v2 is available! KSDK Project Generator - BUG workaround KSDK 1.3 Documents Plugin in KDS - is available now! KSDK 1.3.0 Documents Plugin for KDS 3.0.0   KSDK 1.2 Interrupt handling with KSDK and Kinetis Design Studio Creating a New USB project with KSDK and Processor Expert support in KDS IAR MQX TAD solution for "Unknown error" in Task error code (with KSDK) How to Add lwIP to KDS3.0 Project How to: Create a New FreeRTOS for KSDK1.2 Project in KDS3.0 How to Create a C++ Project Using MQX RTOS for KSDK1.2 How to implement a USB Device MSD demo based on KSDK PEx components and KDS 3.0 How to: execute the demo HVAC on lwIP TCP/IP Stack in KSDK Kinetis SDK FAQ Adding TAD shell in KSDK shell demo FRDM-KL43Z and KL33Z - standalone package New KSDK 1.2. is available! Getting started with KSDK: Building the demo applications   KSDK 1.1 KSDK 1.1 Release How to create copy of KSDK example in KDS UART Example with KSDK   KSDK 1.0 Create new KSDK Projects Kinetis SDK and FRDM-K64F Sharing one documentation issue in KSDK 1.0 demo user guide General
View full article
美国 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 研讨会文件
View full article
都灵理工大学苏默里飞思卡尔杯队技术报告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 都灵理工大学 Sumery 队飞思卡尔杯技术报告 - 2015 年 EMEA 总决赛 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 都灵理工大学 Sumery 队飞思卡尔杯技术报告 - 2015 年 EMEA 总决赛
View full article
如何使用 KDS 和 KSDK 将 RTCS 添加到处理器专家项目 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 大家好, 根据如何:使用来自 macl 和 dereksnell 的 Kinetis Design Studio IDE 中的处理器专家为 KSDK 项目创建 MQX RTOS, 您可以在附件文档中找到使用 KSDK1.2 和处理器专家将 RTCS 包含到 KDS3.0 项目以及最终项目的步骤。 感谢RBORB提供此流程的初稿。 有关使用 MQX 而不使用 Processor Expert 创建新 KSDK 项目的信息,请参阅以下文档。 如何:在 KDS 中为 KSDK 项目创建新的 MQX RTOS 如果您正在寻找一份简单的文档来开始使用 KSDK,请参阅以下文档。 编写我的第一个KSDK1.2KDS3.0 中的应用 - Hello World 和使用 GPIO 中断切换 LED 此致, 卡洛斯 回复:如何使用KDS和KSDK将RTCS添加到处理器专家项目中 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我按照这个出色的教程,在基于 MK66FX1M0VLQ18 的定制硬件上开始了我的项目。 所有 KSDK 固件包(HAL 库、DRV 驱动程序和中间件)都与评估目标 FRDM-xxx 和 TWR-xxx 上提供的示例很好地集成在一起。但是(就像当我开始使用 CodeWarrior 10.1 和 MQX 3.7 处理 Kinetis CPU 时一样),移植在不同于评估板的目标上运行的 Kinetis 示例项目非常困难。此外,很难从用户位置的 KSDK 文件夹树导出自己的 Kinetis 项目。 MQX 4.0 附带 BSPCloningWizard 工具,这正是我一直想在我的定制硬件上启动新项目的工具。不幸的是,KSDK 还没有这样的工具。 所以,我认为从今天开始用 KDS 3.0.0 启动一个新的 Kinetis 项目+ PEx + KSDK 1.3.0 是定制硬件的最佳方式。Processor Expert 生成应用程序所需的 HAL、驱动程序和 MQX RTOS 的所有代码。并且该项目是在自定义文件夹中创建的,没有任何指向 KSDK 文件夹树的链接。精彩的! 如果我的项目需要处理 TCP/IP 堆栈和/或文件系统,通过本教程我可以将 RTCS 和/或 MFS 库添加到我的项目中。不幸的是,如何在我的定制硬件上移植和构建 RTCS 和 MFS 项目? 也许,Erich Styger 可以帮助我们...... 我在http://mcuoneclipse.com/2015/10/28/tutorial-lwip-with-the-freertos-and-the-freescale-frdm-k64f-board/上找到了他的教程,他用KDS+PEx+KSDK创建了一个项目,将lwIP源文件夹添加到他的项目中,并调整编译器设置的包含路径。 将 RTCS 和 MFS 源文件夹添加到项目中是解决在自定义硬件上移植和构建 RTCS 和 MFS 库的正确方法吗? 回复:如何使用KDS和KSDK将RTCS添加到处理器专家项目中 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 因为我有一块 FRDM-K64F 板,就像例子中描述的那样,所以这对我来说很有用。但我不清楚如何将这个过程转移到不同的目标板。如果有人没有 FRDM-K64F、TWR-K60D100M、TWR-K64F120M 或 TWR-K65F180M(四个具有导入路径的目标),那该怎么办?我的真正目标是使用 MK64FN1M0VLQ12,它与 FRDM-K64F相似,但肯定不匹配。 那么,在按照 PowerPoint 文件中的说明进行操作之前,如何为不同的硬件目标设置 RTCS 项目? 谢谢! 回复:如何使用KDS和KSDK将RTCS添加到处理器专家项目中 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 非常好的例子! 非常非常有用 - 10X。 我有时会观察到一个奇怪的现象: 即使 ETH 电缆断开,ETH phy led 仍指示链接(绿色 led)。 这可以避免 ETE 传递数据包。 仅在使用调试器时才观察到这一点' 所以我推测 PHY init 可能是原因。 我该怎么办? 回复:如何使用KDS和KSDK将RTCS添加到处理器专家项目中 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨,罗杰, 您可以在此处找到向当前 MQX-KSDK 和 PEx 项目添加 MFS 和 Shell 支持所需的步骤。如何为新的 MQX RTOS for KSDK 和 PEx 项目添加 MFS 和 Shell 支持 我希望这能对你有帮助, 顺祝商祺! 艾萨克 回复:如何使用KDS和KSDK将RTCS添加到处理器专家项目中 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨,罗杰, 是的,但是队列中还有许多其他项目,我们无法确定何时可以创建该文档。 带来不便敬请谅解。 卡洛斯 回复:如何使用KDS和KSDK将RTCS添加到处理器专家项目中 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好,卡洛斯 您有机会和您的团队交谈吗? 此致敬礼 罗杰 回复:如何使用KDS和KSDK将RTCS添加到处理器专家项目中 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 谢谢罗杰, 听起来不错,我会和我的团队讨论一下。 此致, 卡洛斯 回复:如何使用KDS和KSDK将RTCS添加到处理器专家项目中 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好,卡洛斯 该指南非常有帮助。 如果能有一个用于通过 SDCARD 添加 MFS 的功能就好了? 此致敬礼 罗杰 回复:如何使用KDS和KSDK将RTCS添加到处理器专家项目中 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨,罗杰, 您需要构建第一个 RTCS 库。对于 FRDM-K64,您可以在这里找到: C:\Freescale\KSDK_1.2.0\中间件\tcpip\rtcs\build\kds\rtcs_frdmk64f 我忘了在指南中提到这个要求。我会更新它。 此致, 卡洛斯
View full article
AN5200 - MPC55xx および MPC56xx にインプリメントされたエラー訂正コード この文書のリビジョン1が正式に公開されました。 https://www.nxp.com/docs/en/application-note/AN5200.pdf   関連するコード例は、こちら(AN5200SWに等しい)にも掲載されています。 例 1 - MPC5634M_2b_RAM_ECC_error_injection CW210 例 2 - MPC5674F_1b+2b_RAM_ECC_error_injection CW210 例3 - MPC5643L 1b_RAM_ECC_error_injection CW210 例 4 - MPC5643L 2b RAM と 2b FLASH ECC エラー挿入 CW210 例 5 - MPC5675K-2b_RAM+2b_FLASH_ECC_error_injection CW210 この文書のリビジョン1が正式に公開されました。 http://cache.freescale.com/files/microcontrollers/doc/app_note/AN5200.pdf http://cache.freescale.com/files/microcontrollers/doc/app_note/AN5200SW.zip   関連するコード例は、こちら(AN5200SWに等しい)にも掲載されています。 例 1 - MPC5634M_2b_RAM_ECC_error_injection CW210 例 2 - MPC5674F_1b+2b_RAM_ECC_error_injection CW210 例3 - MPC5643L 1b_RAM_ECC_error_injection CW210 例 4 - MPC5643L 2b RAM と 2b FLASH ECC エラー挿入 CW210 例 5 - MPC5675K-2b_RAM+2b_FLASH_ECC_error_injection CW210 日時: AN5200 - MPC55xx および MPC56xx に実装されたエラー修正コード <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 解決。コードは正しく実行されていますが、正しく実行されていませんでした。 問題はまったく異なっていました。私が(2回)ダウンロードしたところ、コードが破損していました。今日、もう一度ダウンロードすると、実行されているのがわかりました。次に、SSDを使用してコードをアプリケーションに変換します。今はあらゆることがうまくいっています。私はExceprion_Handlers壊れたフラッシュブロックを修正したかったのですが、それはうまくいきます。 ありがとうございます。 日時: AN5200 - MPC55xx および MPC56xx に実装されたエラー修正コード <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 2b ECCエラーインジェクションについて話しているのか(6.2章と例で説明されているため、機能Generate_noncorrectable_FLASH_ECC_errorで示されているMPC5643L)、またはフラッシュメモリコントローラに実装された特定のECCエラー報告フラグ(EER)に関連しているのかはわかりません。私はこれらのフラグを冗長だと考えているため、アプリケーションノートでは言及していません。また、簡単にするためにSSDドライバーを使用していませんが、SSDドライバーでECCエラーを注入することはでき、原理は同じです。 日時: AN5200 - MPC55xx および MPC56xx に実装されたエラー修正コード <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、ドキュメントがあまりありません。ご態度ありがとうございます。 MPC5634M、CW10.2、SSD C90LCを使用しています。フラッシュを過度にプログラムすると、EERが発生する可能性があります。MPC56XX_C90LC_JDP_SSD_100_DEVD またはECC_preliminaryで破棄された例は、e200z335 コアで EER をシミュレートしていません。または、(プロジェクト内に)欠落しているファイルがあるか、これを行うための実用的なルーチンがありません(SSDドライブ内)。 もしお役に立てれば...
View full article