Hi Rob, You can set the following Kconfigs in your prj.conf: CONFIG_CODE_ITCM=y CONFIG_DATA_DTCM=y See soc/arm/nxp_imx/rt/Kconfig.soc for more details. Maureen

Hi Olivier, The touch input hasn’t been enabled upstream yet. I posted a draft pull request to add this, but it hasn’t been merged because we haven’t solidified the API. https://github.com/zephyrproje

#input

Does the application work without the debugger attached? (i.e., did it get programmed into flash correctly?) I’ve seen weird behavior if you leave the GDB client executable at the default. Try changin

#nrf52832 #jlink #debugging #eclipse

Hi Bob, The ‘intelhex’ error looks like you’re missing a python package, but even if you get that resolved you unfortunately cannot use pyocd in the Windows 10 Linux subsystem. WSL has limited support

Hi Nick, You need to set: CONFIG_MPU_ALLOW_FLASH_WRITE=y Maureen

Hi Lawrence, I’m not sure yet what’s going on with the J-Link firmware on this board – the USB CDC enumerates but the J-Link commander fails to connect to the RT1064 target. The LPC-Link2 J-Link firmw

Hi Lawrence, You’re right, I forgot that RT1064-EVK has a different onboard debug circuit than RT1050-EVK. Do you have an external JLink probe you can use? Are you sure you’re using the JLink GDB serv

Hi Lawrence, You have to use JLink firmware to use the JLink GDB server. “lpc4322__mimxrt1064_evk_if_crc_20180810.bin” is DAPLink firmware, not JLink firmware. Try https://www.segger.com/downloads/jli

Hi Lawrence, I rewrote the “Programming and Debugging” sections for all the NXP boards in a PR that was just merged on Friday: https://github.com/zephyrproject-rtos/zephyr/pull/14000 For many of the i

Hi Antoine, It could be that you’re getting an interrupt (e.g., systick) while writing to flash, and the interrupt handler is located in flash. It’s not ideal to disable interrupts for such a long tim

Hi Stefan, If your board selects HAS_DTS_I2C_DEVICE, then you should define CONFIG_LSM6DS0_I2C_MASTER_DEV_NAME and CONFIG_LSM6DS0_I2C_ADDR in your board dts.fixup file rather than myboard_defconfig. S

#sensor #dts #defconfig

Hi Marco, We traced the issue down to a difference in low-power mode behavior between A0 and A1 silicon (EVK and EVKB boards respectively). Please give the following PR a try: https://github.com/zephy

Hi Marco, This board has two versions, EVK and EVKB, which correspond to different revisions of silicon (A0 and A1, respectively). The EVK board works just fine, but I was able to reproduce the issue

Hi Marco, Can you please try samples/basic/blinky or samples/synchronization? These samples should work on this board, but I’m currently traveling and don’t have hardware with me to check if they rece