jayheng / nxp-mcubootutility

恩智浦全系列MCU安全启动一站式工具（研发模式），基于Python2.7.15+wxPython4.0.3

Page visitor counter (starts from 2023.09.23)

📘 My Open Source Projects

nxp-mcubootutility's Issues

EEXT-10 Configuration error

Hello,
I believe in the parameters for the Cypress HyperFlash is incorrect. The S26KSxxxS should be run at 166Mhz and the S26KLxxxS should be run at 100Mhz and at 3.0 Volts based on their data sheet.

I believe in the parameters for the Macronix Octal DDR is also incorrect. The MX25UMxxx45G and MX66UMxxx45G should be run at 166 Mhz based on their data sheet.

EEXT-6 i.mxrt1050 with mx25u25643gz

We have a customized using i.mx rt1050 and qspi flash mx25u25643gz. Can I use your application to direct load bin file into the flash?

EEXT-7 How to "Mass Erase" flash on RT1170-EVK to fix no SWD device found?

My problem is understanding how to use MCU Boot Utility to "Mass Erase" flash on RT1170 in attempt to fix MCUXpresso to recover from SWD not being found. When I attempt to "mass Erase", I get "please configure boot device via Flashloader first" ?

• RT1170 EVK MCUXpresso "SWD Configuration" 0 available SWD devices detected?

1. How do you configure RT1170-EVK boot device via Flashloader?
2. After putting board SW1 into software downloader mode, do I connect a single USB cable J11?
   Or two USB cables, J11 and J20?
   I tried both J11 and J11 plus J20.

In SW1 downloader mode, with two USB cables connected, J11 and J20 connected, I see:

This is the MCUXpresso I am hoping to solve with MCU Boot Utility:

Thank you for a great tool and any advice,
-Ed

EEXT-9 RT1064 external SPI flash programming

Hello!

We have a custom board that use RT1064 with a 32MB SPI flash. We are going to use this SPI flash to store the GUI resources, and use the internal 4MB flash to store the code.

We want to program them via USB. Can this tool finish this job?

We are having trouble programming the 32MB external flash, can you please give me some instruction?

Thank you!

EEXT-4 i.MXRT1170对应的eFuse Map是错的，会导致SRK烧写失败

EEXT-12 Minor permission issue

I'm using NXP-MCUBootUtility to create an SDcard boot image. Works great! Thanks...

One small issue I've encountered: I use the DCD configuration tool within MCUXpresso to create a .bin file to be included with the boot image. I'm running on Windows 11 and the MCUXpresso/Config tool produces a file named dcd.bin

If I view this file with WSL/Ubuntu it has permissions 0666 (rw-rw-rw-). From MCUBootUtility, I pointed to this file to include it with the boot image and the tool threw an error due to permissions. Looks like it is happening when the file is being copied?

If I use WSL/Ubuntu to change the permissions to 0777 (rwxrwxrwx), everything works as expected. Not sure why MCUBootUtility wants/needs execute permission... But giving it solves the issue...

Perhaps a small change to avoid this?

Thanks again!

EEXT-11 RT1064 Cannot Set BT_FUSE_SEL Fuse

We were attempting to use MCUBootUtility for production programming of fresh boards off the line. However we could not get the utility to set the BT_FUSE_SEL fuse. When attempting it I would try setting the fuse value to 1 but it would always get set back to zero and couldn't be saved. Eventually I was able to manually burn the fuse from the command line.

EEXT-13 Small GUI issue with View Bootable Image with SPI NOR/EEPROM

Firstly, great tool of yours, Jay! Thanks

I'm flashing one of the prebuilt images (led_blinky_0x00003000.srec) into LPSPI NOR/EEPROM of EVKB IMXRT1050, after converting it to bootable image using MCUBoot utility v5.1.0. Flashing is successful.

On "View Bootable Image", it shows the expected/correct pattern of 0xd1 (fixed pattern), 0x00 and 0x20 (length of the IVT in bytes), 0x40 (version no.) etc. But, the highlighting (in blue color) of the addresses to indicate where the executable image starts seems to start from 0x1000 (which is the offset for FlexSPI NOR/SEMC NOR), instead of 0x400 which is the expected offset for SPI NOR/EEPROM as per the reference manual.

Is this something that could be easily fixed in the GUI?

Have a good day!
Ram

Support for CRC appended in the end of a binary file

Is it possible to add this support in the future? Thanks!

EEXT-8 Support for lpc540xx

I want to add support for LPC in MCUBoot Utility via USB HID. Will that be too complicated?

I am a beginner but will to spend time and get it done. Just want to make sure it is possible before putting all my time into it.

EEXT-5 i.MXRT1170 HAB Sign Part Of Image时，无法通过验证启动

EEXT-1 MCUBootUtility加密

请问下MCUBootUtility最新版开启加密功能，和以前版本的开启方法是一样的吗

RT1052 BEE 启动失败

问题描述：

• 平台 i.MXRT1052 飞凌 OK1052_32M_sdram 开发板
• MCUBootUtility 版本: v6.1.0
• 测试固件： driver_examples lpuart 固件，这个固件是 fliedspi_nor 启动，不使用 SDRAM，仅调用了串口，以115200的波特率输出测试文本，然后回显收到的数据。
• 现象：BEE 启动失败，串口没有输出

已经做过的尝试：

1. 在 DEV Unsigned Image Boot 模式下下载相同的固件，可以正常启动，串口输出：

Lpuart polling example
Board will send back received characters

2. 使用 BEE 加密，加密区域选择 User Defined，区域长度为 0，可以正常启动。

3. 使用 BEE 加密，加密区域选择 User Defeind，区域设置在固件的外面，可以正常启动。

4. 为排除在加密中调用时钟配置导致启动失败，仅将一个不包含时钟配置的简单函数单独定义到指定地址，对这个地址进行 User Defined 加密，无法正常启动（即使不调用这个函数）。

eFuse 的数据核对：

（顺带一提UI小问题，SRK0-7显示不全，第一个没显示出来）

请问有没有什么可以提示的线索，感谢百忙之中阅读这个 issue，我也将测试固件的源码提交到了附件当中：

polling.zip

EEXT-2 RT1170-EVK USB Enumeration Problems

I'm unable to get the utility to work with my RT1170-EVK because it enumerates as USB HID device with vID 0x0D28 and PID 0x0204 rather than the expected vID 0x1FC9 and PID 0x013D

EEXT-3 Rebuilding from source needs more explanation

After installing python 2.7 I had to update pip using
python -m pip install --upgrade pip
and then
pip.exe install PyInstaller==3.3.1

before I could rebuild the application