Solved

I have connected the nucleo board to my PC using micro usb cable but when I press degugging button in Keil uVision5 it shows "Internal Command error".How to enable debugging in Nucleo board?

That question started bothering me when I was struggling with TLE493D that started interrupting using the i2c clock line.It looked like the i2c in the F429 was gone bananas and keeping the i2c stuck (busy).I was thinking of feeding the i2c the clock pulses and maybe end condition by writing to the GPIO data registers (bit banging), but would that be seen by the i2c? It's not clear from the pictures in the reference manual.It looks (in the pictures) like at least a pin acts as a pin for alternate function, GPIO input and analog input at the same time. And I can read back (GPIO input) the GPIO output pin state.Maybe I can even use ADC to measure the pin's GPIO output voltage? Or get a GPIO input while also measuring the input signal voltage with ADC?I guess, though, that only one "party" can drive the pin output at a time?Oh, and I'm talking about these pictures: https://bluetechs.files.wordpress.com/2013/12/115.png

I'm developing a custom board with STM32WB55CGU6 with firmware based on Cable Replacement example. Trying changing the advertised name, I can not put more than 5 chars, the BLE stops working. I know the standard advertising supports until 7 chars. What I have to configure to have a bigger advertised name ?

Hello,I would like to signal a possible error on the reference manual of the STM32L496 (RM0351 Rev 6)At pag 348, section 11.4.5, Table 45 the first line (source port 8bit, destination port 8bit) indicates that the Number of data items to transfer is 8, however I think it should be 4.Moreover: I don't clearly understand the description of the NDT register. It is described as "the number of data items to transfer", however it looks more like as "the number of DMA transfer". In fact, regardless the sizes of data (MSIZE, PSIZE) the NDT is decremented after every DMA transfer, being it 32,16 or 8 bit. Then for me the fact that it refers to the number of data items is misleading.

I have a weird problem. I have the Nucleo board with a TLE493 magnetometer connected. When I connect the USB cable (power the system), file manager opens. If I then close the window, upload my SW using Atollic, my magnetometer code works fine, but if I don't use the debugger, initialization of TLE fails - the I2C HW is already "busy". (TLE starts interrupting via the I2C clock line).What's different in the boots? The boot0-pin is low by default, and it hasn't been touched.What code initializes the USB and what else does it do? I'm using I2C2 with PF1 as the clock line.

Following up on my last question about the LTDC interface (That's now working) I'm working through the app note 4861.Where for the LTDC interface there is a nice walkthrough on how to find the timing values there is nothing like that for the SDRAM selection. bummer.I have made a board with AS4C4M16SA for the SDRAM, datasheet here: https://www.alliancememory.com/wp-content/uploads/pdf/dram/64M-AS4C4M16SA-CI_v3.0_March%202015.pdfThe timing information is on page 20.But the app note states that one can either use the CubeMX interface or use the BSP files.it goes (lightly) over the BSP integration but don't mention the CubeMX at all.More specifically I am looking for a way to figure out the timing setup from the datasheet:Those are the value for the SDRAM supplied with the STM32F746G-DISCO board.. is there any pointers on how to adjust these values for a new chip?Also - since I'm running the TouchGFX integration I have a file called 'HW_Init.cpp' In the top there is a couple of definitions

Hello ,The Micro Controller Iam Using is STM32h743ZI. an iam using ST link V2 programmer.I have Configured My GPIO pins ,Clock and i have generated the code the code got generated without any errors once the code gets generated i have added the following code for LED Blink.HAL_GPIO_TogglePin(GPIOG, GPIO_PIN_2);  HAL_Delay(500);and i have debugged it iam not getting any errors it is getting debugged perfectly and it shows download and Verified Successfully but My LED is not blinking it is not getting Toggled.i have Attached the code , pin Configuration , Clock Configuration , Setting .kindly Give me a Solution so that it will be very helpfull.Thank you,Muthukumar Ganesan

Hi,I have an application of which uses the STM32F469NI with two MX25L12833F QSPI flash in dual flash mode and are encountering an issue when using HAL_QSPI_AutoPolling().CLK is configured at 1MHz (to allow for logic analyser), both devices share the same CLK and nCS lines, where nCS is provided from BK2_nCS.When performing a sector erase, the instruction is sent to both chips as outlined in AN4760 section 2.2.4, the peripheral is then configured to auto poll for the WEL and WIP bits to be reset. I am seeing that it does not respect both chips. The device on QSPI1 can finish and the autopoll stops yet the device on QSPI2 continues the erase operation. See attached snippet from a logic analyser where device 1 is CH2-5 and device 2 is CH6-9.Is this expected behaviour or is extra configuration required for autopolling when using Dual Flash mode?Thanks,Jack

Hello and thank you for your help ahead of time.I am working on a vehicle detection product using the LIS2MDL and noticed a strange anomaly with the Z-axis when I was testing for stability over temperature. Showm in the attached photo, the Z-axis randomly become very noisy until i moved a piece of ferrous metal near the sensor, at which point it stopped. It was only the z-axis too, all others remained very stable as can be seen in the graph. It should also be noted that this behavior was rare and doesn't happen every time im evaluating the stability. This behavior is very undesirable if it would happen randomly on the final product.Any idea on what could be causing this? Could the Pin 5 Capacitor trace length cause this? Any ideas are greatly appreciated.Thanks again for your help.

My M24LR04E Discovery Board is not showing up when using the CR95HF Development Software's "Auto Detect tool" or the "Vicinity Tags - NDEF Message user interface" tool. In these tools the tag just doesnt show up as seen when you scan for tags. In the "Tag Detection tool" however, the tool is shown (however this isnt very usefull, it only shows that its a ISO15693 tag). The M24LR04E Board itself still has the functionalities to show the voltage of the field or to show the temperature sensor output. The NDEF message however reads:"NOT A NDEF TEXT MESSAGE"How this (probably) happened:I was playing around with the discovery board for my internship, to get to know NFC. I have installed the CR95HF Development Software that goes along with the M24LR04E Discovery Kit.When playing around with the Vicinity Tags - NDEF Message user interface, I could read and write away NDEF messages to the M24LR04E Discovery Board.After that I opened this program: the ISO15693 User Interface M24LR04E. Here I sta

Hello All,I have used STM32F103RBTx Dev board previously on Windows (windows 7 Professional) Platform with Kiel uVision4 IDE and STM32CubeMX 4.24 tool.I had also build an example code which used PWM, GPIO, UART and SPI peripherals and it worked properly.As per requirement now i have to use Ubuntu 14.04 Linux based system with Atollic TrueSTUDIO® for STM32, Version: 9.2.0 and STM32 CubeMX version 5.3.0.I have Installed Atollic IDE and STM32CubeMX and also installed Embedded Software package for STM32F in CubeMx, reference Image attached belowAfter this by refering the video on the link given below i tried to build the blinky example code,https://www.youtube.com/watch?v=6RqUkFIeN6w&t=470sHowever I was able generate the code but when i compile the code i am getting error mention in the attached screen shoot.So is there any Dev board specific package installation to be done so that it finds the HAL Library path which is mentioned in error messageOr, I am missing out on something while

Hi,I have made a PCB with ST25R3911B. Regarding the matching network and the antenna, I have design them starting from the X-NUCLEO NFC05A1 evaluation board (the antenna is the same).The firmware on the microcontroller works, because we have tested it with the X-NUCLEO NFC05A1 mounted over NUCLEO F072RB (the microcontroller is the same STM32F072RB and the pinout is the same).Unfortunately the custom board is not working properly: the IRQ pin is always high (we are using wake up mode for phase/amplitude). In AN4985 there are images of the RF output signal, that are the same that I am obtaining on the X-NUCLEO NFC05A1. Unfortunately on my custom PCB it seems there is not an RF output signal.In the attached images you can see the voltage value at pin 11 of ST25R3911B (RFIO2), I have an RF output on the EV board, but on my custom board the voltage level is Always at 5V. The voltage at power supply pin is correct, as well as the crystal oscillation frequency.There must be an hardw

As per the section 5.2.3 of the STM32H747I-DISCO board user manual, the default configuration of the hardware is to use SMPS mode but the default mode generated by STM32CubeMX when you select STM32H747I-DISCO board is LDO. Because of this mismatch, the board is bricked.ST should have used the same power supply configuration in both the hardware board and default CubeMX configuration.

Hello Community, Is there a fast way to clear the EEPROM of ST25DV. for example, a fast API to clear the whole EEPROM, and how long it will take? I want to have the option to clear the memory when a special command is written through RF Thank you very much for your help

Hi,I'm working with the STM32H750VBTx and I switched to the latest FW version package, STM32Cube FW_H7 V1.3.2.CubeMX generated the stm32f7xx_hal_conf.h file and a line was added to this file:#ifdef HAL_EXTI_MODULE_ENABLED #include "stm32f7xx_hal_exti.h" #endif /* HAL_EXTI_MODULE_ENABLED */The EXTI flags are all enabled in the CubeMX.The stm32f7xx_hal_exti.h file does not exist and so a fatal error is generated: stm32h7xx_hal_exti.h: No such file or directoryIs there a new version of FW H7-package?Do you know this problem?

As described in your help center, I configure my canvasBuffer in my main.cpp. As I have a quite important requirement, I put it in a specific section of my internal RAM memory.However, the designer seems to override this in all my viewBase files with a 3600 buffer size, and not in my reserved section anymore of course, which is a problem. In the designer, when a screen is selected, on the right, there is an option to overwrite the canvasBuffer (quite new option ? I do not really remember it). However, those option are unchecked on all screens, and still defined in the viewBase files.Is there any way to avoid that and keep using my dedicated memory located region for it ?

Is it possible to override a ScrollList so that list scrolling is controlled by a separate widget? This separate widget is on the same screen as the ScrollList, but is outside of the ScrollList. I would still like to be able to use normal press & release on the Items inside the ScrollList.In other words, I do not want to allow the user to scroll the ScrollList by dragging on the ScrollList itself.If that is possible, exactly what would need to be overridden to accomplish that?

Hi,Having tested all the examples from the STM32F7 package for the STM32F769 Discovery kit, I started to write my own project from scratch. For thios, the starting point is the STMCubeMX tool.So far, everything went well till I reached the point of the LCD. I cannot get it working. I compared the generated code with the one of the BSP. It is similar except inthe initialization sequencethe value of some configured timings, that STMCubeMX does not allow to set as in the BSPHas anyone any experience and advices to get a LCD working from a STMCubeMX project ?Thanks in advance.Regards.

I'm using both SPI1 and SPI2 on an STM32G071RBT Nucleo board, using STM32CubeIDE code generation and LL interface. Both SPIs are configured to use DMA for receive and transmit. SPI1 uses channels 2 & 3; SPI2 uses channels 4 & 5. The DMA transmit complete interrupt is enabled on the receive channels. (2 & 4).SPI1 works fine, but not SPI2!?!?! The SPI transaction is successfully started, and the data sent, but I never receive the channel 4 transfer complete interrupt. Any thoughts? Does the DMAMUX need to be configured to receive a channel 4 interrupt? (The interrupt handler is called "DMA1_Ch4_7_DMAMUX1_OVR_IRQHandler".)Thanks for any help.

I have a design where I am using both I2C1 (external ADC) and I2C2 (external EEPROM). I have no problem making I2C2 work perfectly. The MCU both transmits and receives messages with no problem and I can see in on the Oscilloscope. However, when I attempt to use I2C1 in the same way, using the same HAL commands:HAL_I2C_Master_Transmit(&hi2c1, ADCAddrWrite, ADCConfigCond, 0x01, 1000);andHAL_I2C_Master_Receive(&hi2c1, ADCAddrRead, (uint8_t *)aRxBuffer, 0x02, 1000);It does not work. On the oscilloscope I can see the clock signal go low briefly and then go high again every time the MCU attempts to either send or receive a message. I think the MCU is issuing the Start bit but then it times out. When I use the debugger and follow the code through step by step I see that the bus is timing out (or at least I think it is). If I elongate the timeout to 10 seconds I can even count it off and see that the MCU pauses at the command for 10 seconds and then m

I am trying out the sample projectSTM32CubeExpansion_SBSFU_V2.2.0/Projects/NUCLEO-H753ZI/Applications/1_Image.I have completed the following build steps:prebuild.pyBuild SECoreBinBuild SBSFUBuild UserAppThe last step postbuild.py (which is SECBOOT_ECCDSA_WITH_AES128_CBC_SHA256.sh) has an assert:Exception: AES CBC encryption requires the Firmware Image size (22232 bytes) to be a multiple of the AES block size (16 bytes)I don't know how to get around the problem.

Hi all,To be hontest, I am a beginner when it comes to timer and capture hardware. Maybe someone can help me figuring out what the best way is how I can measure the time between two separate impules i get on two separate lines. Accuracy shall be very high.First input: some master clock pulse (1kHz) Second Input: some delayed clock pulse with high level for a few microseconds. I need to measure the time between the first pulse and the second.First thought, use two synced timers, capture two values and calculate the difference between them. Second thought, reset a timer by the 1kHz reference pulse and capture to the timer counter register when the second pulse on a different pin is comming in.Any ideas how to configure the STM32H743 for this?Thanks a lot!

Using STM32Cube, I can build the demo project MOTENV1_IKS01A3_WB55RG fresh from the zipfile fine. However, you cannot open the MOTENV1_IKS01A3_WB55RG.ioc file in it's original location. You get and error that it is the wrong name. So I copy MOTENV1_IKS01A3_WB55RG.ioc from the MOTENV1 directory , into the MOTENV1/STM32CubeIDE/MOTENV1_IKS01A3_WB55RG directory. (where it should be)But if I open it there, make no changes and and regenerate the code, I get numerous errors. The first is: motenv_stm.c:149:3: error: unknown type name 'MOTENV_STM_App_Notification_evt_t'; did you mean 'EDS_STM_App_Notification_evt_t'?Diffing against the previous directory shows numerous changes. Looking at just the .ioc file when opened with CUBE, these lines are different:188,189c188,189< ProjectManager.CustomerFirmwarePackage=..\\..\\..\\..< ProjectManager.DefaultFWLocation=false---> ProjectManager.CustomerFirmwarePackage=> ProjectManager.DefaultFWLocation=true208,209c208,209< ProjectManage

Hi all,(I am using a STM32L031) I'm trying to design a system that receives a UART string and uses this data to drive a WS2812 LED strip at different colors depending on the string. So far, I've done a lot of googling and found that a lot of people are using HAL_TIM_PWM_Start_DMA() to vary duty cycles of PWM for similar purposes. I've done all the peripheral setup required I think and am able to get a PWM signal going (see attached .png) I have a couple of issues though - The PWM never stops even though HAL_TIM_PWM_Start_DMA() requires a length to be passed in. Now, I've checked that the DMA transfer completes, by setting a breakpoint in the IRQ handler like so:void TIMx_DMA_IRQHandler(void) { if (__HAL_DMA_GET_IT_SOURCE(TimHandle.hdma[TIM_DMA_ID_CC3],DMA_IT_TC)){ // if (TimHandle.hdma[TIM_DMA_ID_CC3]->XferCpltCallback != NULL){ //other = other+1; //this following callback does nothing... TimHandle.hdma[TIM_DMA_ID_CC3]->XferCpltCallback(TimHandle.hdma[TIM_DMA_ID_CC3

To port the code from STM32F7 to STM32H7, I have got latest version of CubeMX and H7 firmware package. when I configure one of the GPIO pins on F7, CubeMX generates initialization code automatically. but it does not generate initialization code for GPIO on H7. Why is that CubeMX works for F7 but not for H7. Why can't it generate code for peripherals like GPIO, etc for H7?