Using MFGtools with MIMRX1170-EVK

fmabrouk · ‎01-19-2021

Hello Kerry!

I am trying to use MFGTool with my new dev board iMX RT1176xxxxA. I followed the same steps used with MFGtool with iMX RT1060, but I could not get the blinky LED to work. I attached the files I generated.

I also added these to my IDE: XIP_EXTERNAL_FLASH=1, XIP_BOOT_HEADER_ENABLE=0,XIP_BOOT_HEADER_DCD_ENABLE=0.

Please have a look and see if I am missing anything.

@kerryzhou

fmabrouk · ‎02-17-2021

@kerryzhou

Could you please do a test to program the flash using MFG tools for imXRT1170 dev board.

kerryzhou · ‎02-17-2021

Hi fmabrouk,

I already test the published SDK2.9.0 for RT1170, it works now.

So, you can update your SDK:https://mcuxpresso.nxp.com/

BTW, the MFGtool in the SDK lack the blhost, so you need to add it.

Anyway, to make your let it work easily, I attach the whole working tools folder from my side, with it helps you.

The related .sb already generate by myself, you can find more details in folder:Tools\elftosb

Please try it on your side.

If you still have questions about it, please kindly let me know.

Best Regards,

kerry

kerryzhou · ‎02-17-2021

Hi fmabrouk，

Yes, of course, I will test it today again.

About the newest SDK2.9.0, I also check with my colleague who test that item before the SDK launch, and he said he also has the issues, and he already report the SDK team.

Due to the Chinese Spring Festival, I am back to work just today, I will test the newest SDK again, as I also report it before the new SDK, which I help you test it in that old times.

Any testing result, I will let you know.

Best Regards,

Kerry

kerryzhou · ‎01-22-2021

Hi fmabrouk,

Another good tool for your, still from the MCUBOOTUtility author, which is used to replace the MFGTool:

https://github.com/JayHeng/NXP-MCUBootFlasher/releases/tag/v3.0.0

Manual:

https://github.com/JayHeng/NXP-MCUBootFlasher/blob/master/README.md

My test result and I also attach my generated .sb for you.

This tool is also very easy to use, and I have test it, it works OK with my generated .sb file.

Best Regards,

Kerry

kerryzhou · ‎01-22-2021

Please also note, to RT1176, the flash start from 0X30000000, not the 0X60000000.

So, a lot of .bd file need to be modified, but to your question, this is not the root issue, seems the MFGtool has issues to the RT1170, anyway, let's wait the new SDK published, the SDK2.9.0 for RT1170 is planned to publish in Middle Feb.

Until now, you can use MCUBootUtility tool, let's try to find the way to resolve your MCUBootUtility running issues.

Check python version, minimize the MCUBootUtility tool path length.

Any updated information, just kindly let me know.

Best Regards,

Kerry

fmabrouk · ‎03-04-2021

@kerryzhou

Hi Kerry!

I hope you are doing well!

I am back to MFG tool test again. I tried to test it on my Dev board and I got the error below. However, I dont get this error when I run MFG tool with imXRT1060.

Any idea what the cause of this error is?

C:\Users\...\Documents\NXP Tools\iMXRT1176MFGTools\elftosb>elftosb.exe -f imx -V -c ../../bd_file/imxrt117x/imx-flexspinor-normal-unsigned.bd -o evkmimxrt1170_igpio_led_output_cm7.bin evkmimxrt1170_igpio_led_output_cm7.s19

error: unable to find command file ../../bd_file/imxrt117x/imx-flexspinor-normal-unsigned.bd

Thank you!

fmabrouk · ‎03-04-2021

@kerryzhou

I also managed to get my MCUbootUtility to run on my PC. Can you please give any documentation to how to use it to program my board with a secure boot image?

kerryzhou · ‎03-07-2021

Hi fmabrouk,

Which secure mode you want to use? HAB encrypted or the BEE?

In fact, in the MCUBootUtility tool user manual in Github, it already has the detailed steps, you can refer to it.

But, please note, the secure mode will write your fuse bit, which just can write from 0 to 1.

So, if you are still in the learning phase, I still suggest you learn other peripherals in the SDK, as the secure mode will have the debug limit.

Best Regards,

Kerry

fmabrouk · ‎03-07-2021

Hi Kerry!

do you mean if I program the flash with a secure boot image, I don’t be able to use the board for debugging?

Will I still be able to erase the flash?

Whats the difference between HAB and BEE secure mode? Any documents to look at so that I get a better understanding between these two secure modes?

Regards,

Farid

kerryzhou · ‎03-07-2021

Hi fmabrouk,

https://github.com/JayHeng/NXP-MCUBootUtility

This readme is very good to help your understanding. It also mentioned the different secure mode.

About the HAB encrypted, it need the code is the none-XIP code, you need to run in RAM, not in the flash directly, but you can download to the flash. The encrypted code will copy from the external flash to the internal RAM, then decrypted it in the internal RAM and run it.

About the BEE, you can understand it, the encrypted code in the external XIP memory, it will decrypt it directly and run it.

Yes, if you encrypted it, then you can't debug it freely, that's why I tell you at first.

Normally, we consider the encrypted mode as the project design's last phase.

In my opinion, I think you can learn other knowledge at first. But if you have two MIMXRT1170EVK boards, you can use one board as the secured mode specifically. Another board is not secured.

Wish it helps you!

Best Regards,

Kerry

kerryzhou · ‎01-22-2021

Hi fmabrouk,

I find the newest SDK2.8.2 for RT1170 still don't have the MCUBOOT middleware, so how do you test it? with the RT106X?

This part, the MFGTool should still have issues.

So, I highly suggest you to use the MCUBootUtility, or use the host to download the code directly, just like the MCUBootUtility command:

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 50000 -u 0x1FC9,0x013D -j -- get-property 1 0
toolStatus: 0
commandOutput: {
"command" : "get-property",
"response" : [ 1258487809 ],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 50000 -u 0x1FC9,0x013D -j -- get-property 17 0
toolStatus: 0
commandOutput: {
"command" : "get-property",
"response" : [ 0 ],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 5242000 -u 0x1FC9,0x013D -j -- load-image C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\src\targets\MIMXRT1176\ivt_flashloader.bin
toolStatus: 0
commandOutput: {
"command" : "load-image",
"response" : [],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 50000 -u 0x15A2,0x0073 -j -- get-property 1 0
toolStatus: 0
commandOutput: {
"command" : "get-property",
"response" : [ 1258487808 ],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 50000 -u 0x15A2,0x0073 -j -- get-property 24 0
toolStatus: 0
commandOutput: {
"command" : "get-property",
"response" : [ 1409351680 ],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 50000 -u 0x15A2,0x0073 -j -- efuse-read-once 22
toolStatus: 0
commandOutput: {
"command" : "efuse-read-once",
"response" : [ 4, 0 ],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 5242000 -u 0x15A2,0x0073 -j -- read-memory 1074675776 4 C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\vectors\readReg.dat 0
toolStatus: 0
commandOutput: {
"command" : "read-memory",
"response" : [ 0 ],
"status" : {
"description" : "10200 (0x27D8) kStatusMemoryRangeInvalid",
"value" : 10200
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 5242000 -u 0x15A2,0x0073 -j -- fill-memory 538976256 4 3482320897 word
toolStatus: 0
commandOutput: {
"command" : "fill-memory",
"response" : [],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 50000 -u 0x15A2,0x0073 -j -- configure-memory 9 538976256
toolStatus: 0
commandOutput: {
"command" : "configure-memory",
"response" : [],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 5242000 -u 0x15A2,0x0073 -j -- fill-memory 538976256 4 3221225479 word
toolStatus: 0
commandOutput: {
"command" : "fill-memory",
"response" : [],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 5242000 -u 0x15A2,0x0073 -j -- fill-memory 538976260 4 0 word
toolStatus: 0
commandOutput: {
"command" : "fill-memory",
"response" : [],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 50000 -u 0x15A2,0x0073 -j -- configure-memory 9 538976256
toolStatus: 0
commandOutput: {
"command" : "configure-memory",
"response" : [],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 5242000 -u 0x15A2,0x0073 -j -- read-memory 805307392 1024 C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\vectors\flexspiNorCfg.dat 9
toolStatus: 0
commandOutput: {
"command" : "read-memory",
"response" : [ 1024 ],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\elftosb4\win>"C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\elftosb4\win\elftosb.exe" -f imx -V -c "C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\gen\bd_file\imx_application_gen.bd" -o "C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\gen\bootable_image\ivt_led_blinky_0x3000a000_unsigned.bin" "C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\apps\NXP_X-IMXRT1170-VAL_Rev.A2\cm7\led_blinky_0x3000a000.srec"
Section: 0x0
iMX bootable image generated successfully

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 2048000 -u 0x15A2,0x0073 -j -- flash-erase-region 805306368 49152 9
toolStatus: 0
commandOutput: {
"command" : "flash-erase-region",
"response" : [],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 5242000 -u 0x15A2,0x0073 -j -- fill-memory 538980352 4 4026531855 word
toolStatus: 0
commandOutput: {
"command" : "fill-memory",
"response" : [],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 50000 -u 0x15A2,0x0073 -j -- configure-memory 9 538980352
toolStatus: 0
commandOutput: {
"command" : "configure-memory",
"response" : [],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 5242000 -u 0x15A2,0x0073 -j -- write-memory 805310464 C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\gen\bootable_image\ivt_led_blinky_0x3000a000_unsigned_nopadding.bin 9
toolStatus: 0
commandOutput: {
"command" : "write-memory",
"response" : [],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 5242000 -u 0x15A2,0x0073 -j -- read-memory 805306368 46154 C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\vectors\bootableImageFromBootDevice.dat 9
toolStatus: 0
commandOutput: {
"command" : "read-memory",
"response" : [ 46154 ],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Executing: C:\KerryPC\tool\NXP-MCUBootUtility-2.4.0\tools\blhost2_3\win\blhost -t 50000 -u 0x15A2,0x0073 -j -- reset
toolStatus: 0
commandOutput: {
"command" : "reset",
"response" : [],
"status" : {
"description" : "0 (0x0) Success.",
"value" : 0
}
}

Until now, the MCUBOOT for RT1170 SDK still not launched.

I also try to use the RT106X MFGTool, but even I modify the related code, still meet issues.

Seems the MFGtool related data has issues, anyway, it is still in the internal SDK testing process.

Now, I highly recommend you use the MCUbootUtility tool, just like what I have told you, try it. Or you can use the blhost to test it directly, just like the MCUBootUtility tool command, you even don't need to use the MFGTool.

Best Regards,

Kerry

farid_mabrouk · ‎01-29-2021

@kerryzhou

Hello Kerry!

Thanks a lot for your generous support.

I still could not use the MCUBootUtility even after I followed your suggestion. I keep getting same errors I sent you before.

For our application, we don't need a GUI to program the flash and generate secure boot image. We need to do it in an automated fashion by using text scripts that has a list of commands. The question I have now is: can I generate secure boot image and program the flash using commands? All this can be done using MFG Tools, except the last part when I have to open MFGTOOL2 GUI.

Is it possible to just use command line instead of MCUBoot utility?

The last question I have is: we are looking for documentation on how to do secure OTA for this MCU imx RT1176. Do you have any? if not could you please give us documentation for secure OTA for imx RT1060?

Thanks a lot!

kerryzhou · ‎02-01-2021

Hi farid_mabrouk,

What's the python version you are using? I am using python 3.7.0.

About the command method, of course you can, in fact, the MCUbootUtility also use the command method to download the code, with sdphost, and blhost.

About secure OTA for imx RT1060, I will help you to check it internally.

But, about the secure question, it's better to create the case(email reply private) instead of the public community, as some secure software need the NDA.

Best Regards,

Kerry

fmabrouk · ‎02-01-2021

How can I send you private email?

kerryzhou · ‎02-02-2021

Hi fmabrouk,

1. About the RT1170 download command, in fact, I already give you all the related command in the previous reply, just like the MCUBootUtility log, it use the blhos download the flashloader to the internal RAM at first, then run the flashloader, and configure the external memory and download the app directly.