Messages

31

NXP^TM M522XX, KINETIS and i.MX RT / Re: First Tests with SerialLoader, stuck on "File valid" from SD card?

« on: May 06, 2021, 01:42:00 PM »

Mark,

Thanks, I reinstalled the SerialLoader with the .bin file in your post and retried the (software.bin) SD-Card application update from SD Card and it worked!

What is the difference between the one you posted and the one on the EA iMXRT1062 page?

32

NXP^TM M522XX, KINETIS and i.MX RT / First Tests with SerialLoader, stuck on "File valid" from SD card?

« on: May 05, 2021, 02:30:09 PM »

Hello,

I have started to work with uTasker SerialLoader on an Embedded Artists iMX1062 EVK.  I can successfully write the Serial Loader with MCUBootUtility, but when I place "software.bin" on the SD card and the Loader picks it up, it just stops on "File valid".

If I used the USB-MSD method, by placing the software.bin from the PC on UPLOAD_DISK, then it works correctly.

Any ideas why it wouldn't use the software.bin directly from the SD card?

Here is a video of my entire process:

33

NXP^TM M522XX, KINETIS and i.MX RT / Re: NXP Secure Provisioning Settings for Bootloader on MIMXRT1060-EVP (and EA OEM)

« on: May 05, 2021, 01:23:04 AM »

I am in exactly the same boat. 

I run all my dev on Mac, I even wrote a cocoa app to run all of the sdp/blhost commands directly over USB, but things keep changing, and I can’t keep up with a desktop “updater” for my users. 

Things continually stop working or get locked down with IOKit.  The Windows side was a little easier, but I am not a desktop programmer.

So my hope is that my generic imxrt app can be seamlessly integrated with the uTasker Loader to take the desktop issues out of the equation.

I will try and post any tips I find along the way, and maybe we can from each other’s “journey”!

oh, and don’t update to Big Sur...  MCUXpresso isn’t really ready for it.

34

NXP^TM M522XX, KINETIS and i.MX RT / Re: NXP Secure Provisioning Settings for Bootloader on MIMXRT1060-EVP (and EA OEM)

« on: May 05, 2021, 12:50:12 AM »

I tried a similar path, using Secure Provisioning.
 Looking at the log output, and comparing to MCUBootUtility, the image location is not correct in Secure Provisioning.

 In my case it was 0x60001000 instead of 0x60000000.

 I don’t see a way to change this in Secure Provisioning.