Solved

I have set up the device, 5V 3A wall PSU and connected to the USB stlink connection. Connecting to the onboard stlink I can recognize the board serial number but the programmer fails to recognize the device. What am I missing? The device works perfectly in stand alone mode. As it would not identify the device I upgraded the firmware to V2J37M26 to see if that would correct it.   This was the output in the programmer if it helps.   12:26:58 : ST-LINK SN : 0669FF333536414257062332  12:26:58 : ST-LINK FW : V2J37M26  12:26:58 : Board    : --  12:26:58 : Voltage   : 3.27V  12:26:58 : SWD freq  : 4000 KHz  12:26:58 : Connect mode: Normal  12:26:58 : Reset mode : Hardware reset  12:26:58 : Error: Cannot identify the device

I have ST-LINK V2 Programmer and when I connect this with STM32MCU, it shows an error like this I have checked connections, jumper Wire.Changed the port also. But still, it is showing No STM32 Target Found. For checking Whether My Programmer is corrupted or not, I have checked ST-LINK with STM8 by connecting to SWIM pinout and it successfully uploads on to my STM8.So is MY MCU corrupted or damaged, I have an STM32F103C8 Blue chip board.And have configured its Boot Mode as shown in Pic.BOOT 0 : 0Boot 1: opened Please Help, I am stuck on this for 2 days scratched my head but can't find what the is the issue??

I have two projects. One is an example from ST for a driver controlling stepper motors and the other is my own created with CubeMX where i've added the driver src and header files from the example into to the project. The main.c file is the same for both projects.For some reason the SPI1 registers of the second project (my one) aren't updating in the HAL_SPI_Init() function but they are updating for the original example project even though the functions are identical. The GPIO init function works fine and all the base addresses and handlers are the standard ones from the HAL yet when i debug the project line by line and view the SPI1 registers in the SFR window they do not change.Board Init function:uint8_t Powerstep01_Board_SpiInit(void) { HAL_StatusTypeDef status; /* Initialises the SPI --------------------------------------------------*/ SpiHandle.Instance = SPIx; SpiHandle.Init.BaudRatePrescaler = SPI_BAUDRATEPRESCALER_32; SpiHandle.Init.Direction = SPI_DIRECTION_2LINES; S

..

I am using STM32H753ZI Nuccleo board. When I configure it on cube, I am using independent mode (otherwise no ADC works). I was only able to make them work together by stopping the running ADC in the conversion completion interrupt and raise a flag to start the other one. The problem is that I need both of them to run together without enabling and stopping the ADC_DMAs.

Hello, all.So I have this problem with my SensorTile.box. I received it this afternoon, and I connected it to my desktop PC via a USB cable while the PC was starting. It shows up on the device list on the ST BLE Sensor app; the device's red light was also blinking. Sometime after, I got a notification that I can update my SensorTile.box's firmware. So I updated it, and afterwards, the app cannot detect it. Even when the SensorTile.box's blue light was blinking, the situation is still apparent. Now, when connecting my SensorTile to my desktop PC in the same manner repeatedly, there are no blue and red lights blinking or staying on, and therefore non-discoverable. Is there any way, without asking for a replacement, that I can remedy this and make my SensorTile discoverable again? Thank you for your feedback.

..

I am starting a new project on STM32G070KB and I want to use freeRTOS.Problem that I have is that the configMAX_SYSCALL_INTERRUPT_PRIORITY seems to be gone from the port !I use the latest STM32CubeIDE with the 1.4.1 firmware package for STM32G070KBProblem is that because STM32G070 has only 4 priority level (2 bits) all of the interrupt that I set in the STM32Cube environnement needs to be at 3 (lowest priority) if they use freeRTOS functions !! This means I have no way to priorise them !! #FreeRTOS​ #Interrupt​ 

Hi,Whenever i call aci_gatt_clt_disc_all_primary_services() or aci_gatt_clt_exchange_config(),the stack returns BLE_STATUS_INSUFFICIENT_RESOURCES (0x88).What exactly is insufficient? Is it the heap size of the stack is just busy?What adjustment do i need to make to solve this problem?Some backgrounds of my firmware:Heap is set to 0x800Using data length extensionUsing coded PHY (S=8)Using extended advertising and scanning/* This file contains all the information needed to init the BLE stack v3.x. * These constants and variables are used from the BLE stack v3.x * to reserve RAM and FLASH according the application requests. *//* Default number of link */#define MIN_NUM_LINK_CONF (1)/* Set supported max value for ATT_MTU enabled by the application */#if (CONTROLLER_DATA_LENGTH_EXTENSION_ENABLED == 1) && defined(CONFIG_SW_OTA_DATA_LENGTH_EXT)  #define MAX_ATT_MTU_CONF (OTA_ATT_MTU_SIZE_CONF) /* OTA Client & Server supported ATT_MTU */#else /* No data len

I am using NUCLEO-L4R5ZI-P board, I have measured current consumption by using example project (PWR Mode: STOP1) and I got the following readings :Practically STOP1 : 1.19 uA Datasheet STOP1 : 4 uA Why I am not getting same value mentioned in datasheet is there something wrong?

I used example from STM324xG_EVAL\Applications\LwIP\LwIP_UDP_Echo_Server\Src.​I add lwIP into the project using CubeMX. ping test is good. I sent the message using Hercules tool. but Necleo didn't receive massages .​​there are CubeMX setting value.I also change GATEWAY ADDRESS to 192.168.42.1, not working too.​​​/* lwIP.c*/ void MX_LWIP_Init(void) { /* IP addresses initialization */ IP_ADDRESS[0] = 192; IP_ADDRESS[1] = 168; IP_ADDRESS[2] = 42; IP_ADDRESS[3] = 51; NETMASK_ADDRESS[0] = 255; NETMASK_ADDRESS[1] = 255; NETMASK_ADDRESS[2] = 255; NETMASK_ADDRESS[3] = 0; GATEWAY_ADDRESS[0] = 0; GATEWAY_ADDRESS[1] = 0; GATEWAY_ADDRESS[2] = 0; GATEWAY_ADDRESS[3] = 0;   /* Initilialize the LwIP stack without RTOS */ .... .. }   /*udp_echoserver.c */  void udp_echoserver_receive_callback(void *arg, struct udp_pcb *upcb, struct pbuf *p, const ip_addr_t *addr, u16_t port) {   /* Connect to the remote client */ udp_connect(upcb, addr, UDP_CLIENT_PORT);

I've been developing my own peripheral drivers as a learning exercise, and upon writing the USART drivers, I came to an interesting problem. The interrupts were not being handled at all! Instead of calling the ISR routine, I was getting UsageFault errors...​Upon closer inspection of the startup file (auto generated by CubeIDE), it didn't have any USART handler symbols at all. Just 0's and marked as reserved.​I attach a screenshot of part of the vector table section of the startup_stm32f401ccux.s file:According to the RM for the F401xC chips (RM0368), for example, right after the SPI2 handler, should come the USART1 and USART2 handlers, not the "reserved" 0's...​I added these handlers myself to the vector table (at the appropriate places according to the vector table in section 10.2 of the RM) and now the driver code runs smoothly as it should, with the interrupts being handled properly...​Maybe it's a bug in the auto-generation of these files?​

Hello everyone!I’ve tested wake up from standby mode with Wake up pins PI11 (and PI8). But it is not work I have remove all definitions about wake up pins in dts except place where it defines as wake up pins in stm32mp151.dtsi Entering in standby mode by putting ‘echo mem > /sys/power/state’. And after that MPU no wakes by I acting on pins PI11 or PI8.I do not see any WAKE UP Pins in /sys/kernel/debug/wakeup_sources, maybe I need activate it before going to standby?Do I need set MPU_BEN bit in RCC_MP_BOOTCR before going to standby mode? If yes — how?Maybe another my misunderstanding?

The STM32F7 supports Ethernet with MAC (and DMA), according to doc en.DM00224583.pdf.I try to connect it to a KSZ9896 (ethernet switch) that provides a direct MAC interface in RMII.The KSZ provides configuration bits similar to the STM32 ETH_MACxxx.I wonder if the connection between the 2 RMIIs needs any PHY.STM32 MAC <--> KSZ MAC OR STM32 MAC <--> PHY <--> KSZ MAC OR STM32 MAC <--> PHY1 <--> PHY2 <--> KSZ MACTheoretically, does a MAC-to-MAC connection requires any PHY? 0, 1 or 2? (my guess: 0)Does the STM32F7 specifically requires any PHY with its MAC layer?Is it possible to customize the HAL to bypass the PHY related code, and use only the MAC related code?Thanks in advance for your comments and answers!

Not sure where to report this.I have recently upgraded to OSX Big Sur and also to STM32CubeIDE 1.6.1Not sure when this issue started, I'm pretty sure it wasn't a problem before, and it does NOT happen on my Eclipse 2020-06 installation.Restarted, rebooted and reinstalled. No difference.The issue is that when a file contains inactive code, i.e. marked with #if / #endif, any entering of data BEFORE the #if will "disappear" as long as I type. About 2 seconds after the last keystroke, the entered data will appear. It's not entirely invisible when typing, there are some pixels fluttering at the bottom of where the characters should be.Entering data AFTER the #endif is no problem.If there are multiple inactive code blocks in the file, data can only be entered properly after the last one.This only happens if the code is inactive, with #if 0 as below. If I make the code active with #if 1, there is no problem.This happens in ALL my projects in STM32CubeIDE.And ONLY in files that has any inactiv

Good morning,I'm using a discovery board STM32H747-DISCO.Why, Touchgfx don't generate the project .ioc, to import in CUBE IDE?Instead, if I select another board (for example STM32F7508-DK) , when generate code, the compiler buil also .ioc file.I have also installed the last version 4.14.0 of TouchGFX, but the problem persist.Thank you

Actual version 1.5.0 of CUBE-IDE is a fail with respect to the above mentioned configuration (STM32H747-DISCO and TouchGFX)

I'm using TouchGFX version 4.16.1 with a STM32H747I-DISCO development kit. When I run the simulator or click Generate Code, the project file is created, but not the .IOC file. When I try to import the project into the STM32CubeIDE (Version 1.6.0) I can't because it doesn't find the .IOC file. Importing it as a make file pulls in the project and files, but I can't get it to compile. Generates lots of errors. Am I missing something or is there some other way to iport the project?

Hi,I am working on TouchGFX for STM32H747 Discovery Kit. I have a design created in TouchGFX Designer. I am looking to integrate this into STM Cube IDE. When I hit generate, I am not able to see the STM project being created in the TouchGFX project folder. From some community threads I got to know that application template for H747-DISCO would be ready by the end of 2020. Is it added? Is there another way to do this? Please let me know.Please refer the screenshots of the application template used and folder structure of TouchGFX project. Thank you,Arshiya Tabassum

Hi,I am working on TouchGFX for STM32H747 Discovery Kit. I have a design created in TouchGFX Designer. I am looking to integrate this into STM Cube IDE. When I hit generate, I am not able to see the STM project being created in the TouchGFX project folder. From some community threads I got to know that application template for H747-DISCO would be ready at the Q1 of 2021. Is it added? Is there another way to do this? Please let me know.Thank you,Enes Ozkaya

#autodevkit #softwarerelease #transportation #avas #keepdreaming #staysafeeveryoneDownload from:www.st.com/autodevkitswwww.st.com/spc5studioThis week featured component is the AVAS application based on a new integrated audio module with 2 audio amps, and SPC582B microcontroller. The board can be controlled via CAN bus.For more info check out AEK-AUD-C1D9031 on www.st.com

We boot up the odyssey Stm32mp157c board with distribution package. While booting the display is working but when i try to run qt examples it gives core dump error. Also there is no connector or encoder in the output of modetest. I could't figure out where to look. Thanks in advance.

Hi all,I am currently using VisionSoM board : STM32MP157AAB3 board.I am trying to drive an LVDS display via a RGB to LVDS converter. Here is the datasheet link for it.The panel settings are as follows : panel { u-boot,dm-pre-reloc; status = "okay"; display-timings { timing0: timing0 { clock-frequency = <72400000>; hactive = <1280>; vactive = <800>; hfront-porch = <22>; hback-porch = <150>; hsync-len = <160>; vback-porch = <32>; vfront-porch = <22>; vsync-len = <38>; hsync-active = <0>; vsync-active = <0>; de-active = <0>; pixelclk-active = <1>; }; }; };I also modified the driver : panel-simple.c file in kernel/drivers/gpu/drm/panel and added support for this custom display there.When i run qt demo for playing video on the RGB out i can see on oscilloscope that the clock signal frequency is not going beyond 66.6Mhz . Earlier I was stuck at clock generation frequency of 33.3Mhz since my ch

Hi guys. I'm going to design a PCB and I want to connect a 5MP camera module to my stm32. I did the same project with the VC0706 Camera Module (SC03MPD) and this time I want to have a higher resolution. Initially, I was thinking about a serial connection to the camera ( since the transfer speed is not important for me and I can use a low-speed image data transfer ) but it seems there are a few camera modules? with 5Mpixel resolution and serial interface so I was just wondering has anyone have any idea what is the cheap and easy way to have a 5Mpixel camera connection to stm32.

I'm using STM32L431xx series mcus and as with most STM32 mcus, it has an RTC feature with calendar. The RTC has a calibration function by which you can fine-tune the counting scheme of the RTC and improve upon the accuracy of your clock source.​This works well in theory, but in reality, take into consideration that I'm using an internal clock source (LSI), I wonder how and if this should be put to use.​By that I mean if there is a common characteristic for the LSI, as in does it have a consistent tendency to tick slower or quicker over time, and if this consistency can be observed throughout even different batches.​The official tech-docs puts the accuracy of LSI at ±5%, at the first look it implies it could either go faster or slower than it should, thus rendering the calibration really difficult, since:There could be no consistency within the same batchIf the development chip is different than the production chip, the calibration is rendered uselessEven if consistency is not a major i