While using STM32 CubeMX (version 5.2.1) and selecting the i2c in SMBus-two-wire-Interface it shows as follows:-
Warnings: STM32 CubeMX does not support the configuration of this mode of this IP.However,this IP can be configured manually.
Anyone please tell me the reason for this warning and also a solution for this
Related
I configured with STM32CubeMX the UART interface for my Nucleo F446RE, it's using HAL Driver, and i want to connect it to a USB to UART Bridge so it can communicate with my GUI.
The other Project has all the programm code and it don't uses HAL Drivers.
Is there any way to merge these two Projects in System Workbench for STM32 together?
I have designed a circuit in which I am using STM32L452RETx micro-Controller on PCB. This is basically a current sensor. I am using JTAG-20 connector for debugging. I am using Atollic TrueStudio IDE.
The issue is when I debugg program in TrueStudio by selecting JTAG option in debug configuration then it gives error saying failed to initialize the ST-Link and target not found but when I Select SWD then there is no error and it programs successfully. where as in STM32CubeMx I have set debug to JTAG 5 pin configuration as i am using JTAG 20 in hardware. (serial peripheral-> Sys -> Debug-> Jtag 5 pin). program is debugging without errors but no output at the serial terminal. serial terminal gives no hand shake error.
Can anybody tell is this right way of debugging ( SWD in TrueStudion and JTAG in STM32CubeMx) or I am making a mistake.
Regards,
The paradox is not as big as it seems:
As you can verify in the
Datasheet for STM32L452xx, DS11912 Rev.5, pages 74/75, the alternate functions of the GPIO used for JTAG and SWD are the same (always AF0, "SYS_AF").
Therefore, SWD connetion works after you configured your STM32CubeMX to JTAG (If you had configured your Cube project to SWD, JTAG wouldn't have worked because the JTDI pin (PA15) wouldn't have been connected to AF0.).
This solves the problem why SWD worked unexpectedly.
The problem why JTAG doesn't work remains.
You mentioned that you're using a JTAG-20 connector, but not which ST-Link version exactly you are using. If, for instance, you are using the ST-Link part that is embedded to a nucleo board (or discovery, or similar product of other vendors), the ST-Link pinout is limited to lines needed for SWD and SWO (together: SWV).
This is not due to limitations of TrueStudio, which does support JTAG in principle, but because one of the 5 lines may be unconnected.
Please inspect which exact ST-Link version you are using (easiest thing to check is what the ST-Link Utility program tells you), re-check your schematics and wiring from the target µC to your debug adapter.
If you don't find an obvious reason (and fix your problem this way), your problem may be an electronic one. Then it is off-topic here and (after narrowing it further) you should describe the remaining problem in Electrical Engineering Stack Exchange.
If you have an oscilloscope, it may be worth to check the signals, especially on those pins that are only on JTAG but not SWD (JTDI, JTDO, NJTRST).
I'm creating a blank project for a STM32F103 microcontroller using STM32CubeMX. Using HAL drivers (the default), I got a blinky example working pretty quickly, but I'd like to try out LL (low level) drivers instead of HAL.
When I go to Project > Settings > Advanced Settings in CubeMX, I see the peripherals listed, and there is a pulldown next to each one which only has one option, HAL. According to the docs this is where I could select LL or HAL for each peripheral.
How do I enable LL drivers in STM32CubeMX?
Details: I did a clean install of STM32CubeMX (4.23.0) on Ubuntu (16.04) and created a new project for STM32F103C8 microcontroller (this is on a "Blue Pill" board). I'm using SW4STM32 IDE, everything more or less worked out of the box except I had to select STLink V2 instead of V2.1 in a config file.
from project manager under advanced setting
from driver selector you can change HAL to LL for all peripherals
Currently (STM32CubeMX v4.23.0) the LL drivers are only generated for L1, L4, F2, F4, F7 series. See the chapter 6.2 STM32Cube code generation using Low Layer drivers
For STM32L1, STM32L4, STM32L4+, STM32F2, STM32F4 and STM32F7 Series,
STM32CubeMX allows generating peripheral initialization code based either on the
peripheral HAL driver or on the peripheral Low Layer (LL) driver.
http://www.st.com/content/ccc/resource/technical/document/user_manual/10/c5/1a/43/3a/70/43/7d/DM00104712.pdf/files/DM00104712.pdf/jcr:content/translations/en.DM00104712.pdf
[guys i have installed the VCP driver and have loaded the code of USB_CDC in my stm32f429. but the VCP port is not visible in device manager. instead "unknown usb device,(device descriptor request failed)" is shown in device manager, as shown in figure. whom link is given below. kindly help me to solve this issue.
http://i.stack.imgur.com/qRzed.png ]1
Are you sure that you installed the right version of the driver (32 vs 64 bit)?
If you are, then try to increase the heap size in your project (it is located in the startup_stm32f429xx.s file).
I want to control a Arduino Uno with Matlab. But when trying to activate the Arduino with in the Matlab Console ( a=arduino('Com7','uno')) I first get a message:
Updating server code on Arduino Uno (COM7). Please wait.
and then get the error message:
Cannot program Arduino board Uno (COM7). Please make sure the board is supported and the port and board type are correct.
Does anyone had the same problem and solved it? Or does anyone has an idea what the exact problem is?
Matlab Version: 2014b (64bit) with the Arduino Support Package installed over the supportPackageInstaller
Arduino Software Version: 1.6.5 (The Arduino Support Package from Matlab comes with an older Arduino Software 1.5.6 - and tried also the 1.0.5 version but error still occures)
Windows 7 prof.
I tried this
and this,
but there was no solution. I searched the web for the last 6 hours - with no pay off...so now I turn to you guys.
I hope you can help. Would be very grateful!
Thanks a lot
Marc
Two possible solutions to the problem:
1.Run MATLAB as an admin in windows
2.Remove winavr if installed in the computer(alternatively you may remove the winavr related directory paths from PATH environment variable)
I had the same problem with a Arduino Mega2560 clone and I solved the problem running Matlab as Administrator. Installing the Matlab legacy package for arduino also worked.