Hello Diego,
Yes, trying to send commands to the i.MX RT 1064,
Sorry, I am quit new to the i.MX processor, just trying to send some data to its RAM.
(We have a number of LPC based product which we program in production using jtag (SWD) and a serial interface.
Trying to see whether I can do that for new i.MX RT 1064 products too)
I send the following:
WRITE_FILE ADDRESS FORMAT DATA COUNT 4 BYTES not used RESERVED
0x04 0x04 0x20 0x28 0x00 0x00 0x20 0x00 0x00 0x00 0x08 0x00 0x00 0x00 0x00 0x00
Than I send 8 bytes (for test)
0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07
Now the i.MX sends back to me
0x56 0x78 0x78 0x56 0x89 0x23 0x23 0x89 (I had hoped for 4x 0x88)
If I repeat this simple test under jtag (swd), it works fine and I can read the data back.
I am sure I do something wrong, hoped the 89232389 response would give me a clue.
Best regards,
Thijs1
Hi @Thijs1
Thank you for your response and for your interest on our MCUs.
I recall that I have seen this return in the past with another customer, to him the ROM returned this because : the data size that he gave to the write-file command did not match the actual amount of data that he sent via UART.
I do not have experience interfacing the MCU to that low level without commands. But maybe you can check SDPHOST commands and find easily where the error lies, by decoding them.
Here I wrote an SDPHOST command example. https://community.nxp.com/t5/i-MX-Processors/Serial-download-detail-process/m-p/1794957/highlight/tr...
Also, please find attached the SDPHost user guide MBOOTSDPHOSTUG.
I hope this could help.
Diego
Hi @Thijs1
It seems that you are sending SDPHOST commands to the i.MX RT1064. Is this correct?
If yes, the 0x56787856 means that the MCU is on open life cycle ( no HAb settings)
I did not found a reference for the 0x89232389. But could you let me know further about the commands that you are using?
Also you need to be aware that the OC RAM area that you are targeting does not overlap with the area that the ROM bootloader is using.
I hope this could help.
Diego