Solved

Hello!I have a quite specific question about STM32L4-MCUs. For a project, I would like to use code Readout Protection (RDP), but I have to be able to mass-erase the chip and manually upload a new image. So only RDP level 1 is an option. But with RDP, the debug port seems to have access to SRAM1 and to most of the registers. This is undesirable, because an attacker could read out all sorts of information. So my question is: is it possible to disable SWD and JTAG debugging (manually from user code) when activating RDP level 1, so that the debug interface cannot be used anymore to read out registers and SRAM1, as this functionality is not needed, but still being able to perform a forced mass-erase on the whole chip and reset it to factory, kind of?Thanks and best regards, the blackrod

Hello,I am not able to activate the module entry in Clock Component RLA. Can you please guide me how to do the configuration for sending the uc in standby mode.

I am using a CR95HF chip with ISO14443A cards. I can select the card, read it's UID and all the data storred on the card without any errors.The problem is when I remove one card out of the field and place another card in the field, it refuses to respond. The only way I can get it to respond to the next card is to reset the chip.Both cards are functional, the first card is allways read ok, but the second card allways errors no matter which card I scan first.Is there a "deselect" command ?Also what are the responce codes ? (section 5.1 of the datasheet). i.e. you send a command to the chip and get a responce code back. i.e. I think 0x87 is "bad length parameter"Thanks!

We are porting a piece of software from STM32F1 to a STM32F091.One part of the software is using bit banding. But in the library heade is no definition for the bit danding area in the memory.I fear bit banding is not supported by this special device? Is that correct?

Dear all,In hal driver datasheet, the funcion HAL_PWREx_EnableWakeUpPin is defined like this : void HAL_PWREx_EnableWakeUpPin (PWREx_WakeupPinTypeDef * sPinParams)In stm32h7xx_hal_pwr.c from STM32Cube FW_H7 V1.5.0 library is defined like this : void HAL_PWR_EnableWakeUpPin(uint32_t WakeUpPinPolarity)Is there a mistake ?Thanks,

Hi,I am working on the power delivery expansion pack with cpm tcp architecture by using STM32F072 and PTN5110 as tcpc. Right now i am configuring one of the ports for sink and connect to PD2 capable source device. I am able to get 5v default voltage. however for the later stages of power negotiation i have been stuck at where the Sink generates the last GoodCRC message. this has been always get stuck within the PE_State Machine which is not accessible. Is there a way to get an access to this core function to figure out why the negotiation get stuck? In attach you can see the log file of the traces i m getting. Please feel free to comment on the negotiation, how it should be, if there is something else wrong and how to fix it! Thanks,Faik0 EVENT 381188 1 EVENT_ATTACHED 1 DEBUG 381188 1 VBUS:2393, CC:2 2 SRC 381288 1 SRC_CAPABILITIES DATA:2C91012E / 5V - 3A SOP PD2 H:0x1161 3 SNK 381289 1 GOODCRC SOP H:0x0081 4 SNK 381300 1 REQUEST DATA: 96580211 / ObjectPosition:1 / GiveBack:0 / C

I have implemented a TextArea without wildcards to display fixed Chinese content. I have now created a TextArea with wildcards and want to dynamically display any Chinese content in the TextArea buffer. But so far all that has shown is "??? ". How to operate, thank you

hi all.I use touchGFX with FreeRTOS.My other Task is working fine. However, A few minutes after the system starts, the touchGFX task is blocked and will not run. This phenomenon occurs more quickly when the 16-bit control is performed than when the external RAM data line is 32-bit.I'm not sure what I'm going to review. What should I check?​

Hello,I have a display issue when I using the wildcard buffer.I already used wildcard buffer by the past on a previous version of touch GFX.I created a new project for a custom board and the problem is that I can't modify a text with the wildcard buffer. See my function below : void Screen1View::Button1clicked() { Unicode::snprintf(textArea1Buffer, TEXTAREA1_SIZE, "Bonjour"); textArea1.resizeToCurrentText(); textArea1.invalidate(); }On the screen the letters (B,o,n,j,o,u and r) seems to be all on the top of the others, all at the same position.I made some tests and in another one, I obtained only few letters of the complete word "njo" for exemple. I think I use touch GFX function as needed because as I said I already complete an application on a previous custom board. The only one difference is that on the previous project I used IAR and for this new one I use Atollic.I also tried to complete the buffer, char by char : textArea1Buffer[0] = 'B'; textArea

I'm working on a project that involves NFC communications, so I bought the two product listed in the title to start prototyping. The first step in my plan was to get some sample code running, so I downloaded the X-CUBE-NFC5 package. However, it's unclear to me how to import the source code into a project. I'm using the STM32CubeIDE. Since I'm not using one of the Nucleo dev boards with a pre-built binary, I can't just flash a .bin file, but even if I was, I would still need the example code working to base my application off of.So far, I've tried bringing in source and header files one folder at a time to resolve "file/path not found" errors on "include" lines. It's a slow process, but after fixing a few typos and mysterious errors, I ran into an issue I can't fix: the assembly (*.s) files in the Startup folder are written in the armasm syntax, but the arm-none-eabi-gcc assembler only accepts GNU syntax, so each line comes up as an error (including comments). I tried transplanting a st

..

Hi!I have a question. I know that the question is similar to https://community.st.com/s/question/0D50X0000APcm2T/stm32cubemx510-adc-dma-continuous-requests-doesnt-workBut I have heard that this bug was fixed in CubeMX 5.2.0. I'm using CubeMX 5.3.0 with Nucleo STM32F446RE board and this I want I get when I start a new project.As you see, "Disable" is only selectable option here. Why? Here is the data sheet:https://www.st.com/content/ccc/resource/technical/document/reference_manual/4d/ed/bc/89/b5/70/40/dc/DM00135183.pdf/files/DM00135183.pdf/jcr:content/translations/en.DM00135183.pdfHave a look at this picture. DMA is available.

Hi, I'd appreciate it if you could answer a few questions.I try to use HAL_CAN_Recive_IT in the HAL example, but it's not automatically set up in CUBEMX. Why? And how do I use the HAL command in TRUESTUDIO?

..

Today I decided to start a fresh project on my NUCLEO-F429ZI board. As I tried to select the board, I was notified that that board is obsolete, and CubeMX won't generate code for it. Soon, I found that all boards are marked obsolete! So I am pretty sure it is a bug. But that means I can't proceed with my work unless I am willing to spend time on finding and setting up the old working version - if at all it is still available for download. and then merge my code to the latest CubeMX generated code when the bug is fixed. This is a lot of extra work.There should be more stringent testing done on software before releasing it. This is not the first instance of ST's software creating trouble. I do understand presence minor bugs. But the kind of bugs I come across with ST give an impression that the software development processes are far from mature.Examples:When you make some changes in the .ioc file and regenerate the code, once in a while it says firmware not available in repository even t

I've been having trouble with the GPIO BSRR/BRR registers for the part i'm emulating in Keil, as the setting of bits in these registers aren't having any affect on the ODR register.I've been trying to just have a loop toggle the state of a pin, which should be writing to BSRR/BRR registers for that port to set and reset that pin respectively.However, when monitoring the state of the ODR bit for this pin, it isn't being toggled.Code Snippet as follows:while (1){ HAL_GPIO_TogglePin(RST_OUT_N_GPIO_Port, RST_OUT_N_Pin); }// And the HAL function call:void HAL_GPIO_TogglePin(GPIO_TypeDef *GPIOx, uint16_t GPIO_Pin){  /* Check the parameters */  assert_param(IS_GPIO_PIN(GPIO_Pin));   if ((GPIOx->ODR & GPIO_Pin) != 0x00u)   {    GPIOx->BRR = (uint32_t)GPIO_Pin;   }  else   {    GPIOx->BSRR = (uint32_t)GPIO_Pin;   }}-------------------------------------------------------------------------I

Yesterday my cubeide is working well. But today when i want to configure project with default peripheral but all board display warning  The target device 'STM32XXXX-***"is currently not supported by STM32CubeIDE according 'Obsolete' marketing status The target device 'STM32F072B-DISCO' is currently not supported by STM32CubeIDE according 'Obsolete' marketing statusi tried uninstall cubeide and install again but this problem cant fix. anyone help me fix this problem. Tks

I just wanted to create a new project for the board ( last project I created about 24 hours ago, was still working ). That caused an update to run, the device is now obsolete, and I can't create projects, get the error: The target device 'STM32F429I-DISC1' is currently not supported by STM32CubeIDE according 'Obsolete' marketing statusAs of now, the status on https://www.st.com/en/evaluation-tools/32f429idiscovery.html is still ACTIVE. What is that, and how can it be fixed urgently?

I was thinking that it would really useful if there was a ready to use Raspberry-Pi computing module look alike STM32MP board which could be used in development of user applications.The reason is because although ST has designed MP series to be optimized for 4Layer PCBs, the cost of 4 Layer PCB manufactoring yet is much higher than 2Layer ones. And also most of the times the PCB layout for MCUs and MPUs must remain the same around the chip. So why not provide a pre-made module for prototyping? and also if with a resonable price for productionThe module could contain an MPU + SDRAM + Flash and all the side requirements. It would bring out all the GPIOs out with probably 2mm or 1.27mm header pins (and not like RPi way which requires a DIMM socket which is not so common and usual)

I'm using STM32F103RBT6 to connetc to a OLED with I2C1.The init code is as below.static void MX_I2C1_Init(void) {   /* USER CODE BEGIN I2C1_Init 0 */   /* USER CODE END I2C1_Init 0 */   LL_I2C_InitTypeDef I2C_InitStruct = {0};   LL_GPIO_InitTypeDef GPIO_InitStruct = {0};   LL_APB2_GRP1_EnableClock(LL_APB2_GRP1_PERIPH_GPIOB); /**I2C1 GPIO Configuration PB6 ------> I2C1_SCL PB7 ------> I2C1_SDA */ GPIO_InitStruct.Pin = LL_GPIO_PIN_6|LL_GPIO_PIN_7; GPIO_InitStruct.Mode = LL_GPIO_MODE_ALTERNATE; GPIO_InitStruct.Speed = LL_GPIO_SPEED_FREQ_HIGH; GPIO_InitStruct.OutputType = LL_GPIO_OUTPUT_OPENDRAIN; LL_GPIO_Init(GPIOB, &GPIO_InitStruct);   /* Peripheral clock enable */ LL_APB1_GRP1_EnableClock(LL_APB1_GRP1_PERIPH_I2C1);   /* USER CODE BEGIN I2C1_Init 1 */   /* USER CODE END I2C1_Init 1 */ /** I2C Initialization */ LL_I2C_DisableOwnAddress2(I2C1); LL_I2C_DisableGeneralCall(I2C1); LL_I2C_EnableClockStretching(I2C1); I

Hi,I am executing echo_tty_echo example and trying to get the messages coming from m4 inside qt program as follows:   QString line;   QStringList list1;   char buff[100];   while (1) {       QProcess::execute("echo hello > /dev/ttyRPMSG0");       QFile armIpcReadMsg("/dev/ttyRPMSG0");       if(armIpcReadMsg.exists())       {           if(armIpcReadMsg.open(QIODevice::ReadOnly | QIODevice::Unbuffered)           {               armIpcReadMsg.read(buff,100);               line = QString::fromLatin1(buff);     

..

I'm using a Nucleo-H743ZI2 to learn more about the H7 architecture in preparation for a project. I'm using the latest STM32CubeIDE with the 1.5.0 firmware, but I also tried (with no difference) STM32CubeMX.I very much prefer the LL libraries to the HAL, so after having built a test app with HAL, I went into the Project Manager, Advanced Settings page of the configurator, to select LL libraries instead of HAL. To my surprise, only the GPIO LL library was selectable, and there was no way to set LL libraries for RCC, ADC or USART. I can see that LL libraries are provided (and documented) in the firmware, and the few LL examples for my board have the code to initialize the RCC, so clearly I could make the LL to work, but I would lose the ability to use the configurator.Why are the LL libraries for H7 provided but not usable from STM32CubeIDE?EDIT: I tried again using my STM32F407VGT6 board, and as expected I could configure RCC, ADC, DMA and USART using the configurator and LL libraries, e

Hello,Micro-controller used : STM32F779NIQuestion:My understanding is that there are two 1.2 V internal regulators.[1] The regulator that gets enabled by holding BYPASS_REG pin as low[2] The backup regulator that gets enabled through PWR_CSR1.BREAm i right ?Regards,Vinoth

..