i.MX RT Crossover MCUsのトピックRe: USB Tethering example for iMXRT1064

USB Tethering example for iMXRT1064

billchadwick — Wed, 25 Jan 2023 17:09:00 GMT

Could you please add a version of the imXRT1060 SDK lwip_dhcp_usb_freertos example to the iiMXRT1064 SDK. We want to have a go with USB tethering from Android to an imxRT1064 EVK.

Is there a generalised procedure for moving a 1060 example to run on 1064? a wizard to do the conversion even?

Thanks.

Re: USB Tethering example for iMXRT1064

diego_charles — Thu, 26 Jan 2023 03:02:17 GMT

Hi @billchadwick

I hope you are doing well!

There is an application note that migth be useful to understand migration steps to move from RT1060 to RT1064.

Migration Guide from i.MX RT1060 to i.MX RT1064 (AN12290)

The other way arround is to import into a new RT1064 project SDK example libraries, link manually libraries and add preprocessor defines.

All the best,

Diego

Re: USB Tethering example for iMXRT1064

diego_charles — Thu, 26 Jan 2023 03:14:48 GMT

btw @billchadwick

I have not seen this example on the latest SDK release for RT1064 (v2.13)

I will inform internally about your request, but I there is no warranty of when (which release) this could be done.

Thanks for your understanding.

Diego

Re: USB Tethering example for iMXRT1064

billchadwick — Thu, 26 Jan 2023 16:26:38 GMT

That migration guide is pretty slim. It needs to explain how to do the migration of a project within MCUXpresso.

Re: USB Tethering example for iMXRT1064

diego_charles — Wed, 01 Feb 2023 15:59:08 GMT

Hi @billchadwick

Thanks for your reply! Yes, I agree the application note is very general.

For MCUXpresso project migration I recommend to start in a clean RT1064 project, the starting point it could be one from USB and freeRTOS. Below I wrote some general migration guidelines from my experience.

1 Copy RT1060 tethering folders and source files and paste them in your project. Make sure that folders are not excluded from build. Untick this option in folder properties.

diego_charles_2-1675266994662.png

2 I usually check original project settigns and I try to use the same on the target migration project. Below the most common ones.

Project properties >settings >tool settings > preprocesor, includes libraries

diego_charles_0-1675265967188.png

3 From project properties >settings >tool settings > also check Manage linker script , for more advanced linker settings and also check optimization.

4 Check memory layout project properties > MCU settings.

4 With MCUxpresso SDK component manager pull required/missing application drivers.

diego_charles_1-1675266913512.png

5 Review MPU settings, Board, clock and pin settings. Sometimes SDK projects are using Config tools to clock, peripheral settings.

6 Review (USB) applicaiton settings.

All the best,

Diego

Re: USB Tethering example for iMXRT1064

mjbcswitzerland — Thu, 02 Feb 2023 16:08:41 GMT

Hi
Apart from needing to change the start address from 0x60000000 to 0x70000000 the iMXRT 1064 is compatible with the iMX RT 1062 and so no further changes are necessary.
There is also HSUSB tethering in the uTasker project that works on all i.MX RT 10xx parts: https://www.utasker.com/iMX.html and allows emulation of the operation (including all HSUSB DMA and interrupts) in Visual Studio.
It supports both device and host tethered operation so that android <->iMX RT 1064 <-> additional tethered network (like GSM modem plus routing to i.MX RT 1064 Ethernet) is possible.
Regards
Mark

Re: USB Tethering example for iMXRT1064

billchadwick — Thu, 02 Feb 2023 16:43:32 GMT

Its more complicated than that. The Pins assignments has to change to access the on chip Flash rather than the off chip flash.

Re: USB Tethering example for iMXRT1064

mjbcswitzerland — Thu, 02 Feb 2023 16:55:56 GMT

Bill

Yes I oversimplified a bit - since the 1064 has a fixed W25Q32 in it and 1062 circuits can have various types (on FlexSPI) the flash config needs to be adjusted and any SPI Flash drivers will need to be replaced if different QSPI chips were used. Since the 1064 has internal flash it doesn't use any pins so their initialisation could be removed.

In my projects this is automated so all code runs on any i.MX RT and in any (supported) QSPI/HyperFlash flash so sometimes I forget some details.

However if you need to just run code for test (that doesn't access QSPI Flash) you can select the RAM target (which is offered when you import examples) and then there is 100% compatibility between a 1062 and 1064 target and thus no work to do at all to actually see the examples running.

Regards

Mark