CMSIS | Cortex Microcontroller Software Interface Standard | Wifi library

by ARM-software C Version: v4.5.0 License: No License

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

kandi X-RAY | CMSIS Summary

CMSIS is a C library typically used in Networking, Wifi applications. CMSIS has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

This is not the current version of CMSIS and just provided to allow access to the legacy CMSIS Version 4. Raised any issues on

Support

Quality

Security

License

Reuse

Support

CMSIS has a low active ecosystem.

It has 410 star(s) with 397 fork(s). There are 58 watchers for this library.

It had no major release in the last 12 months.

CMSIS has no issues reported. There are 8 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of CMSIS is v4.5.0

Quality

CMSIS has no bugs reported.

Security

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

License

CMSIS 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

CMSIS releases are available to install and integrate.

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 CMSIS

Get all kandi verified functions for this library.

CMSIS Key Features

No Key Features are available at this moment for CMSIS.

CMSIS Examples and Code Snippets

No Code Snippets are available at this moment for CMSIS.

Community Discussions

Trending Discussions on CMSIS

in CMSIS, why are bitfield positions 'unsigned int' but the mask base 'unsigned long int'?

Understanding Linker output (Elf2Bin)

Controlling STM32F3 GPIOs without the Cube MX libraries

Strange Error Message when Using CMSIS 5.7 with STM CubeIDE during Code Generation

Can some constants be stored in .isr_table section? STM32F1 microcontroller

Source and Include for MakeFile in C

elegant (and fast!) way to rearrange columns and rows in an ADC buffer

Setting GPIOC->ODR[13] = 1 is not tuning up the user LED, rather it is turned up by leaving it to default (i.e. 0). [STM32F103C8T6 (blue pill)]

Ada on the microbit: scrolling text example not working, no libusb library found

STM32F401RE PWM Mode doesn't work in Protues

QUESTION

in CMSIS, why are bitfield positions 'unsigned int' but the mask base 'unsigned long int'?

Asked 2021-Jun-10 at 17:06

Here is an example from a ST CMSIS header:

...

ANSWER

Answered 2021-Jun-10 at 09:04

There's no apparent reason why. I very much doubt these libs are meant to be shared with 8- or 16 bitters, which would be the only sensible explanation.

A Cortex M will be 32 bit with 32 bit int and 32 bit long. And most importantly 32 bit hardware peripheral registers. So even if long was 64 bit it would be senseless to shift a mask outside the register bounds.

The U suffix is enough to prevent undefined behavior left shifts on a signed operand. Other sloppy libs use the bugged 1 << n style, so maybe 1UL was a quick fix to correct that bug - where 1U would have worked just as fine.

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

QUESTION

Understanding Linker output (Elf2Bin)

Asked 2021-Apr-27 at 23:13

I'm doing some development using Mbed Studio and after linking I see this sort of output:

...

ANSWER

Answered 2021-Apr-27 at 23:13

Could it be the change in size from the last link?

Yes.

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

QUESTION

Controlling STM32F3 GPIOs without the Cube MX libraries

Asked 2021-Apr-12 at 13:15

I am adapting this bootloader for STM32F373CC to my device. To indicate that the device is powered but in bootloader mode, I'd like to turn on some of the status LEDs. However, this bootloader doesn't use the STM Cube MX libraries, so I have to code it low-level. The header file stm32f373xc.h is included, so I can use expressions like GPIOB_BASE.

I tried the following first thing in main(), but unfortunately it doesn't work:

...

ANSWER

Answered 2021-Apr-12 at 13:15

I hope that you know that open-drain outputs require pull-up (internal or external)

Use CMSIS definitions, not magic numbers and operations.

requires the entire CMSIS

And what is the problem? CMSIS does not add any overhead to your code, only handy definitions and inline functions, which do not change the size of the code if not used.

Also, HAL has very handy macros useful even if you do not use HAL library itself (it also will not increase the code size even by a single byte)

I will not check your magic offsets and numbers.

First error: after enabling the peripheral clock you need to wait. It is described in the Reference Manual. You do not wait and your first MODER operation has no effect. HAL macros read back the register to make sure that the operation has completed.

Example from STM32L4:

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

QUESTION

Strange Error Message when Using CMSIS 5.7 with STM CubeIDE during Code Generation

Asked 2021-Mar-21 at 21:30

I get a strange Error Message during the Code-Generation Process in STM CubeIDE for a STM32F4 target:

The Details: I am using STM CubeIDE for an embedded Project with an STM32F405 Microcontroller and I have added the CMSIS Package 5.7.0 to the project, because i need some of the DSP functions. I have allready done this before and never experienced such an error message.

The message pops up during the Code-Generation process, after changing something in the Hardware-Setup with the (built in) CubeMX. It occurs two times during the Code Generation process. I can click on "OK" and it does NOT interrupt the Code Generation process, which seems to finish successfully. I can also compile the project without errors and it seems to work ok.

The Question: Even though it seems to work properly, I'd like to know: what is this, where does it come from, and what can I do to solve this? I'm affraid that might lead to some unpleasant sleeping bugs or other nasty stuff ...

Has anyone experienced anything simlilar and has an explanation or even a solution for this?

Hint: I have recently update to CubeIDE 1.6.0 - maybe this is a Bug in CubeIDE and not in CMSIS?

What I've done: I tried to google that, with the keywords: "SliDtzliTZ&" and the "LogicalParser:syntax error detected in expression for ARM.CMSIS.5.7.0" but did not get any usefull results. Next step was to post the question here ...

Thank you in advance, Chris

...

ANSWER

Answered 2021-Mar-21 at 21:30

This problem happens with release version 5.7.0. Using any older version available in the official repository solves the problem.

I'm using 5.6.0 now and all is fine.

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

QUESTION

Can some constants be stored in .isr_table section? STM32F1 microcontroller

Asked 2021-Feb-11 at 23:25

Background

I have some microcontroller experience (Atmel AVR, PIC18, PIC32), but I'm pretty new in STM32.

I need to maintain/refresh some old project written by another developer who for some reasons can't explain this code. Basically whole project needs to be moved from CooCox to STM32Cube IDE and needs serious refactoring.

I understand practically everything in that project except one thing.

Problem

I have found, that there are some constants in the .isr_vector section.

software version
probably build/release date (2020-05-26)
serial number (which is overwritten in the .hex file later, before device programming)

Code and details

...

ANSWER

Answered 2021-Feb-11 at 23:25

This is not at all normal or a good idea.

As you can see though, it works. The main reason it is not a good idea is because it is difficult to maintain, as you are finding out.

The correct way to do it is to put your header in a custom named section and edit the linker script to put this after .isr_vector and before .text or .init etc.

I suspect the person who set this up either didn't want to do the work or didn't know how, or perhaps the IDE they were using was too simplistic to allow custom linker scripts.

If you want to carry on hi-jacking the .isr_vector section for your image header, there are three ways you can get the real vector to still be where it needs to be:

Edit your linker script to specify that .isr_vector from a file called startup* goes before the same section from other files (but if you are editing the linker script anyway you may as well pick your own section name).
Edit the project settings so that the startup assembler unit appears earlier on the linker command line than the file with the header (GNU ld preserves the order of input sections in the output, I don't know about others)
Just cross your fingers and then check the build output to see if it worked. There is a 50/50 chance the sections are in the right order with no changes.

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

QUESTION

Source and Include for MakeFile in C

Asked 2021-Feb-06 at 15:07

I am taking a Coursera course and I am totally stuck in one of the project. Project demands us to create a makefile but I could not.

Here is my files and folders:

...

ANSWER

Answered 2021-Feb-06 at 14:56

It's important to understand that make and the compiler are two completely different programs, that do different things and work different ways. Make can run a compiler, but it can also do all sorts of other things: it could build documentation, or an entire website, or copy files, etc. Basically make is a general-purpose tool that can investigate when files are out of date and run any command you give it to make that file "up to date", whatever that may mean.

So, when you create a variable like INCLUDES = -I... that is setting a make variable to a flag that can tell the compiler where your header files are.

That means nothing to make.

Make sees this rule:

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

QUESTION

elegant (and fast!) way to rearrange columns and rows in an ADC buffer

Asked 2021-Jan-31 at 01:21

Abstract: I am looking for an elegant and fast way to "rearrange" the values in my ADC Buffer for further processing.

Introduction: on an ARM Cortex M4 Processor I am using 3 ADCs to sample analog values, with DMA and "Double Buffer Technique". When I get a "half buffer complete Interrupt" the data in the 1D array are arranged like this:

Ch1S1, Ch2S1, Ch3S1, Ch1S2, Ch2S2, Ch3S2, Ch1S3 ..... Ch1Sn-1, Ch2Sn-1, Ch3Sn-1, Ch1Sn, Ch2Sn, Ch3Sn Where Sn stands for Sample# and CHn for Channel Number. As I do 2x Oversampling n equals 16, the channel count is 9 in reality, in the example above it is 3

Or written in an 2D-form

...

ANSWER

Answered 2021-Jan-31 at 01:21

ARM is a risk device, so 27 cycles is roughly equal to 27 instructions, IIRC. You may find that you're going to need a higher clock rate to meet your timing requirements. What OS are you running? Do you have access to the cache controller? You may need to lock data buffers into the cache to get high enough performance. Also, keep your sums and raw data physically close in memory as your system will allow.

I am not convinced your perf issue is entirely the consequence of how you are stepping through your data array, but here's a more streamlined approach than what you are using:

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

QUESTION

Setting GPIOC->ODR[13] = 1 is not tuning up the user LED, rather it is turned up by leaving it to default (i.e. 0). [STM32F103C8T6 (blue pill)]

Asked 2021-Jan-30 at 09:11

I have recently started learning bare metal embedded development using CMSIS Core framework. I do not understand why the user LED is not turning on by setting the ODR[13] to 1 but rather it is turned on by leaving it to default i.e. 0.

Here is the code I have written.

...

ANSWER

Answered 2020-Dec-30 at 09:39

Disclaimer: I have a software background, and I am using the STM32F103C8T6 blue pill as a hobbyist.

This being said, according to stm32-base.org, it seems that the user LED on PC13 is wired in sink mode. This would explain why setting ODR[13]to 0 is powering the LED on: this does allow the current to flow through the load - see the schematic on the stm32-base.org page:

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

QUESTION

Ada on the microbit: scrolling text example not working, no libusb library found

Asked 2021-Jan-28 at 23:39

I followed the adacore tutorial on displaying scrolling text (https://blog.adacore.com/ada-for-microbit-part-1-getting-started) but can't get it working on my microbit.

Maybe my microbit is a more recent version that is not yet supported? The reason I suspect this is that my board id (9904) was not supported the first time I tried to flash to the board. I used the fix described here: Unable to get the Ada scrolling text demo working on the microbit on GNAT 2019 community edition and added the following line in board_ids.py:

...

ANSWER

Answered 2021-Jan-23 at 14:12

libusb is missing or not found on your computer. It is used to communicate with the Microbit board to upload/debug.

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

QUESTION

STM32F401RE PWM Mode doesn't work in Protues

Asked 2021-Jan-12 at 12:55

I'm trying to generate PWM wave but it seems that proteus has a problem with it. I've tried to do so using CMSIS and CubeMX and neither of them works.

tested timers: TIM 1, 2, 4, 5 with all their channels

Timer configuration in CubeMX Proteus Result

Edited: CubeMX doesn't generate HAL_TIM_PWM_Start as part of the generated codes for TIM's. adding HAL_TIM_PWM_Start to the code and changing the value of Pulse to a non-zero amount, fixed my problem.

...

ANSWER

Answered 2021-Jan-12 at 06:50

You should set Pulse value greater than zero. It is the PWM's duty value.

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

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

Vulnerabilities

No vulnerabilities reported

Install CMSIS

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: