Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
使用 Processor Expert 为 IAR 生成代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 附件文档展示了如何使用 Processor Expert Driver Suit 为 IAR 生成代码。您可以在幻灯片底部的注释中看到详细信息。 顺祝商祺! 卡洛斯
View full article
Implementing infrared functions on UART0 with FRDM-KE02Z platform. This document shows the implementation of the infrared on the UART0 using the FRDM-KE02Z platform. The FRDM-KE02Z platform is a developing platform for rapid prototyping. The board has a MKE02Z64VQH2 MCU a Kinetis E series MCU which is the first 5-Volt MCU built on the ARM Cortex-M0+ core. You can check the evaluation board in the Freescale’s webpage (FRDM-KE02Z: Kinetis E Series Freedom Development Platform) The Freedom Board has a lot of great features and one of this is an IrDA transmitter and receiver on it. Check this out! One of the features of the MCU is that the UART0 module can implement Infrared functions just following some tricks (MCU-magic tricks). According to the Reference Manual (Document Number: MKE02Z64M20SF0RM) this tricks are:      UART0_TX modulation: UART0_TX output can be modulated by FTM0 channel 0 PWM output      UART0_RX Tag: UART0_RX input can be tagged to FTM0 channel 1 or filtered by ACMP0 module For this example we are going to use the ACMP0 module to implement the UART0_RX functionality. Note1: The Core is configured to run at the maximum frequency: 20 Mhz Note2: Refer to the reference manual document for more information about the registers. Configuring the FTM0. The next lines show the configuration of the FTM0; the module is configured with a Frequency of 38 KHz which is the ideal frequency for an infrared led. The FTM0_CH0 is in Edge_Aligned PWM mode (EPWM).           #define IR_FREQUENCY       38000 //hz      #define FTM0_CLOCK                BUS_CLK_HZ      #define FTM0_MOD_VALUE            FTM0_CLOCK/IR_FREQUENCY      #define FTM0_C0V_VALUE            FTM0_MOD_VALUE/2      void FTM0CH0_Init( void )      {        SIM_SCGC |= SIM_SCGC_FTM0_MASK;             // Init FTM0 to PWM output,frequency is 38khz        FTM0_MOD= FTM0_MOD_VALUE;        FTM0_C0SC = 0x28;        FTM0_C0V = FTM0_C0V_VALUE;        FTM0_SC = 0x08; // bus clock divide by 2      } With this we accomplish the UART0_TX modulation through a PWM on the FTM0_CH0. Configuring the ACMP0. The configuration of the ACMP0 is using a DAC and allowing the ACMP0 can be driven by an analog input.      void ACMP_Init ( void )      {        SIM_SCGC |= SIM_SCGC_ACMP0_MASK;        ACMP0_C1 |= ACMP_C1_DACEN_MASK |                   ACMP_C1_DACREF_MASK|                   ACMP_C1_DACVAL(21);    // enable DAC        ACMP0_C0 |= ACMP_C0_ACPSEL(0x03)|                            ACMP_C0_ACNSEL(0x01);        ACMP0_C2 |= ACMP_C2_ACIPE(0x02);  // enable ACMP1 connect to PIN        ACMP0_CS |= ACMP_CS_ACE_MASK;     // enable ACMP                } With this we have now implemented the UART0_RX.     IrDA initialization. Now the important thing is to initialize the UART0 to work together with these tricks and implement the irDA functions. Basically we initialize the UART0 like when we use normal serial communication (this is not the topic of this post, refer to the project to see the UART_init function) and we write to the most important registers:         SIM_SOPT |= SIM_SOPT_RXDFE_MASK; UART0_RX input signal is filtered by ACMP, then injected to UART0.      SIM_SOPT |= SIM_SOPT_TXDME_MASK; UART0_TX output is modulated by FTM0 channel 0 before mapped to pinout. The configuration is as follows:      void IrDA_Init( void )      { // initialize UART0, 2400 baudrate        UART_init(UART0_BASE_PTR,BUS_CLK_HZ/1000,2400);                  // clear RDRF flag        UART0_S1 |= UART_S1_RDRF_MASK;                  // initialize FTM0CH1 as 38k PWM output        FTM0CH0_Init();                      // enable ACMP        ACMP_Init(); SIM_SOPT |= SIM_SOPT_RXDFE_MASK;  //UART0_RX input signal is filtered by ACMP, then injected to UART0.        UART0_S2 &= ~UART_S2_RXINV_MASK;  //inverse data input SIM_SOPT |= SIM_SOPT_TXDME_MASK;  //UART0_TX output is modulated by FTM0 channel 0 before mapped to pinout.      } With the irDA initialization we got the infrared features on the UART0. Philosophy of the Example In the attachments of this post you can find the example which shows the use of these functions in a basic application; the project was compiled in CodeWarrior 10.6 and the philosophy is: I hope that the information presented on this document could be useful for you. Thank you! Best Regards! Freedom Development Platform Kinetis E Series MCUs Re: Implementing infrared functions on UART0 with FRDM-KE02Z platform. I figured out what was the problem. The TWR-K60 has a different IR receiver filter with R=1KOhm and C=0.1uF, which passes frequencies less than 1.6KHz compared to the FRDM-KE02Z which has R=1KOhm and C=1000PF, which will passes frequencies less than 160KHz, hence 38KHz is OK for that board. 38KHz wont work with TWR-K60N512 because it wi ll be blocked by the filter. I set the UART0 baud lower to 1400 and the FTM1 frequency to 1.5KHz and it works like a charm! I compared the two user manuals 🙂 Formula: fc = 1/(2*pi*Τ) = 1/(2pi*RC); where R=1000Ohms, C=0.1*10^-6Farads fc = 1.6KHz Re: Implementing infrared functions on UART0 with FRDM-KE02Z platform. I got it to work without FTM modulation, just with the 3/16 narrow pulse. UART0 configured with 2400 baudrate and inverted RX, CMP DAC Output voltage select is (Vin/64)*31+1 = VDD(3.3v) * 0.5 = 1.65V for a high(1), supply voltage select is 1 for Vin2 which is VDD (3.3v). The trick is to configure the Comparator properly with a good reference voltage on the inverting input. I did not configure any sampling. Next I will try with FTM modulation, only I dont know how exactly to demodulate on the comparator end using the sampling feature. Re: Implementing infrared functions on UART0 with FRDM-KE02Z platform. I am trying this with the TWR-K60N512 KIT, I can receive interrupts on UART0_Rx through Comparator from a TV remote signal, but not from the Tx pin although checking with a smartphone camera, the Tx IR signal is going on. The code is as follows: #include "types.h" #include "infrared.h" #define IR_FREQUENCY    38000 #define FTM1_CLOCK        750000 #define FTM1_MOD_VALUE    FTM1_CLOCK/IR_FREQUENCY #define FTM1_C0V_VALUE            FTM1_MOD_VALUE/2‍‍‍‍‍‍ void init_infrared(void){     //initialize uart0 as infrared port through CMP0     init_uart0();     //initialize Comparator     init_cmp0();     //initialize the Flex timer     init_ftm(); }‍‍‍‍‍‍‍‍ void init_uart(UART_MemMapPtr uartch, int sysclk, int baud){     uint16_t ubd, temp, brfa;    //disable Tx and Rx during setup     UART_C2_REG(uartch) &= ~(UART_C2_TE_MASK | UART_C2_RE_MASK );     /* Configure the UART for 8-bit mode, no parity */     /* We need all default settings, so entire register is cleared */     UART_C1_REG(uartch) = 0;     /* Calculate baud settings */     ubd = (uint16_t)((sysclk*1000)/(baud * 16));     /* Save off the current value of the UARTx_BDH except for the SBR */     temp = UART_BDH_REG(uartch) & ~(UART_BDH_SBR(0x1F));     UART_BDH_REG(uartch) = temp | UART_BDH_SBR(((ubd & 0x1F00) >> 8));     UART_BDL_REG(uartch) = (uint8_t)(ubd & UART_BDL_SBR_MASK);     /* Determine if a fractional divider is needed to get closer to the baud rate */     brfa = (((sysclk*32000)/(baud * 16)) - (ubd * 32));     /* Save off the current value of the UARTx_C4 register except for the BRFA */     temp = UART_C4_REG(uartch) & ~(UART_C4_BRFA(0x1F));     UART_C4_REG(uartch) = temp | UART_C4_BRFA(brfa);     // enable the reciever interrupts     UART_C2_REG(uartch) |= UART_C2_RIE_MASK; }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ void init_uart0(void){     //Gate clock to uart0       SIM_SCGC4 |= SIM_SCGC4_UART0_MASK;     init_uart(UART0_BASE_PTR,96000,2400);//core clock is 96Mhz=96000Khz     //enable IR encoding and decoding     UART0_IR |= UART_IR_IREN_MASK;     UART0_IR |= UART_IR_TNP(0x0);//narrow pulse 3/16 of baudrate     //System integration to route UART0_RX to CMP0     SIM_SOPT5 |= SIM_SOPT5_UART0RXSRC(01);//CMP0 as source of UART0_RX     SIM_SOPT5 |= SIM_SOPT5_UART0TXSRC(01);//Tx pin modulated with FTM1 channel0 output     SIM_SOPT2 |= SIM_SOPT2_CMTUARTPAD_MASK;//select dual pad drive strength for UART0_TX     //Enable receiver and transmitter     UART0_C2 |= UART_C2_RE_MASK;     UART0_C2 |= UART_C2_TE_MASK;     // configure Nested Vector Interrupt Controller: clear pending and set enable     NVICICPR1 |= interrupt_mask(1,INT_UART0_RX_TX);     NVICISER1 |= interrupt_mask(1,INT_UART0_RX_TX); }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ //UART0 brief interrupt handler void UART0_RX_TX_IRQHandler(){     if((UART0_S1 & UART_S1_RDRF_MASK)==UART_S1_RDRF_MASK){         byte2 = (uint8_t)UART0_D;         data_available2=1;     } }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ //FTM1 initialization, used to modulate UART0_TX void init_ftm(void){     SIM_SCGC6 |= SIM_SCGC6_FTM1_MASK;//gate the clock     FTM1_SC |= FTM_SC_CLKS(01);//system core clock as clock source     FTM1_SC |= FTM_SC_PS(7);//divide system clock by 128 = 750Khz     FTM1_MODE |= FTM_MODE_WPDIS_MASK;//disable write protect     FTM1_MOD |= FTM_MOD_MOD(FTM1_MOD_VALUE);//modulo value     FTM1_C0SC = 0x28;//edge-aligned PWM     FTM1_C0V = FTM1_C0V_VALUE; }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ void init_cmp0(void){     //gate the clock to CMP     SIM_SCGC4 |= SIM_SCGC4_CMP_MASK;     //disable comparator while configuring     CMP0_CR1 &= ~(CMP_CR1_OPE_MASK | CMP_CR1_EN_MASK);     //Configure and enable the Comparator's DAC for reference voltage     CMP0_DACCR |= CMP_DACCR_VRSEL_MASK;//supply voltage select is 1 for Vin2     CMP0_DACCR |= CMP_DACCR_VOSEL(0x0F);//Output voltage select is (Vin/64)*VOSEL+1 = Vin * 0.5 for a high(1)     CMP0_DACCR |= CMP_DACCR_DACEN_MASK;     //enable PMUX and MMUX     CMP0_MUXCR |= CMP_MUXCR_PEN_MASK | CMP_MUXCR_MEN_MASK;     //select IN0 for PMUX(positive side) and DACOUT i.e channel 7 as MMUX(minus side)     //          |\     //    IN0---|+\     //          |  \______CMP_OUT     //          |  /     // DACout---|-/     //          |/     //         COMPARATOR     //     CMP0_MUXCR |= CMP_MUXCR_PSEL(0);     CMP0_MUXCR |= CMP_MUXCR_MSEL(7);     //set 0 samples per measurement     CMP0_CR0 |= CMP_CR0_FILTER_CNT(0x0);//disable filter     CMP0_CR1 |= CMP_CR1_COS_MASK;//unfiltered output     CMP0_CR1 |= CMP_CR1_INV_MASK;//invert output     //enable comparator and the output pin     CMP0_CR1 |= (CMP_CR1_OPE_MASK | CMP_CR1_EN_MASK); }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I think I am missing some information on how the modulation actually works. Could you please explain a little further on the actual protocol, how the timing diagrams look like, how do we demodulate, where are the UART settings for demodulation, i can see how we modulate with the FTM, but not how we are actually demodulating the received signal. Is it by sampling the CMP input? BlackNight‌ you have any ideas? Re: Implementing infrared functions on UART0 with FRDM-KE02Z platform. Hello Sanchez,           A good post indeed. But, I was wondering what might be the communication pattern? Is it a standard 3/16th bit width communication or the modulated Tx waveform looks different altogether? Couldn't capture on oscilloscope as the FTM is running continuously. Is the modulated waveform similar to the one attached?
View full article
FRDM-MK64ボードを使用して、KDSのSDカードに加速度計データを書き込む <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KDSのSDカードへの加速度計データの書き込み   形容:   KDS で FRDM-MK64FN1MOVLL12 ボードを使用して Accelerometer データを SD カードに書き込むプロジェクト。 加速度計から取得した変数x、y、zの時間と値が毎秒SDカードに書き込まれます。 これらはlog.txtファイルに書き込まれ、存在しない場合は作成されます。 書き込み中は、LEDが毎秒緑色に点滅します。 エラーが発生した場合、LCDは毎秒赤く点滅します。   http://mcuoneclipse.com/2014/05/26/tutorial-data-logger-with-the-frdm-k64f-board/ から取得したコードのセクション   問題:   フラッシュ後、時間は常に17:51:31から始まります。 これは、TmDt1_Initでそのように設定されているためです。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KDSのSDカードへの加速度計データの書き込み   形容:   KDS で FRDM-MK64FN1MOVLL12 ボードを使用して Accelerometer データを SD カードに書き込むプロジェクト。 加速度計から取得した変数x、y、zの時間と値が毎秒SDカードに書き込まれます。 これらはlog.txtファイルに書き込まれ、存在しない場合は作成されます。 書き込み中は、LEDが毎秒緑色に点滅します。 エラーが発生した場合、LCDは毎秒赤く点滅します。   http://mcuoneclipse.com/2014/05/26/tutorial-data-logger-with-the-frdm-k64f-board/ から取得したコードのセクション   問題:   フラッシュ後、時間は常に17:51:31から始まります。 これは、TmDt1_Initでそのように設定されているためです。 全般
View full article
i.MX31 PDK Board V4L tests Video Unit Test The BSP provides a package that allows testing of several i.MX 31 peripherals on the PDK. The name of this package is 'imx-test'.   The name of the package may vary according to SDK release, at the time of the writing SDK 1.4 was used, on SDK 1.2 the name of a similar package was 'mxc-misc'   For more information on the imx-test package refer to the SDK 1.4 manual, imx31_Linux_RM.pdf, chapter 49 - Unit Tests. This file is available on BSP tarball Testing To test the image sensor and the display on the PDK follow the steps below: Enable imx-test and util-linux packages: $ ./ltib -c Once "ltib" finishes boot the system. On the target board: $ modprobe mxc_v4l2_capture Check if /dev/video0 was created $ ll /dev/video* lrwxrwxrwx  1 root root            6 Jan 1 20:47 /dev/video -> video0 crw-rw----     1 root root    81,   0 Jan 1 20:47 /dev/video0 crw-rw----     1 root root    81, 16 Jan 1 20:46 /dev/video16 Now run the unit tests: $./mxc_v4l2_overlay.out -iw 640 -ih 480 -ow 480 -oh 640 -r 4 -fr 30 -t 10 - capture images with the sensor and display on the LCD $./mxc_v4l2_capture.out -w 640 -h 480 -r 0 -c 150 -fr 30 test3.yuv - capture images and save on /unit-tests/test3.yuv $./mxc_v4l2_output.out -iw 640 -ih 480 -ow 480 -oh 640 -d 4 -fr 60 test3.yuv - capture images and save on /unit-tests/test3.yuv   For usage syntax type: command -help. ./mxc_v4l2_output.out -help Source Code If you want to check the source code, on the host machine "ltib" install path type: $./ltib -m prep -p imx-tests Then, go to /rpm/BUILD/imx-test-2.3.2/test/mxc_v4l2_test
View full article
适用于 CodeWarrior Power Architecture 的 Aurora Trace <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
Exercise 4: Kinetis Random Number Generator To do: The development platform is Eclipse. The EVAL Board is the Kinetis Tower TWR K60. On the Tower, you find 2 pushbuttons and 4 LEDs. a) Generate a hexadecimal random number from 0x0 to 0xF as long as pushbutton1 is pressed. Display the result with the 4 LEDs for about 3 seconds. b) Replace the code for recognizing a pressed key by a macro "KEY1_PRESSED". c) Replace the access to the 4 LEDs by a macro "LEDx_TOGGLE" with x = 0...3". Use active wait loops instead of the timer in this Kinetis exercise. Result: TWR_K60_RANDOM.zip
View full article
フリーマスター - TSA <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> FreeMASTER TSA(Target Side Address translation)の機能を説明するチュートリアルビデオです。   音楽: Bensbound (マイビデオで視聴)
View full article
フローティングライセンスサーバーデーモン - Hiware <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Re:フローティングライセンスサーバーデーモン - Hiware <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ザ  lmgrd  daemon とベンダーデーモンは連携してライセンスキーを管理します。  lmgrd  デーモンは、クライアント・アプリケーション・プログラムとの最初の接続を処理し、接続を適切なベンダー・デーモンに渡します。  lmgrd  デーモンは、ベンダーデーモンも起動および再起動します。
View full article
Floating License server daemon - Hiware Re: Floating License server daemon - Hiware The  lmgrd  daemon and the vendor daemons work together to manage the license keys. The  lmgrd  daemon handles the initial contact with the client application programs, passing the connection on to the appropriate vendor daemon. The  lmgrd  daemon also starts and restarts vendor daemons.
View full article
KDS で FRDM-KL25 ボードを USB マウスとして使用する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KDSのUSBマウス   形容:   KDS で FRDM-KL25Z128M4 ボード上の加速度計を使用して USB マウス入力を制御するプロジェクト。 USBマウスとして接続されていないときはLEDが赤く点滅し、接続されている場合は緑色に点滅します。 リセットボタンは左クリックします。   マウスの感度は、main.cのHIDM1_Moveコマンドを変更することで変更できます リセットボタンは、main.cのコメントを変更することにより、左クリックから右クリックに変更できます   コードのセクションは、以下から取得されます。 - http://mcuoneclipse.com/2012/09/21/tutorial-accelerating-the-kl25z-freedom-board/ - http://mcuoneclipse.com/2013/08/01/using-the-frdm-kl25z-as-a-usb-mouse-device/ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KDSのUSBマウス   形容:   KDS で FRDM-KL25Z128M4 ボード上の加速度計を使用して USB マウス入力を制御するプロジェクト。 USBマウスとして接続されていないときはLEDが赤く点滅し、接続されている場合は緑色に点滅します。 リセットボタンは左クリックします。   マウスの感度は、main.cのHIDM1_Moveコマンドを変更することで変更できます リセットボタンは、main.cのコメントを変更することにより、左クリックから右クリックに変更できます   コードのセクションは、以下から取得されます。 - http://mcuoneclipse.com/2012/09/21/tutorial-accelerating-the-kl25z-freedom-board/ - http://mcuoneclipse.com/2013/08/01/using-the-frdm-kl25z-as-a-usb-mouse-device/ 全般 日時:KDSでFRDM-KL25ボードをUSBマウスとして使用する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Bluetooth to UARTモジュールで可能になる場合があります。しかし、私はこの分野での経験がないことを認めます。 日時:KDSでFRDM-KL25ボードをUSBマウスとして使用する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Bluetoothを使用するように、つまり付属のデバッグケーブルを使用せずにボードを適応させることは可能ですか?
View full article
RDS12VR: Anti-Pinch Window Lift Reference Design Overview Features Block Diagram Design Resources Overview NXP® and Tongji University jointly developed the anti-pinch window lift reference design featuring the MagniV® S12VR MCU, ideal for the development of power windows and sun roof systems. Includes hardware for real door/window in-vehicle applications, as well as software including anti-pinch algorithms and low-level S12VR drivers Aimed at reducing time to market, this design leverages unique features of the MagniV S12VR MCU Reduces unnecessary external components, lowers the total bill of material (BOM), improves system quality and saves space in automotive applications through a smaller PCB Features Window manual/automatic up/down, automatic up/down with stop function Anti-pinch in both manual/automatic mode, anti-pinch region and force can be adjusted Stuck detection out of anti-pinch region, motor overload protection Soft stop when window is close to the top/bottom Fault diagnosis, indicating low voltage, over voltage/current/temperature etc. Low power mode (leveraging S12VR low power mode) to reduce power consumption Self learning, calibration by updating the window/motor parameters stored in EEPROM Use hall sensor as well as current sense to judge anti-pinch in algorithm Easy-to-control Graphics User Interface (GUI), set the parameters and get the status Window lift can be controlled either by multiple LIN salve nodes or LIN master node (through GUI) Able to comply with relevant content in US Federal Motor Vehicle Safety Standard (FMVSS No. 118) Block Diagram Design Resources Legacy Designs
View full article
ヨーロッパにおけるeID文書の進化 このセッションでは、ヨーロッパにおけるeID文書と規制の進化について説明します。 このセッションでは、ヨーロッパにおけるeID文書と規制の進化について説明します。 識別とセキュリティ
View full article
産業用およびネットワーキングアプリケーション向けのLayerscapeマイクロプロセッサポートフォリオ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> エッジコンピューティングアプリケーションについて学習し、ゲートウェイとセキュリティを「管理」するための技術的な課題、クラウドサービスのコンテキストでEdgeScaleフレームワークを含むLayerscapeマイクロプロセッサソリューションを示します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> エッジコンピューティングアプリケーションについて学習し、ゲートウェイとセキュリティを「管理」するための技術的な課題、クラウドサービスのコンテキストでEdgeScaleフレームワークを含むLayerscapeマイクロプロセッサソリューションを示します。 Layerscape処理プラットフォーム
View full article
Enabling SD Interface on P1024 Reference Design Board To enable SD interface in SPI boot on p1024RDB: 1. Perform the following updates in u-boot a) Modify pmuxcr to enable SD bus in case of SPI boot b) Update the corresponding static mux implementation in u-boot 2. Perform the following updates in Linux a) Disable IFC from device tree and kernel defconfig The patch details to enable SD interface are given below. A zip file, AN4336SW.zip, containing the patches for u-boot and Linux accompanies this application note. The file can be downloaded from [1]. U-Boot   Extract the u-boot code from the QorIQ SDK 1.0.1 iso   Apply the patch, u-boot-p1024rdb-enabling-sd-in-spi-boot.patch   Compile the u-boot using "make" command for SPI Flash    make ARCH=powerpc   CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu- p1024RDB_SPIFLASH   Use the boot_format utility to generate the spiimage. For more information, see SDK manual.   Update the SPI Flash with the above built spiimage Linux Extract the Linux source code from QorIQ SDK 1.0.1 iso Apply the patch, linux-p1024rdb-enabling-sd-in-spi-boot.patch Compile Linux using make command #make ARCH=powerpc  CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnuarch/  powerpc/configs/qoriq_sdk_nonsmp_defconfig  #make ARCH=powerpc  CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu- Compile the dts ./sripts/dtc/dtc -f -I dts -O dtb -R 8 -S 0x3000  arc/powerpc/boot/dts/p1024rdb.dts.dts > p1024rdb.dtb.dtb With the updated SPI bootloader, Linux uImage and p1024rdb.dtb, the user must be able to enable SD interface on P1024RDB. NOTE The above-mentioned changes must be done only when the user specifically requires the SD interface using SPI boot. For all other boot methods, these patches must not be used. QorIQ P1 Devices
View full article
使用 Sigfox 发送 GPS 坐标 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 该视频展示了如何使用 Sigfox OL2385 开发板获取 GPS 坐标并将其发送到互联网 (在 “我的视频” 中查看) 智慧城市
View full article
功率和效率增强的 5G mMIMO 模块 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 完整系列的多功能放大器模块可快速部署基站,满足 5G 无线基础设施设备的超低延迟/高数据速率需求。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 完整系列的多功能放大器模块可快速部署基站,满足 5G 无线基础设施设备的超低延迟/高数据速率需求。 接口和连接
View full article
RDDSP56F8SRDS: 3-Phase SR Motor Sensorless Control Reference Design using 56F80X or 56F8300 DSCs Overview Features Block Diagram Board Design Resources Overview The reference design demonstrates sensorless control of the 3-Phase Switched Reluctance (SR) motor using 56F80x or 56F83XX Digital Signal Controllers. It can also be adapted to 56F81XX Digital Signal Controllers. The concept of this application is that of a sensorless speed closed loop SR drive using flux linkage position estimation. An inner current loop with PI controller is included. The change in phase resistance during motor operation due to its temperature dependency creates errors in the position estimation and significantly affects the performance of the drive. Therefore, a novel algorithm for on-the-fly estimation of the phase resistance is included. The Digital Signal Controller runs the main control algorithm. Rotor position is evaluated using the sensorless flux linkage estimation algorithm. The actual flux linkage is calculated at the rate of the PWM frequency and is compared with the reference flux linkage for a given commutation angle. When the actual flux linkage exceeds the reference, the commutation of the phases is done; the actual phase is turned off and the following phase is turned on. Flux linkage error is used for estimation of the phase resistance at low speeds (US Patent No.: 6,366,865). The actual speed of the motor is determined using the commutation instances. Based on the speed error, the speed controller generates the desired phase current. When the phase is commutated, it is turned on with a duty cycle of 100%. Then, during each PWM cycle, the actual phase current is compared with the desired current. As soon as the actual current exceeds the desired current, the current controller is turned on. The current controller controls the output duty cycle until the phase is turned off (following commutation). Finally, the 3-Phase PWM control signals are generated. The procedure is repeated for each commutation cycle of the motor. Features Sensorless control of an SR motor using a flux linkage estimation technique Targeted for 56F80X, 56F83XX, and 56F81XX Digital Signal Controllers Running on a 3-Phase SR HV Motor Control Development Platform The control technique: current control with a speed closed loop Position estimation based on flux linkage estimation Phase resistance measurement during start-up Phase resistance estimation at low speeds Motor starts from any position with rotor alignment Encoder position reference for evaluation of sensorless position estimation Manual interface FreeMASTER software control interface and monitor Fault protection Block Diagram Board Design Resources Legacy Designs
View full article
これで、構成セクションにコンポーネントセクションを要求できるようになりました <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 以前は、設定セクションは設定セクションのみを必要とすることができましたが、現在は設定に設定とコンポーネントを要求できるようになりました。 この新機能により、一部のコンポーネントセクションが一部のボード/キットのすべてのアプリケーションで一般的に必要とされる場合、ユーザーはこのボード/キットの共通の設定セクションを使用して、すべてのymlファイルの「__hierachy__」でそれらを維持するのではなく、それらを要求できるため、保守の労力を大幅に節約できます。 Re:現在、構成セクションにはコンポーネントセクションが必要です <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ケイト、何か例を挙げていただけますか?
View full article
ミニモンキーレブB 基板付:NG <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Mini-Monkeyの設計を更新し、PCB:NGを使用して製作しました。 (マイビデオで視聴)
View full article
驾驶体验:i.MX 8/8X 多媒体——图形、显示控制器、视觉、机器学习 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> i.MX 为多媒体和显示应用提供了一些最通用的平台。加入此会议,深入了解 i.MX 8/8X 的多媒体系统(包括 GPU、显示器、视觉、虚拟化和机器学习)如何协同工作,为客户提供一套可扩展的强大汽车信息娱乐媒体功能。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> i.MX 为多媒体和显示应用提供了一些最通用的平台。加入此会议,深入了解 i.MX 8/8X 的多媒体系统(包括 GPU、显示器、视觉、虚拟化和机器学习)如何协同工作,为客户提供一套可扩展的强大汽车信息娱乐媒体功能。
View full article