Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Alex1982

Pages: [1]
1
STTM STM32 and STR91XF / how to configure SPI pins for bootloading (STM32F405)
« on: June 14, 2023, 06:25:11 PM »
Hello!
I'd like to create an SD bootloader for the STM32F405RGTx except I'm using SPI for the SD card interface, not SDIO

Can you please advise how to proceed to set up SPI card and where to define the SPI pins?

I'm using utaskerSerialBoot V1.4.3 within uVision Keil IDE, compiling fine!

Thanks in advance!

Regards
Alex

2
NXPTM M522XX, KINETIS and i.MX RT / Re: combining applications & jumping between them (uTasker+ teensy 3.2).
« on: March 15, 2022, 06:07:43 AM »
Hi Mark

You are correct, smaller SD cards mount faster.  ;D

Thanks!

3
NXPTM M522XX, KINETIS and i.MX RT / Re: combining applications & jumping between them (uTasker+ teensy 3.2).
« on: March 14, 2022, 03:51:14 PM »
Hello Mark

Thanks a million for your help, using bin files worked!

I can now load and boot teensy app from utasker bootloader, and jump to utasker USB-SD card at runtime!

The only question mark remaining is that it takes about 40-60seconds for the SD card to mount on OSX systems (tried several computers). The disk utility can see the device (grayed out) after about 12seconds, but it takes 30-40 seconds more to appear in the finder.
However on windows machines (win7 and win10) the SD mounts within 4-6 seconds

Does anything come to mind that could cause the delay?

Even at the slow mount speed it's already a victory, I can advise OSX users to be patient...

Thanks again for your great support!
Kind regards
Alex

4
NXPTM M522XX, KINETIS and i.MX RT / Re: combining applications & jumping between them (uTasker+ teensy 3.2).
« on: March 12, 2022, 08:03:17 AM »
Hello Mark

Thanks for your reply. I believe the format is correct (intel hex) as I'm specifying the -Intel in the command line:

srec_cat MAIN.hex -Intel SD.hex -Intel  -Output COMBINED.hex -Intel

The resulting COMBINED.hex works fine with the teensy loader on a blank MCU with MAIN.hex compiled with start address 0x00000000.
And it will happily jump to SD.hex and mount the SD card on a computer.

uTasker loader will accept and load MAIN.hex alone (compiled with start address 0x00005080)
but not when I attempt to combine with SD.hex (compiled start address 0x00038080).

Can you please advise what command I should for your uTaskerCombine.exe to combine:

 MAIN.hex(compiled with start address 0x00005080)
SD.hex (compiled start address 0x00038080).
The resulting HEX should have a start address of 0x00005080.

Thanks and sorry for ignorance!
Kind regards
Alex

5
NXPTM M522XX, KINETIS and i.MX RT / Re: combining applications & jumping between them (uTasker+ teensy 3.2).
« on: March 01, 2022, 04:10:51 PM »
Hello Mark
Many thanks for your quick response, 0x5080 is definitely fine (you kindly helped set it up for me at this address) - no problem uploading single applications.
The issue only occurs when trying to load combined applications (2 hex files combined with srec_cat).

Would it be possible to combine a teensy .hex with a utasker .bin (or .hex) using your uTaskerCombine.exe tool?
Thanks!
Kind regards
Alex

6
NXPTM M522XX, KINETIS and i.MX RT / combining applications & jumping between them (uTasker+ teensy 3.2).
« on: February 26, 2022, 11:03:55 AM »
Hello,

I wish to use a combination of 3 applications on MK20DX256 (teensy 3.2)

The main application is compiled in teensy/arduino and the second is uTasker1.4 and serves as USB-MSD allowing user to access an SD card within the device over USB.

I'm following the steps explained here.
https://github.com/pixelmatix/JumpToUsbMsdAppWithOffset/

To summarise:
Main application is located at 0x00000
USB-MSD is located at 0x38080
We jump from main to USB-MSD @ 0x38080

Everything works when flashing the 2 combined hexes to a blank MCU.

However I wish to use the 2 above applications on top of a third uTasker bootloader application:

0x00000 uTasker bootloader
0x05080 Main application
0x38080 USB-MSD

This is where I have an issue:
the uTasker bootloader won't accept the 2 combined applications (arduino application with 0x05080 start address and USB-MSD with start address 0x38080).
The bootloader won't reboot after transferring the combined hex

Must I change the USB-MSD start address (move forward by 05080?) to compensate for the bootloader offset?
I'm unsure if the address is absolute or relative to the starting address of the main application...

Many thanks in advance, sorry in advance if this is off topic and happy weekend!
Alex


Pages: [1]