About fuses when using the i.MX RT1021 SEC tool. I am trying to write to an i.MX RT1021 using the SEC tool. When I execute the write, the following dialog appears. It says "BURN FUSES", but I would like to leave the fuses as they were when shipped. I used the SEC tool to read the OTP configuration of the board I clicked OK on in the dialog and a brand new board, and compared them, but there were no differences. Where can I check the "user OTP configuration" in the dialog? Also, is it possible to use the SEC tool if the fuses are as they were when shipped? Best regards i.MXRT 102x Re: About fuses when using the i.MX RT1021 SEC tool. The content of my question has changed, so I have posted the following as a new question. Please post the answer there. https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Writing-to-the-QSPI-Flash-of-i-MX-RT1021-using-write-image-win/m-p/2083229#M34066 Best regards Re: About fuses when using the i.MX RT1021 SEC tool. In this thread, I have asked a question about not being able to write using write_image_win.bat, but this has not yet been resolved. I would like to summarize the current situation. - When writing to a brand new board using a bat file, the process that should say "Erase memory before writing image" is displayed as "failed." - Boards that have already been written to using the SEC tool can be written to using the bat file. The following are the questions I would like to ask. 1. Why can't I write to a brand new board using a bat file? 2. Is there anything I need to do to write to a brand new board using a bat file? 3. Is there a difference between a board that has already been written to using the SEC tool and a brand new board? Please answer. Best regards Re: About fuses when using the i.MX RT1021 SEC tool. Regarding the issue I am asking about, I have confirmed the same thing with a brand new i.MX RT1062 custom board. I am unable to write to QSPI Flash using write_image_win.bat even on the i.MX RT1062 board. Boards that have already been written to with the SEC tool can be written to using write_image_win.bat in the same way as the i.MX RT1021. I believe the i.MX RT1062 is in the same situation as the i.MX RT1021. Please tell me the steps to write to a brand new board using write_image_win.bat. Best regards Re: About fuses when using the i.MX RT1021 SEC tool. Thank you for your reply. I followed the procedure you provided to check the board that I was unable to write to in the previous post, and I was able to write to it. After that, I was able to write to this board by double-clicking write_image_win.bat. I prepared another new board and tried writing to it using write_image_win.bat using the following procedure, but it failed. 1. Start CMD directly from Windows 2. Move to the workspace folder 3. Run write_image_win.bat I will upload the log of the above procedure below. ### Parse input arguments ### ### Check presence of FlashLoader ### FlashLoader is not running yet, download and run it ### Check communication with target bootloader ### sdphost -u 0x1FC9,0x0130 -j -- error-status { "command": "error-status", "response": [ 4042322160 ], "status": { "description": "1450735702 (0x56787856) Hab Is Disabled (Unlocked)", "value": 1450735702 } } sdphost succeeded, HAB disabled ### Write FlashLoader ### sdphost -u 0x1FC9,0x0130 -j -- write-file 0x20209000 "C:\Users\suzuki_y\Desktop\TEMP\NX_temp\NX-RT1021\NX-RT1021_\bootable_images\unsigned_MIMXRT1020_flashloader.bin" Status (HAB mode) = 1450735702 (0x56787856) Hab Is Disabled (Unlocked). Response status = 2290649224 (0x88888888) Write File Success. sdphost succeeded, HAB disabled ### Start FlashLoader ### sdphost -u 0x1FC9,0x0130 -j -- jump-address 0x20209000 Status (HAB mode) = 1450735702 (0x56787856) Hab Is Disabled (Unlocked). sdphost succeeded, HAB disabled ### Waiting FlashLoader to be initialized for 3 seconds ### ### Timeout wait value can be adjusted from Preferences ### ### Check presence of FlashLoader ### blhost -t 2000 -u 0x15A2,0x0073 -j -- get-property 1 0 { "command": "get-property", "response": [ 1258424320 ], "status": { "description": "0 (0x0) Success.", "value": 0 } } blhost succeeded ### Configure FlexSPI NOR using FCB on address 0x2000 ### blhost -t 5000 -u 0x15A2,0x0073 -j -- write-memory 0x2000 "C:\Users\suzuki_y\Desktop\TEMP\NX_temp\NX-RT1021\NX-RT1021_\source_images\nx_rt1021_Inspection.fcb_parsed.bin" { "command": "write-memory", "response": [ 512 ], "status": { "description": "0 (0x0) Success.", "value": 0 } } blhost succeeded blhost -t 5000 -u 0x15A2,0x0073 -j -- configure-memory 9 0x2000 { "command": "configure-memory", "response": [], "status": { "description": "0 (0x0) Success.", "value": 0 } } blhost succeeded ### Erase memory before writing image ### blhost -t 50638 -u 0x15A2,0x0073 -j -- flash-erase-region 0x60000000 63876 0 { "command": "flash-erase-region", "response": [], "status": { "description": "20106 (0x4e8a) FlexSPINOR: Command Failure.", "value": 20106 } } blhost failed It seems that once you write to it with the SEC tool, you will be able to write to it with write_image_win.bat, but you cannot write to a board that you have never written to before. Do you have any idea what this difference is? Also, is there any difference between double-clicking write_image_win.bat and running it from CMD? Best regards Re: About fuses when using the i.MX RT1021 SEC tool. Hi @takagi_y
Thank you for your reply, I am glad to know that your first problem was solved.
I understand that with the same board, you can use the SEC tool to write but, then after executing manually the write_win.bat, it fails and stops. The write button is only a trigger button to call the write_win.bat. I recommend you to follow the below to troubleshoot steps, to see where the write_image_win.bat stops.
1 Open the connection with target.
2 Test connection. It should be OK.
3 Open the CMD. The tool automatically opens the CMD on the current workspace.
4 Type the write_image_win.bat
5 Check the output on the CMD.
This way is easier to determine where it write_win.bat stops. Would you share the log?
Btw, If you have not changed any HW setting on the board, you only need to ensure that the RT1020 is on serial downloader before calling the write_win.bat.
I hope this helps,
Diego
Re: About fuses when using the i.MX RT1021 SEC tool. I just posted that the problem was solved, but a new problem has arisen. I am now able to write to a brand new board using the SEC tool, but when I try to write using write_image_win.bat in the workspace folder, the process stops midway (around @echo ### Erase memory before writing image ###). If I have already been able to write to a board using the SEC tool, I can also write to it using write_image_win.bat. Is there anything I should do before using write_image_win.bat to write to a brand new board? Best regards Re: About fuses when using the i.MX RT1021 SEC tool. Thank you for your reply. I created a different workspace as suggested and wrote to a new board, and no warnings were issued and I was able to write normally. Thank you for letting me know how to solve the problem. Best regards Re: About fuses when using the i.MX RT1021 SEC tool. Hi @takagi_y
Thank you for your reply!
You should not worry about 0x460 BOOT_CFG1 [1], by default (brand new MCU and new SEC tool workspace) it should be zero, I updated my picture on my previous comment for your reference, to let you compare easier. This fuse is burned (set to 1) by the tool if you select closed HAB life cycle and Authenticated HAB boot mode. If you have open HAB life cycle and Unsigned boot mode the tool will put this fuse to 0. I hope this explains the preset value on blue. I do not think this could be affecting you.
Btw, if you want to have whole available description of the fuses, please refer to the i.MX RT1020 Security Reference Manual and the Restricted Data Package for MCUXpresso Secure Provisioning Tool v10, they are available under NDA.
I noticed that you migth have set whole 0x470 BOOT_CFG2 to zero , which is ok, probably the tool understands this as your custom User OTP configuration. Please create another workspace and see if the warning persists.
Anyway, I did not found any problems with your fuse settings, I think you should be able to keep developing on Unsigned boot mode. Have you seen any problems? If you do, please let me know.
Diego Re: About fuses when using the i.MX RT1021 SEC tool. I was checking the User Guide and noticed something that bothered me, so I would like to ask an additional question. The following is written on page 39 of the "MCUXpresso Secure Provisioning Tool User Guide v.10". "The hexadecimal value required by SEC or by the user. Values preset by SEC are highlighted in blue and can be modified only in Advanced mode." The BOOT_CFG1 in the screenshot of the OTP configuration I uploaded the other day is displayed in blue. When I checked the bit display of BOOT_CFG1, the display of Restricted in bit1 was blue. I looked at page 1100 of the "i.MX RT1020 Processor Reference Manual" to check the contents of the settings, but bit0 of 0x460 was Reserved and could not be confirmed. Is it possible that this setting is affecting this? Best regards Re: About fuses when using the i.MX RT1021 SEC tool. Thank you for your reply. Below is the image of the OTP configuration of the brand new board. The version of the SEC tool is version 10.0[b241106], and the OS is Windows 10 Pro. Best regards Re: About fuses when using the i.MX RT1021 SEC tool. Hi @takagi_y
The only place to check the "user OTP configuration" is on the below window. This is a picture from the RT1020-EVK at my desk. I think we have not manually programmed fuses before to it.
The warning you see tipically suggest that your OTP config contains a fuse value changed, but your description says you are not doing this. Could you show a picture of your OTP settings?
Here is an example of the Warning window, but because HAB is enabled.
You could still use the SEC tool if the fuses are as they were when shipped. However, lets review your OTP config to double check 🙂
Could you also let me know your SEC tool version and OS?
Best regards,
Diego
查看全文
