Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
ホバーゲームズチャレンジ1 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> フライヤーで消火活動 人為的なものであれ、自然的なものであれ、火災を予測し制御することは困難です。火災は数十億ドルの損害をもたらし、町や森林全体を破壊し、最前線のファーストレスポンダーを含む無数の命を危険にさらしています。 HOVERGAMESはあなたの助けになる機会です このコンテストの目的は、HoverGamesのドローンが、山火事から都市火災まで、想像できるあらゆる方法で消防士の職務を支援できるソリューションを構築することです。NXP HoverGamesドローン 開発キットには、飛行ロボットの開発を開始するために必要なものがすべて含まれています。 HoverGamesのドローンで何ができるのか? あなたのドローンは消防チームの調整に役立っていますか?物資を届けたり、通信ネットワークや物流ネットワークを手の届きにくい地域に拡張したりしていますか?燃えている建物をスキャンしてホットスポットを特定しますか?それとも、火災が発生する前に検出して防ぐのでしょうか? ブレインストーミングを始めるために、いくつかのアイデアをご紹介します。 連絡が届きにくいエリアへの通信の拡大 ホットスポットのピンポイント 新たな火災と潜在的な再起動を監視する リソース、動物、危険にさらされている人々を追跡および監視する 誰かを荒野から導き出す 状況認識に関する洞察を提供する 閉じ込められた人に、ガスマスクや照明弾、CBラジオなどのリソースを届ける ドローンへの許可されたアクセスのみを許可する ドローンオペレーターの特定と承認 そのエリアにいてはいけない他のドローンを特定します チャレンジ1「フライヤーで火事と戦う」
View full article
The Next Wave of Industrial Networking with Time Sensitive Networking (TSN) Industrial OEMs have been hampered by the large array of networking protocols that they need to support in their devices. The new IEEE Time Sensitive Networking (TSN) standard offers to consolidate multiple proprietary protocols with a common IEEE based standard. Come learn what you can achieve with TSN. Industrial OEMs have been hampered by the large array of networking protocols that they need to support in their devices. The new IEEE Time Sensitive Networking (TSN) standard offers to consolidate multiple proprietary protocols with a common IEEE based standard. Come learn what you can achieve with TSN.
View full article
扩展资源域控制器 xRDC <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32x 设备的扩展资源域控制器概述。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32x 设备的扩展资源域控制器概述。
View full article
Dropbox 入门.pdf <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
KL25Z和传感器融合 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 全部, 附件是根据 Andrew Hartnett 的帖子而编写的。它包含用于 KL25Z 上的 9 轴传感器融合 V7.00 的裸机 IAR 项目。您需要为 KL25Z 构建 KSDK 以包含 ISSDK 选项。然后将此文件解压缩到您的 SDK_2.0_FRDM-KL25Z/boards 中目录。示例项目位于 SDK_2.0_FRDM-KL25Z/boards/frdmkl25z_virtual_shield/issdk_examples/algorithms/sensorfusion/baremetal_sensor_fusion/iar。 其中还包含一个 freertos_sensor_fusion 项目。暂时忽略这一点。它可以编译和链接,但需要比 KL25Z 提供的更多的 RAM。我正在寻找降低 RAM 要求的方法。 此致, Mike <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 全部, 附件是根据 Andrew Hartnett 的帖子而编写的。它包含用于 KL25Z 上的 9 轴传感器融合 V7.00 的裸机 IAR 项目。您需要为 KL25Z 构建 KSDK 以包含 ISSDK 选项。然后将此文件解压缩到您的 SDK_2.0_FRDM-KL25Z/boards 中目录。示例项目位于 SDK_2.0_FRDM-KL25Z/boards/frdmkl25z_virtual_shield/issdk_examples/algorithms/sensorfusion/baremetal_sensor_fusion/iar。 其中还包含一个 freertos_sensor_fusion 项目。暂时忽略这一点。它可以编译和链接,但需要比 KL25Z 提供的更多的 RAM。我正在寻找降低 RAM 要求的方法。 此致, Mike 传感器融合 回复:KL25Z和传感器融合 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 全部, 我能够启动并运行 FreeRTOS 版本。以下是您需要了解的内容: 根据裸机说明仅针对 1 种算法进行编译 FreeRTOSConfig.h 中的“#define configMINIMAL_STACK_SIZE ((unsigned short)256)” 替换 FreeRTOS heap_4.c使用 heap_3.c(FreeRTOS 有几种内存分配选项) 将 MKL25Z128xxx4_flash.lcf 中的 __size_heap__ 的值从 0x400 更改为 0x1000。 尽情享受! Mike
View full article
Sensors Overview
View full article
FlexIO USB Video Camera Demo This demo shows how the FRDM-K82F board along with an OV7670 Camera module can be utilized to create a USB web camera application. The demo application software is delivered as part of the KSDK software enablement. The FS USB video class demonstration can deliver images to PCs or tablets. Features: USB Video device class demonstration application included in Kinetis SDK Easy connection to PC or tablet  display and process video captured from the device FlexIO camera driver utilized to interface to OV7670 camera module _______________________________________________________________________________________________________ Featured NXP Products: ARM Cortex-M4 Cores|Kinetis K8x MCUs|NXP AN5275: Using FlexiO for Parallel Camera Interface AN5280: Using Kinetis FlexIO to drive a Graphical LCD _______________________________________________________________________________________________________ Mobile
View full article
LAT-HMB-T2459 - 未来电子:设计时考虑安全性 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 当今的设计师面临着越来越大的挑战,需要保护他们的知识产权和产品免遭假冒或未经授权的访问。为了帮助理解 NXP 提供的安全解决方案,未来的系统设计中心设计了一个安全访问演示板,以展示集成安全性的微控制器 LPC43S57 和 A700X 防篡改安全 MCU 解决方案的功能。本课程将概述安全系统的架构并介绍 NXP 的安全元素。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 当今的设计师面临着越来越大的挑战,需要保护他们的知识产权和产品免遭假冒或未经授权的访问。为了帮助理解 NXP 提供的安全解决方案,未来的系统设计中心设计了一个安全访问演示板,以展示集成安全性的微控制器 LPC43S57 和 A700X 防篡改安全 MCU 解决方案的功能。本课程将概述安全系统的架构并介绍 NXP 的安全元素。
View full article
NET-N1867 ツールとアイデアによるイノベーションの実現 – QorIQ LS1021コミュニティ・ボード <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ARMベースのプロセッサは、パフォーマンス、機能セット、およびパワーのバランスの取れた組み合わせにより、多くの最先端システムに組み込まれています。イノベーションと市場投入までの時間を短縮する重要な要素の1つは、イネーブルメントです。このセッションでは、NXPが提供するイネーブルメントについて検討し、Community Boardsがどのように機会の範囲を拡大するかを探ります。あなたのアイデアを持ってきてください! <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ARMベースのプロセッサは、パフォーマンス、機能セット、およびパワーのバランスの取れた組み合わせにより、多くの最先端システムに組み込まれています。イノベーションと市場投入までの時間を短縮する重要な要素の1つは、イネーブルメントです。このセッションでは、NXPが提供するイネーブルメントについて検討し、Community Boardsがどのように機会の範囲を拡大するかを探ります。あなたのアイデアを持ってきてください! スマートネットワーク
View full article
使用 IBIS 模型的 DES-N1854 DDR 系统设计 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> DDR3、DDR3L、DDR4 具有大型、宽总线,需要在 PCB 布线上进行管理以优化其运行速度。数据总线将具有与片上终端和读取和写入(双向)的驱动器强度相关的特性。地址-命令-控制总线将使用飞越或串行路由并单向工作。两者都需要仔细选择驱动器和接收器的特性,以及优化 PCB 布线和 PCB 上的走线设计。本次演讲将回顾驱动器、接收器和常见的 PCB 特性,并展示如何使用 IBIS 模型模拟来权衡 DDR 总线设计的利弊。 观看视频演示 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> DDR3、DDR3L、DDR4 具有大型、宽总线,需要在 PCB 布线上进行管理以优化其运行速度。数据总线将具有与片上终端和读取和写入(双向)的驱动器强度相关的特性。地址-命令-控制总线将使用飞越或串行路由并单向工作。两者都需要仔细选择驱动器和接收器的特性,以及优化 PCB 布线和 PCB 上的走线设计。本次演讲将回顾驱动器、接收器和常见的 PCB 特性,并展示如何使用 IBIS 模型模拟来权衡 DDR 总线设计的利弊。 观看视频演示 设计 | 软件与服务
View full article
KSDK示例列表 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 当前 KSDK 1.3 的示例位于C:\Freescale\KSDK_1.3.0\examples 中间件示例(tcpip、文件系统)位于C:\Freescale\KSDK_1.3.0\middleware   还有更多示例,创建如下:   KSDK 1.3 使用 KSDK 1.3 的 FTM PWM 实现彩虹色 如何在 KDS3.0 + KSDK1.3 中使用 printf() 将字符串打印到 UART 使用 KSDK 驱动程序驱动 16x2 LCD 将NFC控制器库与KSDK集成 KL43Z 使用 KDS3.0 +KSDK1.3.0 + 处理器专家支持 sLCD 和触摸感应   KSDK 1.2 使用 DMA 和 KSDK 模拟 ADC 灵活扫描模式 编写我的第一个KSDK1.2KDS3.0 中的应用 - Hello World 和使用 GPIO 中断切换 LED 使用 KSDK [FTM + GPIO] 控制直流电机的速度和伺服电机的位置 带 KSDK 的线扫描相机 [ADC + PIT + GPIO] 检测飞思卡尔杯智能赛道中心的简单方法 Kinetis Design Studio 中带有 KSDK 的 FatFs + SDHC 数据记录器 KSDK 段式 LCD 示例 KSDK GPIO驱动程序,带处理器专家 DAC Sinus 演示(使用 PEx + KSDK 1.2 + KDS 3.0) 如何基于KSDK演示代码启动定制的KSDK项目   KSDK 1.1 使用 SDK 和 CMSIS 在 KV31 上实现 FIR 功能的示例项目 如何使用KSDK 1.1.0切换KDS 2.0中的LED和处理器专家 KSDK SPI 主从控制器,带 FRDM-K64F 配置 Kinetis 软件开发套件 (KSDK) 以使用超声波传感器测量距离 Kinetis SDK 1.1.0 的 USB HID 双向通用设备演示项目 配置 Kinetis 软件开发套件 (SDK) 以使用红外 (IR) 传感器测量距离 在 KDS 中编写我的第一个 KSDK 应用程序 - Hello World 和 GPIO 中断   KSDK 1.0 使用 FRMD-K64F + KDS 1.1.0 编写您的第一个 LED 切换应用程序+ KSDK 1.0.0非处理器专家 使用 SDK 的低功耗应用 KSDK I2C EEPROM示例 概述 回复:KSDK示例列表 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 这些示例是否会针对 KSDK 2.0 进行更新 - 这些示例适用于过时的 KSDK 版本,不是吗? 此外,Processor Expert 显然已经过时并且不会进一步开发? 谢谢, 谨致问候,戴夫
View full article
FRDM-KW40Z Bluetooth LE Controller Usage with the Linux hcitool Bluetooth Low Energy is a standard for Low Power Wireless Networks introduced in the Bluetooth specification 4.0. Its target application domains include medical, sports & fitness, home automation and others. The adoption and development rates of this technology are growing fast helped by the wide availability of hardware support in most modern mobile phones and mobile operating systems. The purpose of this application note is to show how the Freescale FRDM-KW40Z can board with BLE Controller software can be used with the hcitool from the Linux Bluetooth stack over the HCI interface. 1. Introduction The Bluetooth specification has a very well defined interface between the Controller and the Host called the HCI (Host Controller Interface). This interface is defined for and can be used with various transport layers including an asynchronous serial transport layer. A typical scenario of Bluetooth Low Energy hardware use is a development board which has a BLE Controller accessible via serial transport HCI connected to a device on which the BLE Host runs. The device which runs the BLE Host can be any type of embedded device or a PC. PCs running a Linux type OS can use the hcitool from the Linux Bluetooth Stack to interact with a BLE Controller via the HCI interface. The particular use case of  FRDM-KW40Z board with a serial transport HCI interface running over USB CDC and connected to a PC running the Linux Bluetooth stack is shown in the diagram below and will be detailed din the following sections. Figure 1FRDM-KW40Z (BLE Controller) connected to Linux PC (Bluetooth Host Stack) via HCI Serial Transport 2. Loading the HCI Application onto the FRDM-KW40Z First load the hci_app on the FRDM-KW40Z board. The hci_app aplication can be found in the \ConnSw\examples\bluetooth\hci_app folder. 3. Connecting the FRDM-KW40Z to the Computer via a Serial Port After the app is downloaded to the board plug the board into a free USB port of your Linux computer. The following instructions, commands and their output is typical to a Debian based Linux OS. After the board is plugged in run the following command to list the serial ports available. >> dmesg | grep tty [ 0.000000] console [tty0] enabled [ 2374.118201] cdc_acm 1-2:1.1: ttyACM0: USB ACM device In our example the FRDM-KW40Z board serial port is ttyACM0. To test the connection some HCI commands can be sent in hex format from any terminal application to the serial HCI on the FRDM-KW40Z board. In the figure below an HCI_Read_BD_ADDR command and its corresponding Command Complete Event are shown as they were sent and received in hexadecimal format from the moserial serial terminal GUI application. Figure 2: HCI command and response event in hexadecimal format (HCI UART Transport) 4. Connecting the HCI Serial Interface to the Bluetooth Stack To connect the Linux Bluetooth stack to a serial HCI interface the hciattach command must be run as shown below. >> hciattach /dev/ttyACM0 any 115200 noflow nosleep Device setup complete If the the HCI serial interface is successfully attached to the Bluetooth stack then the "Device setup complete" message is shown. The any parameter specifies a generic Bluetooth device. The 115200 parameter is the UART baudrate. The noflow parameter diasables serial flow control. The nosleep parameter disables hardware specific power managment. Run the hciconfig command with no parameters to check the HCI interface id of the newly attached HCI serial device. >> hciconfig hci1:    Type: BR/EDR  Bus: UART     BD Address: 00:04:9F:00:00:15  ACL MTU: 27:4 SCO MTU: 0:0     UP RUNNING     RX bytes:205 acl:0 sco:0 events:14 errors:0     TX bytes:112 acl:0 sco:0 commands:14 errors:0 hci0:    Type: BR/EDR  Bus: USB     BD Address: 90:00:4E:A4:70:97  ACL MTU: 310:10  SCO MTU: 64:8     UP RUNNING     RX bytes:595 acl:0 sco:0 events:37 errors:0     TX bytes:2564 acl:0 sco:0 commands:36 errors:0 In this example the FRDM-KW40Z is assigned the hci1 interface as can be seen from the bus type (Type: BR/EDR  Bus: UART). The hci0 interface is the example shown corresponds to the on-board Bluetooth module from the machine. On some systems the interface might need to be manually started by using the hciconfig interfaceId up command. hciconfig hci1 up 5. Configuring the Bluetooth Device and Listing its Capabilities The hciconfig command offers the possibility of configuring the device and listing the device capabilities. To find all commands supported by the hciconfig tool type the following command. >> hciconfig –h ...display supported commands... Each individual hciconfig command must be addressed to the correct HCI interface as reported above. In our example we use the hci1 interface. Some hciconfig commands require root privileges and must be run with sudo (the "Operation not permitted(1)" error will be returned if a command needs to be run with root privileges). Some useful hci config commands: >> hciconfig hci1 version    -> lists hci device verison information >> hciconfig hci1 revision    -> lists hci device revision information >> hciconfig hci1 features    -> lists the features supported by the device >> hciconfig hci1 commands    -> lists the hci commands supported by the device >> sudo hciconfig hci1 lestates    -> lists the BLE states supported by the device >> sudo hciconfig hci1 lerandaddr 11:22:33:44:55:66    -> set a random address on the device >> sudo hciconfig hci1 leadv 3    -> enable LE advertising of the specified type >> sudo hciconfig hci1 noleadv    -> disable LE advertising Now the newly connected board with a serial HCI is attached to a HCI interface of the Bluetooth stack and is ready to use. 6.    Controlling the Bluetooth Device using the hcitool The hcitool can be used to send HCI commands to the Bluetooth device. A command is available which lists all available hcitool actions. >> hcitool -h ...display supported commands... To target a specific HCI interface use the -i hciX option for an hcitool command. We will use -i hci1 in our examples. The hcitool supports commands for common BLE HCI operations some of which are shown below and also supports sending generic HCI commands using a dedicated option which uses hexadecimal numbers for the OGF (Command Group), OCF (Command Code) and the parameters. The 6 bit OGF and the 10 bit OCF compose the 16 bit HCI Command Opcode. The command parameters are specific to each command. 6.1.  Listing Devices Available to the hcitool An hcitool command can list all available device interfaces. >> hcitool dev Devices: hci1    00:04:9F:00:00:15 hci0    90:00:4E:A4:70:97 The device we are working with is connected to the hci1 interface as seen from the output of the hciconfig command used above. 6.2.  Scanning for Advertising LE Devices The hcitool can be used to perform a LE Device scan. This command requires root privileges. Press Ctrl+C to stop the scan at any time. >> sudo hcitool -i hci1 lescan LE Scan ... 00:04:9F:00:00:13 (FSL_OTAC) ^C A list of addresses and device names will be shown if advertised (< > or < > as define din the specification). 6.3.  Obtaining Remote LE Device Information Using the hcitool To obtain information about a remote LE device a special hcitool command can be used. The hcitool leinfo command creates a connection, extracts information from the remote device and then disconnects. The remote device information is shown at the command prompt. >> sudo hcitool -i hci1 leinfo 00:04:9F:00:00:13 Requesting information ...        Handle: 32 (0x0020)        LMP Version: 4.1 (0x7) LMP Subversion: 0x113        Manufacturer: Freescale Semiconductor, Inc. (511)        Features: 0x1f 0x00 0x00 0x00 0x00 0x00 0x00 0x00 In this example information about a device previously discovered using the hcitool lescan command is shown. 6.4.  Connecting and Disconnecting from a Remote LE Device Connecting to a remote LE device is done using the hcitool lecc command. >> sudo hcitool -i hci1 lecc 00:04:9F:00:00:13 Connection handle 32 As before a previously discovered device address is used. If the connection is successful then the Connection Handle is returned and in our case the Connection Handle is 32. The hcitool con command shows active connections information: address, connection handle, role, etc. >> hcitool con Connections: < LE 00:04:9F:00:00:13 handle 32 state 1 lm MASTER To end a LE connection the hcitool ledc command can be used. It must be provided with the Connection Handle to be terminated, and optionally the reason. The device handle obtained after the connection and shown in the connected devices list is used. >> hcitool –I hci1 ledc 32 >> Listing the connections after all connections are terminated will show an empty connection list. >> hcitool con Connections: >> 6.5.  Sending Arbitrary HCI Commands To send arbitrary HCI commands to a device using the Command CopCode (OGF and OCF) the hcitool cmd command can be used. As an example the HCI_Read_BD_ADDR command is used which has the 0x1009 OpCode (OGF=0x04, OCF=0x009) and no parameters. It is the same command shown in the direct serial port to HCI communication example above. hcitool -i hci0 cmd 0x04 0x0009 < HCI Command: ogf 0x04, ocf 0x0009, plen 0 > HCI Event: 0x0e plen 10   01 09 10 00 15 00 00 9F 04 00 The OpCode OGF (0x04) and OCF (0x009) and no parameters are passed to the hcitool cmd command all in hexadecimal format. The parameters length (plen) is 0 for the command. The response is a Command Complete event (0x03) with the parameters length (plen) 10. The parameters are 01 09 10 00 15 00 00 9F 04 00: 01 is the Num_HCI_Command_Packets parameter 09 10 is the Command OpCode for which this Command Complete Event is returned (in little endian format) 00 is the status – Success in this case 15 00 00 9F 04 00 is the BD_ADDR of the device as listed by the hcitool dev command KW41Z31Z21Z
View full article
AMF-ACC-T1213 - DwF 底特律 <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
MCUXpresso 25.6: GDB infinite memory-read loop after Cortex-M0+ EXC_RETURN — workaround: backtrace l Environment IDE: MCUXpresso IDE 25.6 Debugger: GNU Arm GDB 15.2.90.20241130-git Toolchain: GNU Arm Toolchain 14.2.Rel1 Target: NXP LPC845, Arm Cortex-M0+ Debug probe: Onboard LPC-Link2 using LinkServer Host: Windows Problem GDB becomes unresponsive when debugging a Cortex-M0+ application that uses a synthetic exception stack frame to return from SysTick into Thread-mode code. The firmware executes an exception return using: bx lr with LR = 0xFFFFFFF9 (return to Thread mode using MSP). The synthetic exception frame contains a valid Thumb-mode destination PC and xPSR. The application operates on the physical target, but GDB becomes unresponsive after stopping at the destination function. Symptoms include: Variable hover inspection stops working. Memory views display ????????. GDB commands, including info threads, become unresponsive. The debug session generally requires termination and cleanup. The problem also occurs when using a hardware breakpoint at the destination rather than instruction-stepping across the exception return. Reproduction Start debugging the application normally. Stop immediately before the bx lr exception-return instruction. Place another breakpoint at the destination function, System(). Step across the exception return or continue to the destination breakpoint. GDB reaches the destination but subsequently becomes unresponsive. The failure is reproducible with the normal GDB configuration. Remote-protocol evidence Enabling remote-protocol tracing with: set logging file gdb-remote.log set logging overwrite on set logging enabled on set debug remote 1 reveals that GDB repeatedly performs the same sequence of remote memory reads: m1b4,4 -> 91010000 m1ba,4 -> 00000000 m1bc,4 -> 00000001 m1c0,4 -> f9ffffff m190,4 -> 07490868 This sequence repeats indefinitely. LinkServer acknowledges and responds successfully to the requests. The trace therefore does not indicate an ordinary communication timeout. Notably, the response at 0x1c0 contains 0xFFFFFFF9, the exception-return value. Confirmed workaround Entering the following command in GDB: set backtrace limit 1 prevents the observed failure in repeated testing. With this setting active: The debugger repeatedly crosses the same exception-return boundary. Both breakpoints function normally. Variable hover inspection works at the destination. The debug session remains responsive. The workaround also functions when placed in a GDB command file configured through: Debug Configurations → GDB Debugger → GDB command file No application or assembly modifications are necessary. Additional isolation The same target, debug probe, and IDE successfully debug conventional firmware. Calling the destination function without the synthetic exception-return shim also works. A conventional SysTick handler does not exhibit this failure. The problem appears specifically associated with GDB processing the execution state following the synthetic exception return. Expected behavior GDB should remain responsive after the exception return, permitting stepping, register inspection, memory inspection, and variable evaluation. If GDB cannot interpret the resulting stack frames, it should report an error or terminate unwinding rather than enter an indefinitely repeating memory-read sequence. Suspected cause The effectiveness of set backtrace limit 1 strongly suggests that GDB's ARM Cortex-M stack-frame unwinding or frame analysis is involved. The exact internal cause has not been established. Request Please investigate the interaction between GDB's ARM Cortex-M exception-frame handling and synthetic exception returns. In particular, determine why the debugger repeatedly reads the same target memory locations and whether frame unwinding can enter an unbounded loop. The workaround restores debugging functionality, but it restricts backtrace depth and should not be necessary for a valid exception-return sequence. Re: MCUXpresso 25.6: GDB infinite memory-read loop after Cortex-M0+ EXC_RETURN — workaround: backtra forgot the code clip: 0000015c : 15c: b4f0 push {r4, r5, r6, r7} 15e: 4640 mov r0, r8 160: 4649 mov r1, r9 162: 4652 mov r2, sl 164: 465b mov r3, fp 166: b40f push {r0, r1, r2, r3} 168: 4911 ldr r1, [pc, #68] @ (1b0 ) 16a: 6808 ldr r0, [r1, #0] 16c: 3001 adds r0, #1 16e: 6008 str r0, [r1, #0] 170: 2804 cmp r0, #4 172: dd03 ble.n 17c 174: f000 fa24 bl 5c0 178: f7ff ffcc bl 114 0000017c : 17c: 4d0d ldr r5, [pc, #52] @ (1b4 ) 17e: 4e0e ldr r6, [pc, #56] @ (1b8 ) 180: 4f0e ldr r7, [pc, #56] @ (1bc ) 182: b4ff push {r0, r1, r2, r3, r4, r5, r6, r7} 184: 480e ldr r0, [pc, #56] @ (1c0 ) 186: 4686 mov lr, r0 188: b500 push {lr} 18a: bd00 pop {pc} Re: MCUXpresso 25.6: GDB infinite memory-read loop after Cortex-M0+ EXC_RETURN — workaround: backtra Hello @Pedantic2  Thank you for the detailed information. The LPC845 appears to complete the exception return correctly, while the failure occurs afterward, when GDB processes the stack frames. I will check with the MCUXpresso IDE team to determine whether they are aware of this issue. Since the issue appears more likely to be related to GNU GDB’s Cortex-M frame-unwinding implementation, I also recommend reporting this behavior to the GNU GDB project: https://sourceware.org/bugzilla/  Thank you. BR Alice
View full article
MCX-N9XX 评估板 1.8V 电源存在问题。 我有一个 MCXN9XX 评估板,需要从 P1_16 (J17) 和 P1_17 (J18) 焊盘上获得 1.8V 输出,以便与工作电压为 1.8V 的外部 I3C 集线器进行 I3C 通信。为了在焊盘上获得 1.8V 电压,我重新排列了跳线,以便在 MCU_PWR 轨上获得 1.8V 电压,该轨也为 VDD_MCU 供电。执行此配置后,“MCUXpresso”工具无法发现目标设备,并显示“无法与内核通信”(屏幕截图附后)。 请问谁能帮我确定正确的跳线设置,以便在烧录代码的同时,能够在 IO 焊盘 J16 和 J17 上获得 1.8V 电压? 错误截图: 电路板设计 FRDM 培训 HW-开源 MCX N
View full article
TJA1445:中断配置 你好, 我们使用 S32K358,搭配 TJA1445。 我们正在将 NXP TJA1145 驱动程序迁移到 NXP TJA1445,并使用 EB tresos 进行配置。 我们不使用 RXD 作为中断,但在 EB tresos 中配置 TJA 驱动程序时,我无法将其停用。 我已将唤醒支持设置为“不支持”。 我设置的是总线唤醒,我们希望通过 CAN 模式唤醒。 我们使用 INH 输出。 但在配置文件 CanTrcv_TJA14XX_PN_Ip_Cfg.h 中,有这样一条 #defineCANTRCV_TJA14XX_PN_IP_USE_IPV_ICU 它强制在依赖于“Icu_Cfg.h”的文件CanTrcv_TJA14XX_PN_icu_external_access.h中包含“Icu.h”。 但就我们而言,我们的配置中没有 ICU 模块(不需要)。 如何在不使用 RXD 中断的情况下使用驱动程序 TJA1445? 苏菲 Re: TJA1445 : interrupt configuration 你好, 为了更好地了解对 ICU 的依赖性以及生成的配置,请您提供以下信息? 目前使用的RTD版本和EB Tresos版本。 谢谢! Re: TJA1445 : interrupt configuration 你好, 我正在使用 RTD SW32K3_S32M27x_RTD_R23-11_7.0.1 TJA驱动程序:S32K3_CANTRCV_TJA14XX_PN_R21-11_1.0.0
View full article
Secondary failed allocate mbuff from DPDK Pool hi All, Using : LX2160  LSDK 2108 main  MC firmware version: 10.32.0 DPDK Version : dpdk_19_11_tags_LSDK20.04-isc-09 Primary ( DPDK ) Process : Create a mbuff Pool using [ rte_pktmbuf_pool_create("dlmempool", ] Secondary ( DPDK ) Process : fails to allocate mbuff using API [ rte_pktmbuf_alloc(mempool) ] In Secondary i can see mempool is correct. I can see mbuff available is full. The failure happens for 1st mbuff allocation using  rte_pktmbuf_alloc. Any solution for this. Thanks. Re: Secondary failed allocate mbuff from DPDK Pool thanks i will try these options and update you by tomorrow Re: Secondary failed allocate mbuff from DPDK Pool Hello, The secondary process must map hugepages at the same virtual address as the primary. If ASLR is active, the secondary will resolve the mempool pointer to a different virtual address, causing the first allocation to fail. echo 0 > /proc/sys/kernel/randomize_va_space   Run this before launching either the primary or secondary process. 2. Provision Sufficient DPMCP Objects Create as many DPMCP objects as the total number of processes (primary + secondary). For 1 primary + 1 secondary, you need at least 2 DMPCPs: export DPMCP_COUNT=3 # for 1 Primary + 2 Secondary (always provision +1 as buffer) ./dynamic_dpl.sh dpmac.X 3. Provision Sufficient DPIO Objects Each process needs its own DPIO portals. The formula is: (Total Processes) × (cores per process + 1 extra per process) For example, 1 primary (2 cores) + 1 secondary (2 cores) = at minimum 9 DPIOs. export DPIO_COUNT=20 # set generously 4. Correctly Blacklist/Whitelist Devices in the Secondary The secondary process must NOT re-initialize I/O devices (dpni, dpbp, dpcon, dpseci). Only dpio and dpmcp should be initialized by the secondary. Pass the correct blacklist flags: # Secondary process example — blacklist all dpni/dpbp/dpcon, allow only dpio + dpmcp ./your_secondary_app --proc-type=secondary \ -b fslmc:dpni.X \ -b fslmc:dpbp.X \ -b fslmc:dpcon.X \ -- [app args]   Or alternatively, explicitly whitelist only the dpio and dpmcp objects assigned to the secondary: ./your_secondary_app --proc-type=secondary \ -w fslmc:dpio.Y \ -w fslmc:dpmcp.Z \ -- [app args] 5. Use --proc-type=secondary EAL Argument Ensure the secondary is launched with the correct EAL flag: ./your_secondary_app -c -n 1 --proc-type=secondary ...   Or use --proc-type=auto to let DPDK auto-detect. 6. Verify the Mempool Lookup in Secondary In the secondary, do not call rte_pktmbuf_pool_create again. Instead, look up the existing pool created by the primary: // In secondary process: struct rte_mempool *mempool = rte_mempool_lookup("dlmempool"); if (mempool == NULL) { // Error: pool not found — ASLR or hugepage mapping issue } struct rte_mbuf *m = rte_pktmbuf_alloc(mempool);     If rte_mempool_lookup returns a valid non-NULL pointer but rte_pktmbuf_alloc still returns NULL, the issue is almost certainly the DPIO portal not being initialized for the secondary's thread/core.   Regards Re: Secondary failed allocate mbuff from DPDK Pool thanks @Bio_TICFSL for the quick solution
View full article
Locked Mirfare classic 1k I don't really know much about NFC tags but I played around a bit with NFC Tools and wanted to try the lock feature and locked my tag with the password "123" but when I try to unlock it I just get a write error. I was able to read the tag with Mirfare classic tools and that Key a is D3F7(3x) and I tried to reset the access permissions back to FF..FF078069..FF but I can't figure out what key b is. I saw a old post that mentioned the first 6 bits of the md5 sum or the first 4 bits + 42(2x) but neither of those worked. Does anyone know if the chip can be rescued or is it completely broken? NFC Controller Solutions Re: Locked Mirfare classic 1k Hello @chaube97  The chip is physically fine but functionally locked. MIFARE Classic has no format or factory reset command — the only way to modify the sector trailer is to authenticate with the correct Key B first. Without it, the tag cannot be recovered. Hope this helps
View full article
MPC5744p S32DS LINBUS 主从示例 大家好, 请问有人能提供关于 S32 Design Studio 中是否有 MPC5744p LINBUS 主/从示例的信息吗? 谢谢! Re: MPC5744p S32DS LINBUS master slave example 附件中的 ZIP 文件包含修改后的驱动程序文件。 测试配置: - MPC5744P - S32 电源架构设计工作室 2.1 - S32_SDK_S32PA_RTM_3.0.3 - INST_LINFLEXD_UART2 FreeRTOS - 两个物理从控制器 已实现的功能: - LIN 中断和 0x55 同步字节 - 受保护标识符的生成和验证 - 主控端传动 - 中断驱动的从属响应 - 经典和增强型校验和 - 帧最多包含 8 个数据字节 - 响应超时处理 - 从设备断开连接、RESET 或重新连接后的恢复 - 轮询多个从属标识符 该驱动程序使用两个物理 MPC5744P 从控制器进行了测试。 安装: 1.备份原始SDK驱动程序文件。 2. 将提供的头部信息复制到: 平台/驱动程序/公司/ 3. 将提供的源文件复制到: platform/drivers/src/linflexd/ 4. 刷新项目中链接的 SDK 文件。 5. 执行彻底重建。 我希望这能帮助任何需要使用 S32 SDK 进行基本 LIN 通信的人。 欢迎提供其他 MPC5xxx 设备的反馈和测试结果。 顺祝商祺! Re: MPC5744p S32DS LINBUS master slave example 这里有一种可行的方法,可以模拟唤醒信号。   #define SYNC 0x55 #define WAKEUP = 0x00 ;    …… LINFLEXD_UART_DRV_SetBaudRate ( INST_LINFLEXD_UART1 , 4800 );     LINFLEXD_UART_DRV_SendDataBlocking ( INST_LINFLEXD_UART1 , & WAKEUP , 1 , 100 );     LINFLEXD_UART_DRV_SetBaudRate ( INST_LINFLEXD_UART1 , 9600 );     masterMessage.sync = SYNC ;​​     masterMessage.id = PID ;​​     masterMessage.data [ 0 ] = 0x00 ;​     masterMessage.data [ 1 ] = 0x00 ;​     masterMessage.chksum = linbus_calculate_checksum ( masterMessage.data , 2 ) ;​​​   Re: MPC5744p S32DS LINBUS master slave example 您好, 你可以继续使用SDK和LINFlex模块,但需要自己编写代码/驱动程序,例如重用现有的裸机代码。 BR,彼得 Re: MPC5744p S32DS LINBUS master slave example 我的想法是继续在 SDK 环境中运行,您认为这目前是启用 LIN 硬件的最佳方式吗?或者,有没有办法通过 PIT 和 GPIO 来创建软件? Re: MPC5744p S32DS LINBUS master slave example 您好, 据我所知,SDK 中没有 LIN 支持,也没有计划添加该功能。 BR,彼得 Re: MPC5744p S32DS LINBUS master slave example 使用SDK和LIN总线的最佳方法是什么?我尝试使用 linflexd_uart 生成 LIN 消息,但无法生成中断和唤醒消息。我应该将 TX 用作数字输出吗? Re: MPC5744p S32DS LINBUS master slave example 感谢您的快速回复,请问是否可以将示例的一部分(初始化和发送 LIN 消息)与 SDK 包中的 FreeRTOS 示例集成,而不会出现任何重大问题? Re: MPC5744p S32DS LINBUS master slave example 您好, S32DS 中有 LIN 主站和从站的示例,您可以参考一下。 PetrS_0-1692959754415.png BR,彼得
View full article
S32K312 - SRAM 数据保持 - 冷启动时偶尔出现硬故障 你好 我正在尝试让 S32K312 中的 SRAM 存储器末尾(256 字节)在功能 RESET 后保留数据。 我通过修改链接器脚本来实现这一点,将ram_rsvd2(以及 __INT_SRAM_END)拉回 256 字节,这样启动汇编脚本就不会再清除最后 256 字节。 Hareesh_S_0-1787256254412.pngHareesh_S_0-1787256254412.pngHareesh_S_0-1787256254412.pngHareesh_S_0-1787256254412.png 为了测试此功能,我切换了 2 个 GPIO/LED——一个用于指示 SRAM 内容已保留,另一个用于指示 SRAM 内容未保留/无效。 Hareesh_S_1-1787256280872.pngHareesh_S_1-1787256280872.pngHareesh_S_1-1787256280872.pngHareesh_S_1-1787256280872.png 项目首次烧录时,似乎按预期工作——LED_01 在第一个周期内为高电平,随后 LED_02 在 RESET 周期后保持高电平。 不过,在冷启动时,两个 LED 灯都不亮——我可以确认这是因为 MCU 在尝试访问保留的 SRAM 区域中的地址时发生了硬故障。 我还注意到,当 MCU 运行时(发生硬故障)连接调试器时,我无法通过内存监视器单独读取/写入特定 SRAM 区域中的数据(它显示 ???? 而不是数据)。S32 Design Studio 和 Segger Ozone 都存在这个问题。 这种硬故障行为也不稳定,因为有时在冷启动时,项目可以按预期工作,LED_01 为高电平,但这种情况很少发生。 我附上了一个可以重现我问题的最小示例项目。如果能得到一些关于调试/更好地理解这种行为的帮助,那就太好了! 此致, 哈里什·S Re: S32K312 - SRAM retention - occasional hardfaults on cold boot 你好, 我还注意到,当 MCU 运行时(发生硬故障)连接调试器时,我无法通过内存监视器单独读取/写入特定 SRAM 区域中的数据(它显示 ???? 而不是数据)。S32 Design Studio 和 Segger Ozone 都存在这个问题。 这意味着 RAM 内容丢失,并且 RAM 中包含 ECC 错误——RAM 未初始化。如果复位导致 RAM 内容被破坏,则取决于执行的是哪种复位操作。 检查 RMG [DES/ FES] 寄存器,查看发生了哪种 RESET。 petervlna_0-1787295026947.pngpetervlna_0-1787295026947.pngpetervlna_0-1787295026947.pngpetervlna_0-1787295026947.png petervlna_1-1787295110517.pngpetervlna_1-1787295110517.pngpetervlna_1-1787295110517.pngpetervlna_1-1787295110517.png 当从 RAM 读取 ECC 错误时,会触发硬故障。 顺祝商祺! Peter Re: S32K312 - SRAM retention - occasional hardfaults on cold boot 你好@petervlna , 谢谢你的解释。我知道 SRAM 中的内容会无效,但没想到这会导致硬故障。 我还有一个问题——当我的应用程序进入待机模式并通过唤醒事件退出时,MC_RGM DES/FES 标志均未设置。这是预期行为吗?如果答案是肯定的,我该如何确定MCU是否已退出待机状态?这条后续内容是否更适合另开一篇社区帖子?通过唤醒信号退出待机状态是否会在 RDSS 寄存器中反映出来? Re: S32K312 - SRAM retention - occasional hardfaults on cold boot 你好 , 查阅了其他社区帖子和参考手册后,我的理解是,我应该结合 RDSS 检查 MC_ME[PREV_MODE](实际上是 MC_ME.MODE_STAT)来判断 MCU 是否已从待机状态唤醒。 除非我理解有误,否则我认为这已经解答了我的疑问。 非常感谢大家的支持! 此致, 哈里什·S Re: S32K312 - SRAM retention - occasional hardfaults on cold boot 你好, 是的,这是意料之中的。由 WKPU 事件引起的从 STANDBY 唤醒不一定会设置任何 MC_RGM DES 或 FES 标志。如果 MC_RGM 中未报告 RESET 状态,则确定设备是否从待机状态恢复的推荐方法是检查 MC_ME PREV_MODE 字段。 顺祝商祺! Peter
View full article