Programming RT1050 via serial bootloader

cancel
Showing results for 
Search instead for 
Did you mean: 

Programming RT1050 via serial bootloader

692 Views
Contributor III

After designing the first RT1050-based board, I discovered a huge mistake (JTAG.MOD pin disconnected) so I have no JTAG/SWD interface

To remedy somehow, I am attempting to do some tests by downloading a firmware via SDPHOST.

Unfortunately, doing so triggers unexpected errors when attempting to write in the OCRAM area.

sdphost.exe -p com7 -- write-register 0x20200000 8 0x00
unexpected write response 0x89232389.
Status (HAB mode) = 1450735702 (0x56787856) HAB disabled.
Reponse Status = 2300781449 (0x89232389) REENUM Ack

Moreover, when attempting to read more than 4 bytes from the same location, another error occurs:

sdphost.exe -p com7 -- read-register 0x20200000 8 8
getStatusResponse.readPacket error 5.
Status (HAB mode) = 1450735702 (0x56787856) HAB disabled.

Of course the write-file command fails as well...

Any suggestions from you fellow engineers?

Please forgive me if I am asking stupid question or doing stupid errors. I am really new to RT1050.

Tags (2)
0 Kudos
4 Replies

74 Views
Senior Contributor II

@Giuseppe, I'm getting started with a 'RT1020, and I see similar results using imx_usb_loader.  I know the connection is up 'cause I do get 0x56787856 response to a status request; plus I am able to read a few registers that are as they should be; however, most other reads return 0x89232389.  I'm guessing there must be additional initialization that must be done, but have not stumbled on it as of yet.  What did you find?

0 Kudos

74 Views
Contributor III

Hi Ed, unfortunately I can't be of help, because in the end we were able to put MOD to ground and enable SWD for programming.

It is worth of mention that NXP modified the MOD pin that has now a pull-down instead than a pull-up, so when MOD is not connected, JTAG does not start in boundary scan (same behaviour than the majority of MCUs...)

74 Views
Senior Contributor II

Ok thanks for responding anyway... I've kinda concluded that the 0x89232389 must be some kind of valid-but-undocumented return code that is generated when attempting to access invalid addresses through the ROM serial loader.  That value "x89232389" is too similar in format to others (like x56787856).  I can't find any documentation on it, so I don't know for sure but when I changed my addresses a bit I found I did have some success with reading and writing through that interface.

0 Kudos

74 Views
NXP Employee
NXP Employee

You can also try this tool, with this tool, You can flash bare image into various boot devices easily and don't need to care about headers (ivt, boot data...)

GitHub - JayHeng/nxp-sec-boot-ui: A one-stop GUI tool to work with NXP MCU (Kinetis, i.MXRT, LPC) RO... 

0 Kudos