stm32f429 | Keil projects and libraries for STM32F4xx devices

by MaJerle C Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(5)Vulnerabilities Install Support

kandi X-RAY | stm32f429 Summary

stm32f429 is a C library typically used in Internet of Things (IoT) applications. stm32f429 has no bugs, it has no vulnerabilities and it has medium support. You can download it from GitHub.

Keil projects and libraries for STM32F4xx devices

Support

Quality

Security

License

Reuse

Support

stm32f429 has a medium active ecosystem.

It has 1817 star(s) with 1251 fork(s). There are 269 watchers for this library.

It had no major release in the last 6 months.

There are 7 open issues and 8 have been closed. On average issues are closed in 116 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of stm32f429 is current.

Quality

stm32f429 has no bugs reported.

Security

stm32f429 has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

stm32f429 does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

stm32f429 releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of stm32f429

Get all kandi verified functions for this library.

stm32f429 Key Features

No Key Features are available at this moment for stm32f429.

stm32f429 Examples and Code Snippets

No Code Snippets are available at this moment for stm32f429.

Community Discussions

Trending Discussions on stm32f429

How can I make the second code works? (C code, sprintf and pointers)

Extending u-boot functionality

Conflicting CPU architectures 1/13 when compiling for cortex M4

stm32f429 buildroot remote-debugging

Gyroscope on STM32F429-DISC1 is behaving strangely

QUESTION

How can I make the second code works? (C code, sprintf and pointers)

Asked 2020-Dec-04 at 08:16

I am using stm32f429 UART to send commands into a module. I prefer the second function code but I don't know how can I make it work. First function code, which works completely.

...

ANSWER

Answered 2020-Dec-04 at 08:16

It works it the first piece code because you are allocating memory for with

Source https://stackoverflow.com/questions/65139811

QUESTION

Extending u-boot functionality

Asked 2019-Nov-04 at 23:28

I need to add some new features to u-boot like pressing specified button to setup my device using blinking LED as a device response. The problem is that I don't where u-boot starts to execute C code. What file should I modify?

I use STM32F429I-Discovery for testing and have already installed everything I need to run kernel using buildroot. One of the LEDs (GPIO_13) is constantly blinking, so, I tried searching for the code that provides such functionality. It looks like led.c and gpio_led.c must do the thing but changing them gives nothing.

Update.

Well, I was trying to dig into triggers but it looks like modifying .dts file doesn't have impact on LED blinking. Commenting code in the corresponding heartbeat-trigger turns off the LED, however, there is no GPIO choice, so, I cannot change the green LED to the red one. After moving "linux,default-trigger" to GPIO14 in the .dts file I recompile u-boot and linux with buildroot but nothing changes. Here are my changes (I took some code from stm32f746-disco.c):

stm32f429-disco.dts

...

ANSWER

Answered 2019-Oct-18 at 14:34

You should add the u-boot functionallity in the board.c file. Which can be found at: u-boot/board/stm/stm32f429-discovery/board.c

You might need to change other settings, which can be done in the header file. This file can be found: u-boot/include/configs/stm32f429-discovery.h

Source https://stackoverflow.com/questions/58442977

QUESTION

Conflicting CPU architectures 1/13 when compiling for cortex M4

Asked 2019-Aug-03 at 13:02

I used to compile my microcontroller code with arm-none-eabi-gcc/arm-none-eabi-g++ and everything worked fine. I use the homebrew Cask gcc-arm-embedded on Mac. Yesterday I updated it and now I get these error messages for every object file at the link stage when I compile for a Cortex M4 architecture (compiles fine with M3):

...

ANSWER

Answered 2017-May-25 at 06:49

A colleague found the issue. For some reasons we needed to change the compiler specs. For this we added this to the link commandline: -specs=…/specs

We generated the specs file with the following command arm-none-eabi-gcc -c foo.c -dumpspecs

The thing is that the new version of the compiler had new specs, so we had to generate them again, which solved the issue.

Source https://stackoverflow.com/questions/44153706

QUESTION

stm32f429 buildroot remote-debugging

Asked 2018-Nov-24 at 07:47

there

I just learned how to use buildroot and followed one of the tutorials to flash the built images of linux kernel, U-Boot, etc. to a beagle bone. It's all good and fine. So I applied buildroot on the stm32f429-disc1 and flashed the images to the board. There is a bug on the busybox and I want to debug it. The question is how would I modify the openocd script below so that I can debug the booting process, presumably with gdb (server) open in another terminal ?

...

ANSWER

Answered 2018-Nov-24 at 07:47

To debug userspace applications, you will not use OpenOCD, but rather pure software debugging, using gdb and gdbserver. You can read https://bootlin.com/doc/training/buildroot/buildroot-slides.pdf starting from slide 275 for more details.

Source https://stackoverflow.com/questions/53091861

QUESTION

Gyroscope on STM32F429-DISC1 is behaving strangely

Asked 2018-Feb-23 at 00:05

I'm quite new in STM32 world, and I have a problem with the on-board L3GD20 gyroscope on teh STM32F429-DISC1 board.

I had troubles in getting it running (the gyroscope was constantly sending the same data, even after reset or power down) and after I finally managed to get it working (by sending instructions a couple of times), I saw strange results (both on x-axis, y and z) (see graph below).

Am I missing something, or should I do something with the raw data, that will smooth it? Is there a possibility, that the IC is defective?

I am using Atollic TrueStudio v9.0 for STM32 with STM32F429-DISC1.

Here is my code:

...

ANSWER

Answered 2018-Feb-22 at 23:55

From the L3GD20 app note:

Note the last part "expressed as a two’s complement number"; you are incorrectly interpreting the data as unsigned. It looks like the value is hovering around zero; or actually it looks like you are holding it rather unsteadily in a position, but certainly not rotating it continuously as a steady rate. The device is a gyroscope not an accelerometer. It measures angular velocity not acceleration (or tilt - i.e. acceleration due to gravity). While stationary you would expect zero on all axes. What your graph shows is probably your hand shaking trying to hold it at 45 degrees.

Source https://stackoverflow.com/questions/48938408

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install stm32f429

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: