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 - bob_STM32

Pages: [1]
1
STTM STM32 and STR91XF / Re: STM32 Software Versions
« on: November 25, 2020, 04:40:15 PM »
This problem was immediately. The bootloader only accepts binaries. For some reason HEX and SREC files do not write.
Writing a binary file looks like this: it hangs for a few minutes, then quickly writes, restarts, and starts working.

2
STTM STM32 and STR91XF / Re: STM32 Software Versions
« on: November 25, 2020, 12:24:49 PM »
Hello. Help, please. The firmware is recorded through the bootloader very slowly 5k - 2 minutes. What could be the reason?

3
STTM STM32 and STR91XF / Re: STM32 Software Versions
« on: November 21, 2020, 05:33:42 PM »
Thank you, everything worked.
Tell me, please.
The documentation describes the possibility to program the controller not with a BIN file, but with a HEX file.
How can this be implemented?
What HEX file format do you need? Intel HEX?

4
STTM STM32 and STR91XF / Re: STM32 Software Versions
« on: November 19, 2020, 06:15:54 PM »
Hello!
As I understood correctly, to begin with I compile uTasker with a configuration "stm32_SerialLoader" with definition:
 #define "ARDUINO_BLUE_PILL".
 #define NEW_SOFTWARE_FILE "software.bin"
 #define VALID_VERSION_MAGIC_NUMBER 0x651c
 #define _SECRET_KEY {0x9c, 0x66, 0x9a, 0x00, 0x8f, 0x71}
I program the controller with this firmware.
The "UPLOAD_DISK" disk should appear on the system.
Then I create my program, which should be programmed through the bootloader with the start address 0x08004080.
Then the binary file of my program "soft.bin" and I transfer to the "Tools" folder.
In this folder I run the program "uTaskerConvert.exe" with the parameters:
uTaskerConvert.exe soft.bin software.bin -0x651c -9c669a008f71

A firmware called "software.bin" should appear in the "Tools" folder.
I copy this firmware to the "UPLOAD_DISK" disk.
After that, the program should run ...

I do everything as I wrote. After I transfer the firmware "software.bin" to the disk "UPLOAD_DISK", the disk does not reboot, control does not switch to my program. After rebooting, the "UPLOAD_DISK" disc opens blank.

Maybe I should add some more definitions for correct work?

5
STTM STM32 and STR91XF / Re: STM32 Software Versions
« on: November 17, 2020, 07:48:50 PM »
Hi,Mark !
Now i chose configuration "stm32_SerialLoader" , linkerscript "uTaskerV1_4\Applications\uTaskerV1.4\GNU_STM32\STM32F103_64_20.ld".
After build and download firmvare to BluePill, system find "UPLOAD_DISK" drive.
But after trying to write the "firmware.bin" file to it, a message appears that the recording is blocked and the disk seems to reboot, and the file with the firmware disappears.

As I understand it, the Loader.h file has a name, a magic number and a secret key.
     #define NEW_SOFTWARE_FILE "software.bin"
     #define VALID_VERSION_MAGIC_NUMBER 0x651c
     #define _SECRET_KEY {0x9c, 0x66, 0x9a, 0x00, 0x8f, 0x71}
And I need to convert the firmware with the uTaskerConvert utility.
How exactly to do it?

6
STTM STM32 and STR91XF / Re: STM32 Software Versions
« on: November 17, 2020, 11:18:54 AM »
Thank you for your help.
The device now opens as a "DATADISK1" flash drive.
LED_PC13 blink 2 times per/sec.
The flash drive has 3 files ram.bin, software.bin, uTasker.html.
The flash drive is not writable. You cannot delete or replace files.
How to make a project work like this https://www.utasker.com/stm32/BluePill.html
That the flash drive was empty, and it was possible to write the firmware?
The config.h file defines:
#define _TICK_RESOLUTION TICK_UNIT_MS (50)
#define USE_CORTEX_CYCLE_COUNTER
#define UNUSED_STACK_PATTERN 0x55
#define UREVERSEMEMCPY

#define FLASH_FILE_SYSTEM
  #if defined USB_INTERFACE
  #define USB_DEVICE_SUPPORT
#define USE_USB_MSD
#define FAT_EMULATION

P.S Definitions for USB_MSD mode are contained in the files of the uTaskerSerialBoot folder, but these files are not compiled with the uTaskerV1.4 project

7
STTM STM32 and STR91XF / Re: STM32 Software Versions
« on: November 16, 2020, 09:42:33 PM »
Hi! I need a help...
A clone to GIT project to my local machine, and delete the original project files at the top of the project directory.
Then copy files from uTaskerV1.4\KinetisAtollic\Project_Settings  to top directory/
Then i import this project into Attolic true studio. Manager build configuration consist 3 variants of build: KinetisFLASH - uTaskerV1.4, KinetisSRAM - uTaskerV1.4 , Standalone FLASH build for STM32.
I choose Standalone FLASH build for STM32.
In Project -> properties->C Linker->general, in dialog "linker script" choosing "Applications\uTaskerV1.4\GNU_STM32\STM32F103_64_20.ld"
In Project -> properties->C/C++ General->Patch and symbols->Sumbols seted variables _GNU and _STM32
In file config.h from folder Application->uTaskerV1.4 i defined  #define ARDUINO_BLUE_PILL.
Build Finished succesfull.
After load HEX file into BluePill, Led PC13 blinking, but but on USB there is no connection.

Maybe somewhere else there are some settings that affect the USB connection?

8
STTM STM32 and STR91XF / Re: STM32 Software Versions
« on: November 15, 2020, 12:50:49 PM »
And one more. How to use Atolic true studio to create a bootloader for STM32F103C8T6 similar to uTaskerSerialLoader_BluePill_USB-MSD, but without wachdog?
Which archive to choose for compilation?

9
STTM STM32 and STR91XF / Re: STM32 Software Versions
« on: November 15, 2020, 12:26:19 PM »
Hello, there is no configuration for the STM32F103C8T6 processor (Blue Pill) in the archive. How do I add such a configuration?
Maybe there is another version of the project where Blue Pill is added?

Pages: [1]