|
LDmicro Forum - Test STM32F103 / Bluepill target under ldmicro |
|||
|
|
|
(you are viewing a thread; or go back to list of threads)
Test STM32F103 / Bluepill target under ldmicro (by José GILLES)
Bluepill board is a well known, cheap and powerfull board equiped with an STM32F103 32 bits ARM MCU ; it also works under arduino:
https://wiki.stm32duino.com/index.php?title=Blue_Pill http://www.rvq.fr/arm/bluepill.php It has 128 KB of flash, 20 KB of RAM, runs at 72 MHz and has 2 32 bit ports ; and standard ADC, PWM, USART, I2C and SPI peripherals working under ldmicro. It can be easily programmed with the low cost ST-Link-v2 compatible emulators: https://www.amazon.fr/Programm...lique-Downloader/dp/B01F37YMJ4 If you're interested, you can test it in a beta version under ldmicro32 (5.3a) available on my github in 3 languages, with required libraries: https://github.com/joegil95/LdMicro32 It's derived from ldmicro 5.3.0.4 This new Blupill target is only available in C mode but you can compile your ladder and upload it to the target without exiting ldmicro with a new flashMcu.bat file Test it and let me know ?
(no subject) (by Calubert)
Hola José GILLES, Esta tarjeta que propones en este foro, no es de el ARM-stm32xx que esta en el Software de LDmicro.
mi pregunta es como se asignan las patas (Pines) ya que este que pones el enlace es de 48 pines. Bonjour José GILLES, Cette carte que vous proposez dans ce forum, ne provient pas de l’ARM-stm32xx qui se trouve dans le logiciel LDmicro. ma question est de savoir comment les jambes sont assignées (Pins) puisque celui-ci que vous mettez le lien est 48 pins. Hello José GILLES, This card that you propose in this forum, is not from the ARM-stm32xx that is in the LDmicro Software. my question is how the legs are assigned (Pins) since this one that you put the link is 48 pins
(no subject) (by José GILLES)
Hi Calubert
It'not (not yet) in the official version but you can test it by downloading LdMicro32 v 5.3: https://github.com/joegil95/LdMicro32 Then run and choose the new micro in the list.
(no subject) (by José GILLES)
Calubert excepted, nobody is really interested in this wonderful target ? It'll be included in next official release of ldmicro.
(no subject) (by bfwolf)
Hi José GILLES
"nobody is really interested in this wonderful target ?" Some weeks ago, i suggested to add the STM32F103/Bluepill as ldmicro-target.. But the i never read any reaction by you on my suggestion, so i thought you weren't interested.. I was very happy and pleased, as i saw this post here and that you included the STM32F103/Bluepill in ldmicro, as i also think, this is a really nice and cheap alterantive for arduino-boards! :-) By the way: Did you know, that most (nearly all) STM32F103/Bluepill boards have 128KB of flash?? xD https://wiki.stm32duino.com/index.php?title=Blue_Pill If you order the STM32F103/Bluepill boards directly in china, the are really very cheap! I bought a batch of 5 boards for only 8€, shipping included !!! :-) Thank you very much for your work, José :-) Regards..
(no subject) (by Calubert)
Tranquilo SR,José GILLES, es demasiado novedoso, la gente esta como loca con alduino, cuando pueda comprare una para jugar ya que uso el atnega 2560 y tiene muchas patillas que me sobran segun proyecto.
yo no estoy muy relacionado con C++, yo soy programador de PLC y toco la mayoría de PLC del mercado. la verdad tranquilo siempre habrá alguien interesado y es cuando estarás orgulloso de tu trabajo. Tienes mi apoyo. Saludos Paulino (Calubert).
(no subject) (by José GILLES)
OK
Thanks for your support ! I know that most Bluepills have 128 KB of flash and that's what is declared in ldmicro ! Best regards José
(no subject) (by Mark)
Good morning everyone
I would like to point out that the microcontrollers supported so far are "toys" compared to a 32-bit Arm with resources and possibilities elevated to n compared to a Pic and also to an Atmega, which I also use. The introduction of this, and I hope other families of microcontrollers is an obligation now also because the eight bits are destined to disappear as reminiscence of the past and the cost in proportion is extremely small. Surely also the complexity of the programs that will become possible to build will be at the n, and LdMicro will have to develop tools for understanding and help in drawing up the logic of the program that will allow the vision of the various parts easily ..... see sub-programs, visual division for logical parts ..... drivers, functions ..... (I would leave the simulation integrated, but perhaps with the connection to external simulators directly from inside the ide). A question I wanted to ask is about the generation of the code, and the possible compatibility with standards .... for example, Misra Congratulations on your effort and great skill, in my opinion.
(no subject) (by MGP)
Mark, all very nice but the problem is that there are not enough developers.
(no subject) (by Mark)
Yes, I have participated for a long time in free developments etc ...... but now after 41 years of work it's time for me to think about my grandchildren.
Therefore, let the young people go, the world will have to continue thanks to them. However, I will follow to satisfy the curiosity that never goes away, and if I will be allowed to give small things, perhaps useful.
program for compile (by Nadi Radiana)
greetings all ..... the question that I ask a lot is ... with what program you compile c langue files to hex ... by keil?, by coocox?,or by eclip, and how to do it
because for pic16fxxx ic it's easy .... hex file already exists when compiling
(no subject) (by José)
1) Install EmIde 2.20 from their download link.
2) Copy Bluepill basic libraries from ldmicro\LIBRARIES_FOR\ARM\STM32F1 and create a project. 3) Compile your project. 4) Download hex or elf file created in bin directory to your bluepill board with your st-link v2 key Here's an example of ready made project to play with leds. José
(no subject) (by Tom J.)
Greetings,
If the Bluepill has an operating frequency of 72mhz is it fast enough to count frequency with LDMicro? What's the shortest cycle time we can do with it?
(no subject) (by Ihor Nehrutsa)
The shortest cycle time depends on the complexity(number of rungs and elements) of LD file.
You can experimentally determine the shortest cycle time. 1) Develope the full LD program. 2) Set the YPlcCycleDuty checkbox in the menu->Settings->MCU Parameters. 3) Decrease the cycle time. 4) Measure(view on an oscilloscope) the frequency of YPlcCycleDuty. 5) Go to #3) if the PLC cycle time is stable like in the picture. https://user-images.githubuser...592-11e7-9608-015f12eeefae.png
EmIde 2.20 not found (by Joan)
Hello, I'm looking for EmIde 2.20 and the author's website is not available, does anyone know where it can be obtained?
Thank you very much and go ahead with the STM32F103, it is a good project.
(no subject) (by Joan)
Perdón, ya lo encontré.
(no subject) (by José)
I don't know why, but EmIde's site is out ot of order. You can download it on my temporary link: http://hpvexin.free.fr/script/temp/EmIDE-V2.20-Setup.exe José
Hello Jose (by Joan)
I downloaded the software, thank you very much.
I have a question: I have a small example and when I run flashMcu.bat it can't find the st-link programmer and the program ends. St-link I don't have it yet and that's why it doesn't end correctly. I have an other question; Does Ldmicro copy the compiled file somewhere on the computer? for example in tmp or something similar? To know something? Thank you.
(no subject) (by José)
If you don't have any st-link programmer, it's normal that flashMcu.bat doesn't end correctly. Which version of ldmicro do you use to build your example ? Generated files are in your ld file directory (C files) and in its ARMGCC subdirectory (Binary files). St-Link is called in flashMcu.bat with a line like this: ST-LINK_CLI.exe -c SWD -P ARMGCC\bin\%~nx2.hex -V "after_programming" -Run It looks for the .hex file generated in ARMGCC\bin
--> José (by Joan)
Hi, thanks for your help.
Sorry, the version I use is yours, ldmicro32.V5.5 and is installed in the emIDE directory. I start by saying that it generates the ARMGCC directory but there are no files. When I give the option to Generate C solution, in the log, many errors appear. Any chance of an email or link to send you information. Thank you
(no subject) (by José)
OK
To have a working project, you must have ldmicro in a directory and the LIBRARIES_FOR subdirectory with its content in it: ldmicro.exe dir --->LIBRARIES_FOR dir ------->ARM dir ----------->STM32F1 dir Then you create your ladder, you compile it for ARM-Gcc (generates .h and . c files in .ld folder), you build the project (generates ARMGCC subdir with required libraries in lib, temporary files in obj and .hex file in bin) You shoud have no error message if everything is fine. Finally you can upload bin/.hex file to the target using FlashMcu (must be customized) If any pb, capture and post full output screens. José
Thanks José for your help (by Joan)
I tell you, the first part works, copy in the .h .c folder.
The problem is when I give "build the project", just copy the libraries and the rest in the log says: "it is not recognized as an internal or external command", I send you an image and sorry for the language, it is in Spanish. Thank you very much for your collaboration.
In gratitude to Mr. José (by Joan)
EUREKA !!!
I already have it, the directory was missing the "x" of "(x86)". Thank you very much and God bless you. Best Regards, Joan
STM32F103 - Bluepill tarjet. (by Joan)
Everything works fine, even in Proteus until I get the ST-Link programmer.
I have a question. I would like to be able to program the PC13 pin, where can I parameterize it? Although it is only a particular option. Thank you.
(no subject) (by José)
That's fine if it works for you ! Sorry, but Port C hasn't been declared in Bluepill config for ldmicro because it only consists in PC13 pin, which is bound to a led... You can't add it without modifying and rebuilding ldmicro source code.
Monsieur José (by Joan)
José is fine. You are right in port C.
I want LDmicro to continue improving for many years. Greetings and it's all for now. Thank you.
Post a reply to this comment:
|
|
|