Solved

Hi,I am setting up my STM32F405RG with 3 analog inputs on ADC with DMA.The problem I'm having is that the ADC buffer is being filled in the wrong order:For example, I have channel 11, 12 and 13, with ranks 1, 2 and 3 respectively, so I presume the ADC buffer should be as follows:adc_buf[0] -> data from channel 11adc_buf[1] -> data from channel 12adc_buf[2] -> data from channel 13...but what I am actually getting is:adc_buf[0] -> data from channel 12 - this wrong orderadc_buf[1] -> data from channel 11 - this wrong orderadc_buf[2] -> data from channel 13adc_buf is defined above int main():#define ADC_BUF_LEN 3   uint16_t adc_buf[ADC_BUF_LEN];  in int main we have:int main(void) { /* USER CODE BEGIN 1 */ /* USER CODE END 1 */   /* MCU Configuration--------------------------------------------------------*/   /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init();   /* USER CODE BEGIN Init */ /* USER COD

Couldn't find a "general questions" category, so goes here...I've registered to STM webinar Accelerating STM32 application development with new STM32Cube Tools on Sep. 22 . I received a "Webinar login information" which has no login but only yet again "join the webinar" button...So far I don;t have login and I don;t have a link to the webinar and / or webinar software to download... Also the webinar registration page does not have any contacts links for specifically addressing the webinar questions... so STM does not provide any venue to get help with webinar participationSo I apologize for placing this to the wrong category although the topic of webinar belongs here :)Can anybody help?

Hi,I am trying to check IWDG functionality on Nucleo-L4R5ZI board.Referring to the example code available for NUCLEO-L496ZG, i created new project for L4R5ZI nucleo. I was trying to go step by step in debug mode. When the debugger is inside HAL_IWDG_Init(&hiwdg), it was able to successfully enable IWDG using __HAL_IWDG_START(hiwdg);But when do step into IWDG_ENABLE_WRITE_ACCESS(hiwdg); the debugger enters into system memory. I confirmed this by PAUSEing the debug, and it stopped at 0x1FFFxxxx address. At the same time, LD3 led is glowing. Nowhere in the code I control the LD3. What is happening ? Pls help.Code is as below:/* Includes ------------------------------------------------------------------*/ #include "main.h"   /* Private includes ----------------------------------------------------------*/ /* USER CODE BEGIN Includes */   /* USER CODE END Includes */   /* Private typedef -----------------------------------------------------------*/ /* USER CODE BEGIN PTD *

Hi all,First post on here so apologies if I make some errors in my question format/clarity.I am doing some testing using the SPI HAL library attempting to communicate with another chip, everything works as expected and I can successfully send bytes and receive the expected data. There is, however, one slight bugbear that I can't seem to explain or overcome. Straight after the STM32F072RB is reset the SCK signal is held high (implying a high idle state), however I have set my SPI up to communicate using MODE 0, i.e. low idle state, and sample on the rising edge. This high idle state causes the first received data to be left-shifted by 1 bit, as the first transition the clock performs, after the SS is asserted, is falling edge indicating the data to change for the subsequent rising edge. All transactions after this first are correct.This is incorrect behaviour, and SCK should idle low at all times. I have tried pulling the GPIO low before setting it up as an alternate function pin, pulli

Hi.I'm wondering about discrepancies in antenna dimensions between AN5129 application note and the actual board - Nucleo MB1335. As you can see the differences are subtle but visible. I'm mostly curious about why the antenna width varies? Widths at different spots I was able to measure: 0.4mm, 0.425mm, 0.45mm, 0.475mm, 0.5mm.Also, the gap between parallel arms varies between 0.725mm and 0.75mm, which is different than 0.8 specified in the app note.Is there a reason for that or is it simply a mistake while doing a layout? I can see that the antenna wasn't defined as library component but rather drew as a polygon.

Hi ST Teams,I'm building successfuly an image "st-image-core", for stm32mp1 machine.I'm able to add python package and remove some package too.But unfortunately, My team who works on M4 copro can't connect anymore on it.If i made a sd card with starter kit on it, M4 can connect (ie debug run & so on)If i made my st-image-core, it can't.Is there any special "append" to add to my distro in order to get things works?I'm using SDK 1.2Thanks in advance.

In DS12712 Rev 2 (STM32G473) table 13 shows PB10/11 as CAN3_TXFD/CAN3_RXFD but in table 12 CAN is not listed for these pins. Also in tab 13 sometimes it is CAN3_TX and sometimes CAN3_TXFD. Which one is valid ? Interestingly in STM32G474 tab 13 both CAN pinout and naming is different.

I downloaded the software pack en.x-cube-nfc3.zip for the nucleo NFC-03A1.I tried to import the demo STM32F401RE_NUCLEO_PollingTagDetectNdef.If I do a normal import into workspace, the imported project contains only link to non existing files.I can import the projet only if I select Import AC6 System ...In this case, the compiler aborts with this message: arm-none-eabi-gcc "C:/ws/STM32CubeExpansion_NFC3_V2.1.0/Middlewares/ST/rfal/Src/rfal_analogConfig.c" -mcpu=cortex-m4 -std=gnu11 -g3 -DUSE_HAL_DRIVER -DSTM32F401xx -DSTM32F401xE -DUSE_LOGGER -DST25R95 -c -I../../../Inc -I../../../../../../../Drivers/STM32F4xx_HAL_Driver/Inc -I../../../../../../../Drivers/STM32F4xx_HAL_Driver/Inc/Legacy -I../../../../../../../Drivers/CMSIS/Device/ST/STM32F4xx/Include -I../../../../../../../Drivers/CMSIS/Include -I../../../../../../../Drivers/BSP/Components/ST25R95/ -I../../../../../../../Drivers/BSP/STM32F4xx-Nucleo -I../../../../../../../Middlewares/ST/rfal/Inc -I../../../../../../../Middlewares/ST/nde

Hi , We want to design the Antenna for NFC Reader IC ST25TV02K , so any reference design available for Antenna Designing ? What is the recommended Impedance or more specifically inductance for the antenna ?

Hello,I am working on a project where I have to interface the LIS2DE12TR Accelerometer via I2C interface with TI cc2652 chip. As a start I wanted to verify the hardware functionality. In the datasheet it is mentioned of a Self-Test Mode of operation. I did not understand how the operation can be verified in the self-test. Should we just enter into self test mode and then monitor the x,y,z output values and check if they are within the specified range ? Also is there any example for this self test procedure that has been done.Also in the datasheet there is mentioned a Slave Ack and a Master ACK. How do we know that the slave Ack has been received and how do we send a Master Ack/NackRegards,SS

Dear contributorsIn order to make this forum efficient in helping newcomers and all users of this forum to find solutions to their problems in the already resolved issues or questions , please adhere to the following rules:the post title must be shortthe post title is not a chat (no "Hi" or "Hello", no newline, no "I" or "it", and so on)the post title has to be very meaningful of your issue or question (no general title such as "Problem with the tool MC-SDK")if possible, only one new post for each of your issues or questionsif possible and if relevant, do not forget to give details about your materials (such as boards ID and versions)if possible and if relevant, do not forget to give details about your tools (detailed list of tools with the version for each)your personal details have not to be inserted in the text (phone number, email, and so on)do not post a message on the forum, which targets everyone, in asking to a particular member to answer (don't worry, we now handle absolutely

..

..

Hello,I'm try using ISM330DLC connect to Linux OS on board IMX8MP via I2CLinux supported driver for this device (iio/imu/st_lsm6dsx); I added to dts file as below:&i2c5 { clock-frequency = <100000>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_i2c5>; pinctrl-assert-gpios = <&pca6416 2 GPIO_ACTIVE_HIGH>; /* i2c5 pin conflict with can1: default gpio low select can1, gpio high select i2c5 */ status = "okay";   ism330dlc@6b { compatible = "st,ism330dlc"; reg = <0x6b>; st,drdy-int-pin = <1>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_ioexp_int>; interrupt-parent = <&gpio1>; interrupts = <12 IRQ_TYPE_EDGE_RISING>; }; };But I didn't see any interrupt signal to Linux# cat /proc/interrupts | grep 12 6: 12073 10115 14187 8714 GPCv2 i.MX8MQ 47 Level timer@306a0000 38: 127 0 0 0 GPCv2 i.MX8MQ 76 Level 30ad0000.i2c 46: 6787 0 0 0 GPCv2 i.MX8MQ 120 Level 30be0000.ethernet 50: 0 0 0 0 GPCv2 i.M

..

Hi, All.Program fuses values is a delicate task. I would like to confirm that it is possible to program PKH(Public Key Hash) using STM32_Programmer_CLI.The PKH is stored in OTP WORD 24 to 31For example: Set the value 0x9ffd3d2f into the word 24 (0x18) [pkh0]STM32_Programmer_CLI -c port=usb1 -otp program wordID=0x18 value=0x9ffd3d2fIs this right?Is there a specific command to close the device from STM32_Programmer_CLI?Thanks!

My STM32F769-disco is connected via built-in st-link 2.1 to my computer. I use the bypass USART for printf(). And that works OK for output data, whereas input data stuck before they come to USART->RDR and do up the RXNE flag indicating an interrupt.Here the states of registers involved in the process.USART1->CR1 = 0x0000002d (UE, RE, TE, RXNEIE)USART1->ISR = 0x006200c2 (FE, TC, TXE, CMF, TEACK, REACK)NVIC->ISER1->SETENA = 0x00000020NVIC->IPR9->IPR_IN0 = 0xe0So, it is seen that the USART is adjusted right. The hex-data of NVIC indicate the state of the interrupt had been set and it could be confirmed by changing the flag RXNEIE to TXEIE or TCIE (the interrupt starts to work as it has to, or, at least, as it is expected). PA9 and PA10 are set as push-pull alternatives AF7 at the highest speed.I made a tryout to set RX as a floating input with no result. RCC is set correctly as well.Is here a little secret maybe or something kind of? Thanks any help. -)

I am using STM32L072RB MCU.I am trying to scan the devices connected to i2c bus (i2c2 and i2c3)following is my function#define DEBUG 1 void i2c_scan(void) { uint8_t *p_data; uint16_t addr_scan = 3 ; printf("I2C3 Address : ");  //scanning i2c devices from address 3 to address 127 in i2c3 of MCU for(addr_scan=3; addr_scan <=0x7F ; addr_scan++) { #if DEBUG printf("\r\naddr_scan : %d",addr_scan); #endif if(HAL_I2C_Master_Receive(&hi2c3,(uint16_t)(addr_scan << 1),p_data,1,500) != HAL_OK) { continue ; } printf(" 0x%x",(addr_scan << 1)); }   printf("\r\nI2C2 Address : ");  //scanning i2c devices from address 3 to address 127 in i2c2 of MCU for(addr_scan=3; addr_scan <=0x7F ; addr_scan++) { #if DEBUG printf("\r\naddr_scan : %d",addr_scan); #endif if(HAL_I2C_Master_Receive(&hi2c2,(addr_scan << 1),p_data,1,500) != HAL_OK) { continue ; } printf(" 0x%x ",(addr_scan << 1)); } }I

Just trying to wrap my head around the IDE and can't find a reference to this.Ta

I want to use the Interaction function "Hardware button is clicked" ​.Can it work in PC simulation? Like i press 'w' on the keyboard of PC，and it call a function.Is there an example program for it.

I tried install different Cube version ,include latest version on 2 windows computers . both them are disabled HSE configuation in clock configuation dialog.Since HSE disabled and USB clock also inavliable.Who can tell me why and how solve this issue. ( Manually coding please skip, I mean this tool, STMicoelectronics launched tool) 

I am just trying to use the STM32CubeMX tool.The application needs two USARTs. One for communication with external processor. This will be an RS485 interface. The PCB will have hardware for RS485 transceiver, mux/demux for directionality of transmission. Due to this, I am configuring this USART in asynchronous mode (no flow control for RS232 or RS485). This USART1 will also be used as a bootloader. Please confirm if this configuration will work. For the NVIC settings, I enabled the USART1 global interrupt. Will this interrupt trigger both on transmit and receive bytes?I also need the serial wire debug capability. I want to configure a separate USART (USART2)for this. Do I configure this the same way as USART1? Initially I will be using the ST-Link debugging tool, later maybe the JLink SWD. I will disable the interrupt for this. Please confirm if correct.Thanks,Priya

​Hello,I have missed to confirm my registration ​on webinar, could you confirm my participation?I have received the board for this webinar, thank you.​Best regards, Oubaid.​

Hi ST,I received an email this morning (21st September 2020 at 7:00) with the prerequisites for the training on the 22nd.XSBSFURequest SoftwareRequest for software successfully submitted. The approval process may take up to 48 hours. After you have been approved, you should receive a link to the requested software via email.Hopefully this is not the case as I won't be setup for the training tomorrow. Maybe try sending the emails out earlier next time?Mark Symonds

..