So i managed to generate and flash it with K_128_16.ld file, seems like it can work, just SRAM lower is not used by bootloader. Led is blinking all the time(5Hz i guess), even when i power without bootpins asserted(probably missing application file)
When i plug my board UPLOAD_DISK appears with some random files in it (attached pictures) and i can't copy anything into it(not enough space)
Could u please tell me what i've done wrong? because at this point there is no way to move anything into that storage.
Back to my main application, i've read some posts and looked through Loader.h and it seems like it uses 32*1024 +80 which gives 0x8080 start point of my application.
I've made some changes ( correct me if they're wrong) . Added 2 lines in main code:
SCB -> VTOR = 0x20000000;
memcpy((uint32_t*)0x20000000,(uint32_t*)0x00008080,0x200);
And changed memory as shown on the picture below:
Hi Grzegorz
I don't believe in lucky chances or black magic when developing embedded firmware (although sometimes one indeed has the feeling that there is a mischievous gremlin corrupting things that you are convinced you are doing right, until you realise what are you doing wrong...).
If you open the project in Visual Studio and run the simulator it immediately shows you the problem:
#define UTASKER_APP_START (32 * 1024) // application starts at this address
#define UTASKER_APP_END (unsigned char *)(UTASKER_APP_START + (128 * 1024))
Since your chip has 128k of flash the application range is too large. What is happening is that there is a check at startup to see whether this range is blank and that crashes when checking beyond the end of flash.
The reason why you didn't see this when you had non-blank flash is because the check already quit since it had already found non-blank content - meaning it don't have to check so far and find it crashed.
Since you have RUN_FROM_HIRC enabled it overwrites the crystal settings (if you look carefully you should find these defines are not active and are displayed grayed out by the editor).
Therefore it will be Ok if you change the application size to
#define UTASKER_APP_END (unsigned char *)(UTASKER_APP_START + (96 * 1024))
for example.
Or
#define UTASKER_APP_END (unsigned char *)(SIZE_OF_FLASH - UTASKER_APP_START)
will work if you automatically want to use all remaining flash (although often one keeps an area for saving parameters to that is preserved across firmware uploads).
I checked your LED setup and it is good.
Your force loader switch is not quite right yet and would cause the next crash:
#define SWITCH_4 (PORTA_BIT5)
#define FORCE_BOOT() (!_READ_PORT_MASK(A, SWITCH_4))
There is however nothing configuring the port input before use so you need to also have:
_CONFIG_PORT_INPUT_FAST_LOW(A, (SWITCH_4), PORT_PS_UP_ENABLE);
somewhere.
You can add this to the INIT_WATCHDOG_DISABLE() macro, where the original switch input was being configured.
After this I expect full functionality. When I run it after these modification the simulation shows your chip giving correct USB operation, the LED on PTC2 blinking and the correct input configured:
Good luck
Regards
Mark
I'm not sure if you're looking at uTaskerSerialBoot because even if i got #define RUN_FROM_HIRC , OSC defines are not grayed(blacked in dark theme) which is shown on the pic below.
I changed everything u suggested and still no success. Attaching new modified files.
Seems like gremlins are still fiddling with me.
So i debugged bootloader and it hangs at irq_default causing hardfault. If u need more detailed photos i can provide them. Attached not working binary.
I'm not sure what clocks exactly bootloader uses(i only know that it uses IRC48MHz for usb). So i've done something "crazy" and i created new project, commented out any clock initialization, debugged it, took a piece of paper and write down every clock register value, check in datasheet what exactly is default. After this i added "resetting" at the beginning of the code and it seems that i helped.
