topic Re: Trouble configuring uTasker bootloader for RT1024 in i.MX RT Crossover MCUs

Trouble configuring uTasker bootloader for RT1024

davenadler — Sun, 25 Feb 2024 04:02:36 GMT

No doubt I've missed something...

I have a custom board with USB OTG, and need to boot-load from a USB memory stick (USB host MSD load). As NXP's boot-loader doesn't seem to support this configuration, I'm trying the uTasker boot-loader. My board has no externally connected serial ports. I made a 'blinky' test application, verified it works as a normal application, then built it as a boot-loadable application per the instructions. I configured, built, and installed the boot-loader - all seems OK. But when I insert the USB stick with "software.bin" the stick's LED comes on, briefly blinks off, then stays on - but blinky is never loaded and executed.

Some basic questions:

I didn't find any way to disable all serial communications in uTaskerSerialBoot\config.h.
Do I need to do this? If so, how?
Is there a way to configure "serial loader" to report (printf) step-by-step diagnostics to a file on the USB stick? That's how I debugged the last bootloader I had to implement for a no-serial board.

Excruciating details of my configuration and test in the attached PDF, along with the relevant configuration files.

@mjbcswitzerland- any help much appreciated!

Thanks!
Best Regards, Dave

Re: Trouble configuring uTasker bootloader for RT1024

mjbcswitzerland — Sun, 25 Feb 2024 13:05:59 GMT

Hi Dave

To remove all serial mode support in the loader simply comment out
#define SERIAL_INTERFACE
This will remove the LPUART driver and all modes that are associated with the serial interface (and all debug output via UART).

Without the serial debug output it is not possible to know exactly what is happening but I would suggest using

#define FORCE_BOOT() 1 // always start the serial loader
#define RETAIN_LOADER_MODE() 0 // never stay in the serial loader after checking the application

since this will cause the loader to always start and always jump to the application after checking. As you don't have any GPIO to control this it may be that the ones used are causing the RETAIN_LOADER_MODE() to stay in the loader and not start your application (for example).

You have an error in the LED toggle:
#define TOGGLE_WATCHDOG_LED() _TOGGLE_PORT(1, BLINK_LED)

This should be
#define TOGGLE_WATCHDOG_LED() _TOGGLE_PORT(3, BLINK_LED)

since you have moved it to port 3.
This is in fact a potentially serious error since the watchdog task will be writing to a non-initialised port and it may result in a hard fault.
Note that when the serial loader is running its heartbeat LED is expected to be flashing at 5Hz and not remain static.

If you would like to simplify the generation of the loader you can also do this:
- Edit the file \Applications\uTaskerSerialBoot\GNU_iMX\CompleteLoaderBuild.bat
-- set its target to yours (set iMX_RT=MIMXRT1024)
-- ensure its tools path points to your MCUXpresso tools directory (for the GCC compiler)
- Double click the bat file and it will build all loaders in the correct order without needing MCUXpresso and the manual builds
-- MCUXpresso build is useful if debugging of the code is required but the bat file build is easier to generate operating binaries

I don't know exactly what the light on the stick means but it sounds as though it has power (but check your HW to ensure no power enabling is needed - if so these macros can be used
#define USB_HOST_POWER_CONFIG()
#define USB_HOST_POWER_ON()
#define USB_HOST_POWER_OFF()
)
The memory stick LED flash 'may' be activity but may also have no meaning in this case.

It would be possible to log to the memory stick (rather than use serial output) by opening a file

static UTFILE utLogFile = {0};
utOpenFile("log.txt", &utLogFile, ptr_utDirectory[0], (UTFAT_OPEN_FOR_WRITE | UTFAT_TRUNCATE | UTFAT_CREATE)); // open/create a log file in the root directory (ptr_utDirectory[0] is the root, as configured already in disk_loader.c)
and write any output to it with utWriteFile(&utLogFile, "text", 4); // example of writing to the log file
but this assumes that the memory stick has enumerated and the file system has mounted and if you have issues before this point it won't help.

There is a set of debug outputs used during the loading process and these could also be modified to signal states on LEDs instead:
#define _DISPLAY_SD_CARD_NOT_PRESENT() fnDebugMsg("Mem-Stick not present\r\n")
#define _DISPLAY_SD_CARD_NOT_FORMATTED() fnDebugMsg("Mem-Stick not formatted\r\n")
#define _DISPLAY_SD_CARD_PRESENT() fnDebugMsg("Mem-Stick present\r\n")
#define _DISPLAY_VALID_CONTENT() fnDebugMsg("File valid\r\n")
#define _DISPLAY_INVALID_CONTENT() fnDebugMsg("File invalid\r\n")
#define _DISPLAY_SW_OK() fnDebugMsg("Software OK\r\n")
#define _DISPLAY_SW_UPDATED() fnDebugMsg("Software Updated\r\n")
#define _DISPLAY_ERROR() fnDebugMsg("Update failed\r\n")
#define _DISPLAY_OVERSIZE_CONTENT() fnDebugMsg("File oversized!\r\n")

Note that, unlike USB devices, USB host can be easily debugged using the debugger so normal debugging with your debugger may be just as easy.

If the above doesn't help, please post the test application you are try to load via the stick.

Note that the operation can also be fully tested in the uTasker simulator where you can put your application file onto an emulated memory stick. The simulator is started and the memory stick is inserted using the menu "USB | Attach High Speed Device" which will allow the complete code (USB driver, interrupts, DMA, file system and serial loader application with your application binary) to be tested and debugged in the much more powerful Visual Studio debugging enviroinment.

Even if your HW doesn't have serial output the simulator can be used to see the debug messages and here is a typical session when a stick is inserted (in this case file is oversized and so it aborts)

uTasker Serial Loader V2.4
===========================
[0x60020100/0x6009ffff]
bc = blank check
dc = delete code
ld = start load
bt = start boot loader
go = start application
> No Application!!
No Application!!
USB HS device detected
USB device information ready:
USB2.0 device with 64 byte pipe
Vendor/Product = 0x1d0d/0x0213
Manufacturer = "TDKMedia"
Product = "MSD "
Serial Number = "12345"

Bus-powered device (max. 200mA) with 1 interface(s)
Mass Storage Class : Sub-class = 0x06 interface protocol = 0x50
Endpoints:
2 = BULK IN with size 64
2 = BULK OUT with size 64
3 = INTERRUPT with size 2 (interval = 125us)
Enumerated (1)
LUN = 1
UFI INQUIRY -> Status transport - Passed
UFI REQUEST SENSE -> Status transport - Passed
UFI FORMAT CAP. -> (3:512:16777216) Status transport - Passed
UFI READ CAP. -> (16785408:1016575) Status transport - Passed
Mem-Stick mounting...
***Mem-Stick present
*File oversized!

If you post the (application) binary you have I can do this and check that it works - if it does it signals likely HW differences rather than FW / configuration issues.

Regards

Mark (uTasker project lead)

For our discounted i.MX and Kinetis stock availability see https://www.utasker.com/Shop/semi.html

Re: Trouble configuring uTasker bootloader for RT1024

davenadler — Sun, 25 Feb 2024 16:17:49 GMT

Thanks @mjbcswitzerland ! Better but still no joy.
USB power is AOK (hardware controlled by OTG cable jumper; my application reads/writes stick OK).
Here's what I've done:

found and commented out //#define SERIAL_INTERFACE
corrected port number in TOGGLE_WATCHDOG_LED() - hope I haven't missed any other hard-wired port numbers...
set #define FORCE_BOOT() 1 // DRN: always start serial loader
set #define RETAIN_LOADER_MODE() 0 // DRN: never stay in serial loader after checking application
enabled #define UTFAT_WRITE
I added debug output code below but got no trace file on the memory stick

Behavior now:

LED fast-blinks ~3Hz
On inserting USB stick, hiccup in fast-blink so probably mounting stick and failing later.

I've attached complete blinky project. #define USE_EVK_LED to change back to EVK's LED port definition.

My trace attempt in driver.c:

extern UTDIRECTORY *ptr_utDirectory[/*SDCARD_FILE_COUNT*/]; // DRN // pointer to directory objects extern QUEUE_TRANSFER fnDebugMsg(CHAR *cToSend) { #if 0 static FILE * traceFileFP; if(traceFileFP==0) traceFileFP = fopen ("BLtrace.txt", "w"); if(traceFileFP) { fputs(cToSend,traceFileFP); fflush(traceFileFP); // fclose(traceFileFP); } return 0; #elif 1 static UTFILE utLogFile = {0}; static bool fileOpenedOK; if(!fileOpenedOK) { int r = utOpenFile("BLtrace.txt", &utLogFile, ptr_utDirectory[0], (UTFAT_OPEN_FOR_WRITE | UTFAT_TRUNCATE | UTFAT_CREATE)); // open/create log file in root if(r == UTFAT_PATH_IS_FILE) fileOpenedOK=true; } if(fileOpenedOK) utWriteFile(&utLogFile, (unsigned char *)cToSend, strlen(cToSend)); return 0; #else return (fnPrint((unsigned char *)cToSend, DebugHandle)); // send to debug port #endif }

Is there a convenient way to change the LED blink rate (so I can set rate in #define _DISPLAY_ macros)?

Thanks Mark!

Re: Trouble configuring uTasker bootloader for RT1024

davenadler — Fri, 01 Mar 2024 19:06:57 GMT

Hi @mjbcswitzerland - I made an in-memory buffer for the diagnostic messages (in uTasker/Driver.c function fnDebugMsg),
and attached to the running process to see the results.
Looks like some kind of error occurred while mounting the memory stick.
Here's what I see in the debug log (stick inserted before bootloader started):

USB HS device detected
USB device information ready:
USB2.0 device with 64 byte pipe
Vendor/Product = 0x058f/0x6387
Manufacturer = "Generic"
Product = "Mass Storage"
Serial Number = "FEBB4044"
Bus-powered device (max. 100mA) with 1 interface(s)
Mass Storage Class : Sub-class = 0x06 interface protocol = 0x50
Endpoints:
1 = BULK OUT with size 512
2 = BULK IN with size 512
Enumerated (1)
LUN = 1
UFI INQUIRY -> Status transport - Passed
UFI REQUEST SENSE -> Status transport - Passed
UFI FORMAT CAP. -> H:2 0x02008140 0xf0406001 0x02008100
HS USB error - 0
Stall on IN EP-2
Cleared IN EP-2
Status transport - UFI FORMAT CAP. -> (2:512:2035712) (0:512:2035712) H:2 0x02008140 0xf0406001 0x02008100

HS USB error - 0
Stall on IN EP-2
Cleared IN EP-2
Status transport - Passed
UFI READ CAP. -> (512:2035711) Status transport - Passed
Mem-Stick mounting...
* TOD
Status transport - Passed
READ:No Application!!

Any idea what is going wrong?
What's this "No Application!!" about?
Thanks!
Best Regards, Dave

PS: I see "No Application!!" is when the boot-loader tries to branch to an application but there's none present.
If I plug in the stick after the boot-loader is running, here's what's in the debug log (Stops after "READ:"):

No Application!!
No Application!!
USB HS device detected
USB device information ready:
USB2.0 device with 64 byte pipe
Vendor/Product = 0x058f/0x6387
Manufacturer = "Generic"
Product = "Mass Storage"
Serial Number = "FEBB4044"

Bus-powered device (max. 100mA) with 1 interface(s)
Mass Storage Class : Sub-class = 0x06 interface protocol = 0x50

Endpoints:
1 = BULK OUT with size 512
2 = BULK IN with size 512
Enumerated (1)
LUN = 1
UFI INQUIRY -> Status transport - Passed
UFI REQUEST SENSE -> Status transport - Passed
UFI FORMAT CAP. -> H:2 0x02008140 0xf0406001 0x02008100
HS USB error - 0
Stall on IN EP-2
Cleared IN EP-2
Status transport - UFI FORMAT CAP. -> (2:512:2035712) (0:512:2035712) H:2 0x02008140 0xf0406001 0x02008100
HS USB error - 0
Stall on IN EP-2
Cleared IN EP-2
Status transport - Passed
UFI READ CAP
. -> (512:2035711) Status transport - Passed
Mem-Stick mounting...
* TOD
Status transport - Passed
READ:

PPS: I tried with a new very fast USB stick and it went into the following loop (when USB stick inserted at startup or later):

USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
USB device removed
Mem-Stick unmounted
USB HUSB HHHH

Re: Trouble configuring uTasker bootloader for RT1024

mjbcswitzerland — Sun, 25 Feb 2024 23:22:32 GMT

Hi Dave

In the task configuration file TaskConfig.h the watchdog task's characteristics are defined, whereby it is called once immediately and then repeatedly every 100ms (giving 5Hz LED waveform)

{ "Wdog", fnTaskWatchdog, NO_QUEUE, 0, (DELAY_LIMIT)(0.1 * SEC), UTASKER_GO}, // watchdog task (runs immediately and then periodically)

You can change the rate by adjusting the (0.1 * SEC) value.

I loaded the serial loader (with UART enabled) onto the MIMXRT1024-EVK. The LED doesn't flash since you have moved it but I could load your application and it ran (I don't see it blinking since it is on a different port) but when I connect with a debugger it is in a loop in valid XiP flash range.

This is the output:

uTasker Serial Loader V2.4
===========================
[0x60020100/0x6009ffff]
bc = blank check
dc = delete code
ld = start load
bt = start boot loader
go = start application
> USB device information ready:
USB2.0 device with 64 byte pipe
Vendor/Product = 0xcd12/0xef18
Manufacturer = "USB "
Product = "DISK "
Serial Number = "0482DE22941182E"

Bus-powered device (max. 100mA) with 1 interface(s)
Mass Storage Class : Sub-class = 0x06 interface protocol = 0x50
Endpoints:
2 = BULK OUT with size 512
2 = BULK IN with size 512
Enumerated (1)
LUN = 1
UFI INQUIRY -> Status transport - Passed
UFI REQUEST SENSE -> Status transport - Passed
UFI FORMAT CAP. -> (2:512:511744) Status transport - Passed
UFI READ CAP. -> (512:511743) Status transport - Passed
Mem-Stick mounting...
***Mem-Stick present
*************************************************************************************************************************************************************************************************************************************File valid
*****************************************************************************************************************************************************************************************************************Software Updated

When I plug the memory stick sometimes I see

USB device removed
Mem-Stick unmounted
USB device removed
Mem-Stick unmounted
USB device removed
Mem-Stick unmounted
USB device removed
Mem-Stick unmounted
USB device removed
Mem-Stick unmounted

when it is plugged slowly and 'bounces' but then it detects it normally and continues.

In the case of your fast memory stick I don't know why it doesn't enumerate but perhaps it is USB3 only (?) whereas the i.MX RT supports USB2.

In your log you have

HS USB error - 0
Stall on IN EP-2
Cleared IN EP-2

which is a USB stall due to the memory stick not supporting a certain MSD command. There is indeed a USB error due to the stall but it is normal and recovers with the endpoint clear (a method used by the USB protocol).

In usb_host_loader.c
there is a local define
//#define SKIP_READ_FORMAT_CAPACITY
which removes a command that is often not supported and not really relevant, which could be enabled.

The actual error that you have is when the mass storage module (utFAT) tries to mount the stick and performs sector reads. It uses utReadMSD() (in usb_host_loader.c) to issue read commands but there is no answer within the expected time limit:

if (++iWait > MAX_USB_MSD_READ_WAIT) { // limit the maximum wait in case the memory stick fails
fnDebugMsg(" TOD\r\n"); // timeout
return UTFAT_DISK_READ_ERROR;
}

You could try increasing the wait time:
#define MAX_USB_MSD_READ_WAIT (500000)

I think I remember having a stick once that wouldn't read until I enabled SKIP_READ_FORMAT_CAPACITY but it worked fine with Windows. When I checked the windows behavior it also didn't issue the READ_FORMAT_CAPACITY - possibly because they know that it can cause issues(?).

Regards

Mark

Re: Trouble configuring uTasker bootloader for RT1024

davenadler — Sun, 25 Feb 2024 23:45:19 GMT

Hi Mark - I should have mentioned:
Both USB sticks I am testing with work fine on this hardware using tinyUSB.

The infinite loop I see is different from what you mention above and happens even if the USB stick is already plugged in when boot-loader started:

USB HS device detected
USB device removed
Mem-Stick unmounted
USB HS device detected
...

I will increase the time-out delay and see if the slow stick will mount.
Still need to find out why the fast stick goes into an infinite loop...

Thanks,
Best Regards, Dave

Re: Trouble configuring uTasker bootloader for RT1024

davenadler — Fri, 01 Mar 2024 16:47:45 GMT

@mjbcswitzerland- Some success!
I increased the #define MAX_USB_MSD_READ_WAIT timeout by a factor of 10 and now blinky boot-loads and runs. Yay
Also:
- restarting board with no stick present shows boot-loader correctly branch into the application.
- restarting again with stick reloads application and starts it

Now - What to do about the fast stick that doesn't work?
It's a SanDisk ExtremePro 128GB with exFAT file system (again, works fine on this hardware with tinyUSB).

Thanks Mark!

Re: Trouble configuring uTasker bootloader for RT1024

mjbcswitzerland — Mon, 26 Feb 2024 00:26:57 GMT

Dave

>>restarting again with stick reloads application and starts it

In this case it is verifying that the code matches the loaded one and starts it (also if the source on the drive is stored in encrypted form) - it doesn't reload it again since that takes longer and would "wear out" the QSPI over time.

In the case of the stick that is not enumerating that doesn't show any information about the enumeration process it is not something that I have experienced and the reason is only visible with the debugger or with a USB analyser. It may be something trivial since the enumeration is carried out only on EP0 and is not dependent on what the device does later - the enumeration sequence is always the same - a few descriptors are requested and then the details are shown:

USB device information ready:
USB2.0 device with 64 byte pipe
Vendor/Product = 0xcd12/0xef18
Manufacturer = "USB "
Product = "DISK "
Serial Number = "0482DE22941182E"

Bus-powered device (max. 100mA) with 1 interface(s)
Mass Storage Class : Sub-class = 0x06 interface protocol = 0x50
Endpoints:
2 = BULK OUT with size 512
2 = BULK IN with size 512
Enumerated (1)

after which I would expect any special behavior to start.

The enumeration is controlled by fnHostEnumeration() in USB_drv.c which is generic for ever possible device.
You could add your debug output to there to see how often it is called and how the state-event machine progresses to get an idea of whether it aborts somewhere due to unexpected behavior.

If you have a USB analyser you could send a recording of an operating case and a failed case.

Regards

Mark

Re: Trouble configuring uTasker bootloader for RT1024

davenadler — Mon, 26 Feb 2024 00:35:08 GMT

@mjbcswitzerland Any chance you could get one of these sticks and have a look?
Also, you do support exFAT, right?
Thanks!

Re: Trouble configuring uTasker bootloader for RT1024

mjbcswitzerland — Mon, 26 Feb 2024 01:53:03 GMT

Please can you confirm that this is the one I would need to order?

https://www.digitec.ch/de/s1/product/sandisk-extreme-pro-128-gb-usb-a-usb-stick-6073315?ip=SANDISK+Extreme+Pro+USB

The utFAT used is FAT12/16/32. I was told by someone that they could work with exFAT formatted drives (although files > 4GBytes can't be worked with) but I was surprised but never checked myself.
If you could format the drive that works as exFAT instead of FAT you could check whether it is true or not.

Regards

Mark

Re: Trouble configuring uTasker bootloader for RT1024

davenadler — Mon, 26 Feb 2024 02:26:39 GMT

Yes that's exactly the drive. I'm using them because of speed and capacity (for the data-logging in this project). I'm a bit concerned about the power consumption though; they get warm...

Re: Trouble configuring uTasker bootloader for RT1024

mjbcswitzerland — Mon, 26 Feb 2024 04:00:09 GMT

OK. I ordered one and should be able to test it on Tuesday.

Re: Trouble configuring uTasker bootloader for RT1024

mjbcswitzerland — Wed, 28 Feb 2024 17:17:20 GMT

Dave

I received the drive and did a first quick measurement with my USB analyser and MIMXRT1024EVK running the MSD-host:

1. A typical HW device connection:

seen when connecting various devices (memory sticks, mobile phones, serial cables, wifi modules, etc.)

2. Connecting this stick (which otherwise behaves as you have described)

The high speed handshake is normal after the USB reset but when the host tries to send the getDescriptor (as is the case when a device is detected) the data that it sends out is "mangled".
Instead of the SETUP being seen [that is the byte sequence 0x2d 0x00 0x10] the analyser sees (when I check the data in the Invalid packets, which are being repeated by the USB controller due to a bus problem)
0xbd 0x95
0xbd 0x79 0xe8
0x7d 0x79 0xe8
0xbd 0x79
0xbd 0x79
0xbd 0x76 0xf4
and other similar but random values before giving up.

Therefore my initial impression is that the stick is loading the bus much more that expected and the data is not being sent (being corrupted) or its power consumption is causing the voltages to drop to unreliable levels.

Alternatively it may be that the stick drives the bus for a short time and this corrupts any data the host sends.

Could you check in the operating stack how it configures the HSUSB transceiver to see whether is does anything special (like setting very high drive level) or whether it adds a delay before it sends the first data [comparing the operation with a windows host I see that there is 30ms delay between the HW detection and the getDescriptor start]?

This is the transceiver setup that I have always used (based on NXP references)

PMU_REG_3P0 = (PMU_REG_3P0_OUTPUT_TRG_3V200 | PMU_REG_3P0_BO_OFFSET_175mV | PMU_REG_3P0_ENABLE_ILIMIT | PMU_REG_3P0_ENABLE_LINREG | PMU_REG_3P0_VBUS_SEL_1); // enable current limited LDO output at 3.2V from VBUS1 input

USB_ANALOG_USB1_CHRG_DETECT = (USB_ANALOG_USB1_CHRG_DETECT_EN_B | USB_ANALOG_USB1_CHRG_DETECT_CHK_CHRG_B); // disable charger detection

phy->USBPHY_TX = ((phy->USBPHY_TX & ~USBPHY_TX_DCAL_VALUE) | 0x0c); // trim the nominal 17.78mA current source for the high speed drivers (USB_DP and USB_DM) (taken from NXP reference)

but maybe they have changed something after encountering such devices (?)

Regards

Mark

Re: Trouble configuring uTasker bootloader for RT1024

davenadler — Fri, 01 Mar 2024 20:20:06 GMT

Tut mir leid, es ist feierabend. Ich bin wieder bei der arbeit am 20/3/2024. Or so says my girlfriend.

And when I get back I have a lot of work to do (like rework NXP's astonishingly bad LPSPI driver so it properly manages CS signals and byte ordering, which I must do to get my application working reliably)...

Sorry I'm not able to dig into this problem just now,
Thanks,
Best Regards, Dave

PS: Notes on my efforts so far are attached.

Re: Trouble configuring uTasker bootloader for RT1024

davenadler — Sat, 02 Mar 2024 17:14:54 GMT

Hi Mark - A quick search of my project's tinyUSB sources:

PMU->REG_3P0 = (PMU->REG_3P0 & (~PMU_REG_3P0_OUTPUT_TRG_MASK)) | (PMU_REG_3P0_OUTPUT_TRG(0x17) | PMU_REG_3P0_ENABLE_LINREG_MASK);

The symbol USB_ANALOG_USB1_CHRG_DETECT does not appear in my project.

Hope that helps!
Best Regards, Dave

PS: My project's complete USB initialization routine follows:

static void DRN_init_USB(void) { // If freeRTOS is used, IRQ priority is limited by max syscall ( smaller number is higher priority ) NVIC_SetPriority(USB_OTG1_IRQn, configLIBRARY_MAX_SYSCALL_INTERRUPT_PRIORITY); // Clock CLOCK_EnableUsbhs0PhyPllClock(kCLOCK_Usbphy480M, 480000000U); CLOCK_EnableUsbhs0Clock(kCLOCK_Usb480M, 480000000U); // Enable PHY support for Low speed device + LS via FS Hub USBPHY->CTRL |= USBPHY_CTRL_SET_ENUTMILEVEL2_MASK | USBPHY_CTRL_SET_ENUTMILEVEL3_MASK; // Enable all power for normal operation USBPHY->PWD = 0; // TX Timing uint32_t phytx = USBPHY->TX; phytx &= ~(USBPHY_TX_D_CAL_MASK | USBPHY_TX_TXCAL45DM_MASK | USBPHY_TX_TXCAL45DP_MASK); phytx |= USBPHY_TX_D_CAL(0x0C) | USBPHY_TX_TXCAL45DP(0x06) | USBPHY_TX_TXCAL45DM(0x06); USBPHY->TX = phytx; }

Re: Trouble configuring uTasker bootloader for RT1024

mjbcswitzerland — Fri, 08 Mar 2024 15:56:50 GMT

Dave

I experimented and identified how to get the stick working.

This is the line that is causing problems:
phy->USBPHY_TX = ((phy->USBPHY_TX & ~USBPHY_TX_DCAL_VALUE) | 0x0c); // trim the nominal 17.78mA current source for the high speed drivers (USB_DP and USB_DM) (taken from NXP reference)

since it causes the value 0x1006060f to be written.

It works when I change the line to

phy->USBPHY_TX = ((phy->USBPHY_TX & ~USBPHY_TX_DCAL_MASK) | 0x0c);

which then sets 0x1006060c.

Although I never had an issue with any other device the D_CAL resistor trimming code value of 0xf (+25%)

doesn't allow bus operation with this particular stick.

Notice that I had an error in the code since the masking of the field was not correct since it was masking with 0xc instead of with 0xf but, as noted, this difficulty was never experienced with any other device and so was "hidden".

However, reading the user's manual in more detail I find this (for the MIMXRT1024):

which in fact 'recommends' the use of 0x10000007 and not 0x1006060c as used by the SDK and also your project code. Those values are, according to this, potentially not certifiable.

I then checked in the MIMXRT1060 user's manual and find that other values are recommended there:

Due to this I tried the recommended values on the MIMXRT1024EVK and they worked OK.

This means that I have changed my own code base to set the recommended values, depending on processor type:

phy->USBPHY_TX = (USBPHY_TX_EDGECTRL_VALUE | USBPHY_TX_RSVD1_VALUE | USBPHY_TX_TXCAL45DP_VALUE | USBPHY_TX_TXCAL45DN_VALUE | USBPHY_TX_DCAL_VALUE);

where

#if (defined iMX_RT101X || defined iMX_RT102X || defined iMX_RT1064) #define USBPHY_TX_DCAL_VALUE 0x00000007 // recommended certifiable values for J/K levels #define USBPHY_TX_TXCAL45DN_VALUE 0x00000000 #define USBPHY_TX_TXCAL45DP_VALUE 0x00000000 #define USBPHY_TX_RSVD1_VALUE 0x00000000 #elif (defined iMX_RT104X || defined iMX_RT105X || defined iMX_RT106X) #define USBPHY_TX_DCAL_VALUE 0x00000008 // recommended certifiable values for J/K levels #define USBPHY_TX_TXCAL45DN_VALUE 0x00000200 #define USBPHY_TX_TXCAL45DP_VALUE 0x00020000 #define USBPHY_TX_RSVD1_VALUE 0x00000000 #else // original NXP SDK values #define USBPHY_TX_DCAL_VALUE 0x0000000c #define USBPHY_TX_TXCAL45DN_VALUE 0x00000600 #define USBPHY_TX_TXCAL45DP_VALUE 0x00060000 #define USBPHY_TX_RSVD1_VALUE 0x00000000 #endif

You can simply set
phy->USBPHY_TX = 0x10000007;
to verify until I have updated the code in the repo.

Regards

Mark

Re: Trouble configuring uTasker bootloader for RT1024

mjbcswitzerland — Fri, 08 Mar 2024 16:31:45 GMT

Dave

The bad news is however that the FAT can't work with exFAT since it thinks the stick is not correctly formatted.

USB HS device detected
USB device information ready:
USB2.0 device with 64 byte pipe
Vendor/Product = 0x0781/0x5588
Manufacturer = "SanDisk"
Product = "USB Extreme Pro"
Serial Number = "14A45679AE36"

Self-powered device with 1 interface(s)
Interface 0
Mass Storage Class : Sub-class = 0x06 interface protocol = 0x50
Endpoints:
1 = BULK IN with size 512
2 = BULK OUT with size 512
Enumerated [1]
LUN = 1
UFI INQUIRY -> Status transport - Passed
UFI REQUEST SENSE -> Status transport - Passed
UFI FORMAT CAP. -> H:1 0x02008140 0xf0406001 0x02008100
HS USB error - 0
Stall on EP-1
IN EP-1 cleared
Status transport - UFI FORMAT CAP. -> H:1 0x82008140 0xf0406001 0x82008100
HS USB error - 0
Stall on EP-1
IN EP-1 cleared
Status transport - UFI FORMAT CAP. -> H:1 0x82008140 0xf0406001 0x82008100
HS USB error - 0
Stall on EP-1
IN EP-1 cleared
Status transport - UFI READ CAP. -> (512:250085375) Status transport - Passed
Mem-Stick mounting...
Malformed - Non-formatted Memory stick

Does your project contain an exFAT implementation so that your embedded code can work with the stick?
Also, do you know the details about licensing exFAT since, although the specification for it has been open since 2019 [https://learn.microsoft.com/en-us/windows/win32/fileio/exfat-specification] it looks like it needs either royalty payments to Microsoft or membership of OIN (open invention network)?

Regards

Mark

Re: Trouble configuring uTasker bootloader for RT1024

davenadler — Fri, 22 Mar 2024 20:59:32 GMT

I use the widely-used Chan's FatFs, which supports exFAT. I've been using this for decades, in many successful projects (also boot-loaders for PIC32, etc.). In my current RT1024 project I've already done through-put tests writing very large data-logs to the fast (exFAT-formatted) USB stick. Works just fine (and fast enough for my logging requirements).
Hope that helps!

PS: No idea about licensing...

PPS: Your customers will see increasing numbers of exFAT-formatted sticks...

Re: Trouble configuring uTasker bootloader for RT1024

mjbcswitzerland — Sun, 10 Mar 2024 13:38:26 GMT

Dave

I didn't know that FatFS had exFAT support but I see that it was added in 2016 - three years before Microsoft released the specification - presumably the project developer had insider information or was a member of group with access to it. I read somewhere that there is a charge of $4 per devices using exFAT, payable to Microsoft via a few partner companies that collect it for them, but I don't know whether it is still valid or not.

So that your boot loader will not be restricted I added exFAT read capabilities yesterday to the utFAT that the uTasker loader uses so that I can list the stick content and read its files (I haven't checked very large files yet since I need to add some long long counters to ensure larger data than 4GBytes can be read but I am sure your FW upload won't need that immediately ;-). Also I haven't yet handled the date/time since they use a different format that I need to convert for listing functions - again not important for the loader since it only checks the name).

I'll check in the new support shortly: you just need to add #define UTEXFAT to the utFAT configuration section of config.h to enable the new capability whereby the application (serial loader) itself is not affected.

Below is the listing from my stick (I just added a couple of additional files to its delivered state) in the root directory. [Tested in the uTaskerV2.0 application since it supports testing various functions of the interface - also supporting the same on exFAT formatted SD cards].

Regards

Mark

Hello, world... MIMXRT1060 [Software 2]
Unique ID: 0x65f82946453849d2-500000ff
01.01.1970 00:00:08
Static memory = 0x000011a0
OS Heap use = 0x00000449 from 0x0002b000
Initial stack margin 0x0003bcb0
FlexRAM:
3 Code banks [0x00000000..0x00017fff]
13 Data banks [0x20000000..0x20067fff]
SPI Flash: ISSI 8MByte IS25LP064A
uFileSystem integrity
Granularity: 0x0001c000
Start: 0x600a0000
End: 0x607d3fff
uFileSystem size = 0x00734000
OK
USB DEVICE HOST
USB (1) HS device detected
USB device information ready:
USB2.0 device with 64 byte pipe
Vendor/Product = 0x0781/0x5588
Manufacturer = "SanDisk"
Product = "USB Extreme Pro"
Serial Number = "14A45679AE36"

Self-powered device with 1 interface(s)
Interface 0
Mass Storage Class : Sub-class = 0x06 interface protocol = 0x50
Endpoints:
1 = BULK IN with size 512
2 = BULK OUT with size 512
Enumerated (1) [1]
LUN = 1
UFI INQUIRY -> Enumerated (0) [1]
Status transport - Passed
UFI REQUEST SENSE -> Status transport - Passed
UFI FORMAT CAP. -> H:1 0x02008140 0xf0406001 0x02008100
HS USB error - 1
Stall (1) on EP-1
IN (1) EP-1 cleared
Status transport - UFI FORMAT CAP. -> H:1 0x82008140 0xf0406001 0x82008100
HS USB error - 1
Stall (1) on EP-1
IN (1) EP-1 cleared
Status transport - UFI FORMAT CAP. -> H:1 0x82008140 0xf0406001 0x82008100
HS USB error - 1
Stall (1) on EP-1
IN (1) EP-1 cleared
Status transport - UFI READ CAP. -> (512:250085375) Status transport - Passed
Mem-Stick mounting...
Disk E mounted

Serial number: 00
Software version V2.0.000
Device identification: uTasker Number 1

Main menu
===================
S         Configure serial interface
I         Go to I/O menu
A         Go to administration menu
O         Go to overview/statistics menu
U         Go to USB menu
u         Go to utFAT disk interface
help      Display menu specific help
quit      Leave command mode
u

Disk interface
===================
up         go to main menu
info       utFAT/card info
dir        [path] show directory content
dird       [path] show deleted directory content
dirh       [path] show hidden content
infof      [path] show file info
infod      [path] show deleted info
cd         [path] change dir. (.. for up)
comp       compare [file1] with [file2]
file       [path] new empty file
write      [path] test write to file
mkdir      new empty dir
rename     [from] [to] rename
trunc      truncate to [length] [path]
copy       [file1] to [file2]
hide       [path] file/dir to hide
unhide     [path] file/dir to un-hide
prot       [path] file/dir to write-protect
unprot     [path] file/dir to un-protect
print      [path] print file content
del        [path] delete file or dir.
format     [-16/12] [label] format (unformatted) disk
fformat    [-16/12] [label] full format (unformatted) disk
re-format [-16/12] [label] reformat disk!!!!!
re-fformat [-16/12] [label] full reformat disk!!!!!
sect       [hex no.] display sector
sectw      [hex no.] [offset] [val] [cnt]
help       Display menu specific help
quit       Leave command mode
>info

Disk (125042687 kBytes) FATex
Bytes per sector: 512
Cluster size: 524288
Directory base: 0x00010800
FAT start: 0x0000c000
FAT size: 0x00000800
Number of FATs: 1
LBA: 0x0000c800
Total clusters: 0x0003b9c0
Info sect: 0x00000000
Free clusters: 0x00000000
Next free: 0x00000000
>dir
Directory E:\

---A 00.00.1980 00:00          8600360 SanDiskSecureAccessV3.01_win.exe
---- 00.00.1980 00:00 <DIR>            SanDiskSecureAccess
---A 00.00.1980 00:00        225888525 Firmware_Packet_V1.03.152.zip
---A 00.00.1980 00:00             8739 left.txt
---A 00.00.1980 00:00             8739 right.txt
4 files with 234506363 bytes
1 directories, 134215168 kBytes free
E:\>

Re: Trouble configuring uTasker bootloader for RT1024

davenadler — Fri, 29 Mar 2024 19:36:31 GMT

Hi Mark - I finally ready to get back to the bootloader. I've just now finished hardware qualification of my board (for which I had to recode some buggy FSL stuff - grrrrrr). From your replies above I think the fixes to your bootloader I need are:

increase timeout time constant to support old slow USB sticks (done),
fix initialization of USB peripheral to correctly support new USB sticks,
incorporate updates to support exFAT

I've done the first. What's the most efficient way to get the remaining fixes?

Thanks!
Best Regards, Dave