Solved

I'm trying to make a lighting control demo using Bluetooth Mesh.I have two STEVAL-IDB008V2 evaluation boards and I tried to use Demo firmware included in Mesh SDK 1.07.The firmware I used is the file STSW-BNRG-Mesh 1.07.000\Firmware\Projects\BlueNRG-2\Applications\Lighting_Demo\Binary\BlueNRG2_Lighting_Demo.binI provisioned two nodes using my iPhone with BlueNRG_Mesh App in App Store and set up publish address properly. Then I can control the other node's blue LED by pushing PUSH1 switch, and of course from my iPhone too.However, after many control attempts (maybe more than 100 times), the control will stop working suddenly. In the situation, I can control neither from iPhone nor push switch, and I can't do anything from iPhone BlueNRG_Mesh App (e.g. getting library version).It seems the BLE Mesh communication stoped suddenly.I tried many times and I always get this situation.Does anyone have the same situation?

First time using a nucleo board and I am getting started with the stm32cubeide. I have selected the stm32wb55 nucleo board during project creation and used all the defaults for the cubemx autogeneration code which initializes the buttons and leds. I am able to build the project, but when I run the code the mcu enters the hard fault handler after entering the SystemInit function called in the startup assembly code. The below picture shows the disassembly of the SystemInit function. While stepping through the disassembly, I found that I enter the hard fault handler immediately after executing the "add r7, sp, #0" instruction. I've looked at other posts and some of the recommendations were to make sure that you compile with -mthumb option and indeed I am as this is one of the compile options specified for the elf file in the makefile. I'm not sure what could be wrong especially since this is all auto-generated and I have not edited a single line of code. All suggestions are appreciated, t

I've tried to uninstal it from Windows7 standard "programs and components". It's said that the "Program has already been uninstalled, remove from the list". But nothing actually has changed. Now I can't reinstall the IDE cause the installer argues that it is already installed.What a ....!

RM0038 Reference manualSTM32L100xx, STM32L151xx, STM32L152xx and STM32L162xx advanced ARM®-based 32-bit MCUsFigure 8. Power supply overview(LQFTP100)has the following note:VDDA and VSSA must be connected to VDD and VSS, respectively.If I am using separate supply for VDDA should I still connect them?Table 58. ADC pinshas the following:2.4 V ≤ VDDA ≤ VDD (3.6 V) for full speedIt means VDDA can be less than VDD.Manual is a bit confusing. Please help! Which one is a correct statement:VDDA doesn't need to be connected to VDD and can be different from itVDDA must be connected to VDD

I am using a STM32F746zg uc connected to a W25Q80 Flash memory. In my initialization I erase a page then memory map the flash and then I read a pointer to that address. I expect to read 0xFF as the flash has just been erased, however I read 0x88. I'm not sure what is causing this behavior. Have I improperly wired the flash or is this an issue with my code (see snippets below)?More Info: I'm using Cube IDE and created the project using Cube MX. I am able to properly read the manufacturer and device ID so I know that atleast vcc, gnd, cs, clk, io0 are wired properly.I followed the cubef7 example for memory mapped qspi as closely as possibleint EraseSector(QSPI_HandleTypeDef* hqspi, QSPI_CommandTypeDef* sCommand, QSPI_AutoPollingTypeDef* sConfig, uint32_t addr) { sCommand->Instruction = SECTOR_ERASE_CMD; sCommand->AddressMode = QSPI_ADDRESS_1_LINE; sCommand->Address = addr; sCommand->DataMode = QSPI_DATA_NONE; sCommand->DummyCycles = 0;   if (HAL_QSPI_Command(hqs

Excuse me.​Can I change COM Port of name in keil C ?if there is no way , how to change it name ?

..

Hello all , I would like to use BlueNRG-2 in my project to communicate in BLE with mobile phone . My application is build with Atollic TrueStudio on STM32L0. I'am using BlueNRG-2 on STEVAL-IDB008V2 to test demo applications .I downloaded BlueNRG-1.2 DK software package and BlueNRG GUI V3.1.0. So far I understand that I need to flash DTM binary file: DTM UART.hex with BleuNRG-2 navigator to configure BleuNRG-2 as a network coprocessorI connected my STM32 uC UART interface with UART_RX (IO11) and UART_TX (IO8) of the BlueNRG 2 on the STEVAL-IDB008V2. . My questions are : 1- Is there any HW configuration to do on STEVAL-IDB008V2 to use UART interface.2- which software library i need to implement in my uC or BlueNRG 2 to communicate with my mobile phone ?3- In which case i need the DTM Updater ? 4- how can i test DTM firmware ?Thank you .

Hi Everyone, I need the installer for STM32CubeMX 4.23. It is not on the download page anymore. How can I obtain the installer?Thanks,

Hi,I have custom board for stmf401 and I try to program it in DFU mode. I set the boot0 to 1 and reset the chip but it is not recognized as DFU device. (not listed in the DfuSe).Do I miss any procedure or settings?(I have connected the PA11/PA12 pins to the corresponding pins in USB).Thanks in advance.Duncan

I am using STM32Cube FW_WB V1.1.1 and built a new project.I have programmed stm32wb5x_BLE_Stack_fw.bin into the memory space for CPU2 (0x80CB000).I have added the following interrupt handlers:void IPCC_C1_TX_IRQHandler(void) { HW_IPCC_Tx_Handler(); return; } void IPCC_C1_RX_IRQHandler(void) { HW_IPCC_Rx_Handler(); return; }I have configured STM32_WPAN as follows:My small application runs fine but I get no indication that the BLE is running at all. I am using ST BLE Sensor to scan but do not see my device.Any pointers on where to look or what to check would be greatly appreciated.-Louis

Hello,I am attempting to use the built-in bootloader to flash code to the STM32H743 Nucleo-144 using the USART. I have tried two methods: following the flow chart in AN2606 Figure 48, and jumping directly to the bootloader, but so far neither method seems to work.For the first method, I just call HAL_RCC_DeInit(); soon after start to get the clock set up, and then sit in a while loop, but the flash loader never recognizes the board.For the second method, I am following this tutorial:https://stm32f4-discovery.net/2017/04/tutorial-jump-system-memory-software-stm32/I have tried a jump to memory address 0x1FFF000 and 0x1FF1E7FE, which are the two addresses I can find called out in AN2606. This method has the same result: the flash loader demonstrator never recognizes the board.I have the UART cable hooked up to USART 3 on connector CN10 pins 32 (PB10) and 34 (PB11).Am I doing something wrong here? Does anyone have a good example showing how to use the built-in bootloader for the STM32H7? I

When querying STM32H7 system bootloader with GET (0x00) command, it responds with:31-00-01-02-11-21-31-44-63-73-82-92-FF-79in e.g. STM32F4 series the response was:31-00-01-02-11-21-31-44-63-73-82-92-79The AN3155 document does not mention the extra byte or H7 protocol. I am using Rev 7 of AN3155.What is the FF before the ACK (0x79)? Where can I get the recent protocol document for H7 series?

..

Hello,I'm looking to use the STM32F429 to output data to an SVGA display. The supported video formats for the display are shown in the image below. The display is actually a monochrome variant, so color is not relevant as the RGB lines are tied together.The STM32F429 seems to support a number of RGB protocols, including RGB888. This seems to be the most likely correct protocol. to use with the fourth entry in the table above. Out of curiosity however, does anyone see a way that any of the other first three protocols shown in that table could be used with the output protocols supported on the STM32?

I'm developing an STM32F429-based high-speed USB audio device that uses a Microchip USB3320 external PHY and would benefit from a DFU mode. Is there an example available anywhere for such a configuration?The default bootloader present in system memory doesn't seem to support the external PHY, so a bootloader that does this would reside in flash memory, similar like this project here:https://github.com/akospasztor/stm32-bootloader

Hi there,​I got some troubles getting the USB Host system working on the STM32H746ZI.​Worth mentioning is that this is no dev board here, just a plain H7 mcu on a DIY bread board. It is properly supplied with filtered 3.3 and 1.8V. Got UART, I2C, LCD peripherals working fine already. Only this USB host thing wont work at all.​My USB setup:​Pin75 D-Pin76 D+​VBus pins are not used. USB devices are powered directly from linear 5V supply.​The code and project files are created with STcubeMX. FatFs and USB Host with MSC included.​What happens when I stick in an USB mem stick:​D+ goes high (up to about 0.6V) but no communication, no enumeration visible on the scope... debugging the USB_process loop there is never any change from IDLE state.​any idea what I could check?

Hi, does somebody knows, is STM32WB55 support LE Codded or LE 1M or LE 2M?Does this MCU supports Long range connectivity?--best regards,Sergii

Hello,i used the stm32ai software to quantize my MNIST model. I can load the quantized model on my STM32H743-Nucleo Board and with the Validation Software I can validate my quantized model on target.But I would like to create my own Application, so I used the Application Template.I can already run my "normal" model with floating point input-vecors.But if I want to feed my quantized net with fixed point input vector, I only get the same probabilityon every number (see picture). I think the problem is my input data type. The Application Template expects ai_i8. But this data type is to small for grey-scaled Mnist Digits (0-255). So I changed it to ai_u8 and got the output data shown in the picture. But if I put the exactly same input Data as .csv file in the Validation software, i get the right classified number. Does anyone knows the answer to my question?

..

I need a unique ID and expected to use the 96 bit one from the chip. Then I read that STM32F070x6/B do not have it. Very disappointing, but I looked at the F0 location 0x1ffff7ac and sure enough there is something that looks exactly like a described ID with the proper X and Y coordinates, etc. The chips I tested are all STM32F070CBT6. Very confusing. Is it possible that some do have it and others don't?

I would like to understand what the Eclipse IDE is doing to start the debugger, so that I can move away from using it. I much prefer CMake and other tools. I'd be grateful for any assistance. The wiki section for this is TBD.I'm not too familiar with OpenOCD, but have run the command: $OECORE_NATIVE_SYSROOT/usr/bin/openocd -s $OECORE_NATIVE_SYSROOT/usr/share/scripts -f board/stm32mp15x_dk2.cfgThis seems to work so, moving on to GDB: $OECORE_NATIVE_SYSROOT/usr/bin/arm-openstlinux_weston-linux-gnueabi/arm-openstlinux_weston-linux-gnueabi-gdb firmware.elfAnd this is where I come unstuck. I've used GDB a bit, but don't know the magic incantations to install an image into the M4 on this platform.(gdb) target remote localhost:3333Remote debugging using localhost:33330x00000000 in g_pfnVectors ()I get a "target not yet examined" error which I don't understand. The vector table is all zeroes, so nothing has yet been placed in the RAM yet. (gdb) loadLoading section .isr_vector, size 0x298

Hi,As i was testing the limit of how many virtual uarts i can create, i found that the limit is actually 4:Using debug tracing i can see that the channels get created inside the code (here i am creating 5 virtual uart) but only 4 ttyRPMSG are created.I reduced the total buffer used by each channel to 256 instead of 512:// File: rpmsg_virtio.h   /* Configurable parameters */ #ifndef RPMSG_BUFFER_SIZE #define RPMSG_BUFFER_SIZE (256) #endifSo in theory, i should be able to create 8 channels but the max is 4 apparently.Can someone please confirm how they made it?Thanks

I recently came across defects in STM32G0 & STM32G4 reference material. I tried reporting this through the support channel only to receive kneejerk deflections. Since i have already worked around the issues myself I'm not seeking any help or support but rather wanted to help improve the overall platform experience for others. The responses I got from are disappointing and reflects poorly on the company culture and the support team's attitude toward quality control.

The "MX_RTC_Init" function called by default from the main.c resets the RTC's date and time to zero values (by default) or to some other predefined constant values.The standard practice is to set a bit in one of the backup registers after setting the date and time and to check the existence of the bit after enabling the backup domain and RTC - if the bit is set then don't touch the date and time.There are no user code sections in MX_RTC_Init to try and change its logic, so what is the recommended way of implementing "don't change the date and time if it is already set" in a Cube generated LL project with RTC enabled?Thank you.