Solved

I have some problems in understanding the appropriate way to setup the ST25R3916 chip to being in sleep mode, wake up the Microcontroller from an interrupt and then read an NTAG type A message and finally putting the NFC Chip back to wakeup mode. I am working with the NFC06A1 Example code, using a STM32-L476RG.I would like some ideas of the functions that need to be called in order to properly work with the RFAL State machines.

..

I need to mount a Nucleo-64 development PCB as a plug-in to a PCB motherboard and need to locate the mechanical Gerber files so that I can create a footprint in Eagle CAD.

Hello, I am simply tring to communicate with the L3GD20 Gyrosensor using the WhoAmI command. I am sending 0x0F and i'm expecting 0xD7 back (11010111) but I only received 0xFF which means i'm doing something wrongI am using STM32CubeMX to generate the code , Keil IDE and using STM32L071 https://www.mouser.co.uk/datasheet/2/389/l3gd20h-954865.pdfAny help would be appreciated!//put CS low HAL_GPIO_WritePin(GYRO_CS_GPIO_Port,GYRO_CS_Pin,GPIO_PIN_RESET); //Transmit register address spiData[0] = 0x0F; HAL_SPI_Transmit(&hspi1,spiData,1,10); //read HAL_SPI_Receive(&hspi1,&spiData[1],1,10);   //put CS High HAL_GPIO_WritePin(GYRO_CS_GPIO_Port,GYRO_CS_Pin,GPIO_PIN_SET);

I wonder why are all ACI commands, that imply using pointer-to-const parameters actually use non-const ones? Is there any reason? Will it ever be fixed?For example:tBleStatus aci_gatt_add_service(uint8_t Service_UUID_Type, Service_UUID_t *Service_UUID, uint8_t Service_Type, uint8_t Max_Attribute_Records, uint16_t *Service_Handle) { <...> Osal_MemCpy((void *) &cp0->Service_UUID, (const void *) Service_UUID, size); <...> }

There are many occasions where I would like to put simple graphics up on a TV - to use it like a giant oscilloscope, or to log data via an optically isolated link. Monochrome, low resolution would be fine. It sounds like you have to pay licensing fees if you want to sell a product using HDMI ($5K a year!?). So VGA seems like the simplest approach, and if the TV doesn't have a VGA input, you can buy a VGA to composite converter. (But I have noticed that some newer TV's only seem to accept HDMI as an input option).I know there are options on the web for building your own VGA interface - and I may end up resorting to that. But I thought I would add my name to those who would like a VGA connector on a DISCO board - as Clive commented back in 2016 :"I'm surprised ST doesn't have a DISCO with a VGA 15-pin connector on it. A Video DAC might be asking a bit much, but a resistor chain/ladder would do, and it wouldn't have the licensing or IP issues of HDMI, etc."

�? original source code : B-L475E-IOT01A.(STM32L475V)�? IDE Tool : uVision �? Symptom : When i set PA2 as output, Program go into HardFault_Handler() it can't reach while(1); Other ports are no problem. only PA2 has this problem.�? source code int main(void) {  HAL_Init();  SystemClock_Config();   __HAL_RCC_GPIOA_CLK_ENABLE();  GPIO_InitTypeDef gpio_init_structure;  gpio_init_structure.Pin  = GPIO_PIN_2; //gpio_init_structure.Mode =GPIO_MODE_OUTPUT_OD; //gpio_init_structure.Mode =GPIO_MODE_AF_OD;  gpio_init_structure.Mode = GPIO_MODE_OUTPUT_PP  ;  gpio_init_structure.Pull = GPIO_NOPULL;  gpio_init_structure.Speed = GPIO_SPEED_FREQ_HIGH;​  HAL_GPIO_Init(GPIOA, &gpio_init_structure); while(1);​

As the topic says i want to implement double buffer for my ADC on DMA interruption to save data on SD card.I've done two buffors. I am saving data to two of them in sequence. If one gets to it's limits the other one is taking the data. To point the cell of my buffer, I am using iterator. The problem is my iterator doesn't reset despite of code that does that. Whole two buffors are filled with data in first loop, then iterator gets stuck. Here is code.uint32_t measurementADC; uint16_t buff1[256]; uint16_t buff2[256];   int buff_iterator = 0; bool flag_active_buff = true; bool flag_to_save = false;   void HAL_ADC_ConvCpltCallback(ADC_HandleTypeDef* hadc){ if(buff_iterator==255) { flag_active_buff = !flag_active_buff; flag_to_save = true; buff_iterator=0; } else { flag_to_save = false; } if(flag_active_buff == true) { save_to_buff(buff1, measurementADC); } else { save_to_buff(buff2, measurementADC); } } void save_to_buff(uint16_t table[], uint16_t value)

Hi, I have about half year experience now with STM32H750 hardware, and all working very nice now. Up to now I always had used Revsion Y chips.Now on the last order we got Revision V chips (LQFP100 housing, chip marking line 1: "STM32H750", line 2: "VBT6 V", line 3: "VB454 VQ", line 4: "PHL 7B 944"). ... with this chip I cannot connect any more with Keil ArmCC (I must admit older 32bit Version of Keil ARMCC V5...).ST-Link with the new Rev V works ok: After connect it shows "Device: STM32H7xx, Device ID: 0x450, Revision ID: Rev Y, Flash size 2MBytes".(2MBytes is wrong, it really should say here 128kB). If I connect the new "Rev V" STM32H750 device, then for Revision ID, ST-LINK gives the message "Unknown" (it should say "Rev V" here I assume).I tried already ST-Link Firmware update, this seems to work nicely (I use some older "STM32F401 Discovery board" for ST-LINK Hardware connection.Can somebody give me a hint how to update ST-LINK such, that "Rev V" will show correctly after connect?

Hi All,I'm searching for example Bootloader code for SPC560P50L3 controller ( 100 pins package). I tried import from the example code in SPC5 studio, but it is for a SPC560P50L5 controller. How I can convert this code SPC560P50L35controller ( 144 pins package). I need to match the controller pin mapping Is there any way to convert this code to 100 pins package controller OR is there any bootloader example code available for SPC560P50L3 controller, where i can find it.Please suggest me the link or method to convert it.Thanks,Basava.

We were planning to replace our STM32WB55 design with an STM32WB50CG, unfortunately we saw the errata document DM00625356.In particular we need to operate with LSI2 for the Bluetooth and cannot add an LSE crystal.When will there be a silicon revision to STM32WB50 that fixes this issue?

In the linker scripts for BLE_p2pServer_ota in CubeWB1.3.0, the ld script puts the OTA_TAG at 0x08007178:/* Specify the memory areas */ MEMORY { FLASH (rx) : ORIGIN = 0x08007000, LENGTH = 1k RAM1 (xrw) : ORIGIN = 0x20000004, LENGTH = 191k RAM_SHARED (xrw) : ORIGIN = 0x20030000, LENGTH = 10k OTA_TAG (rx) : ORIGIN = 0x08007178 , LENGTH = 599k }However, the BLE_ota example checks a COMPLETELY different address in CheckFwAppValidity:static uint8_t CheckFwAppValidity( void ) { uint8_t status; uint32_t magic_keyword_address; uint32_t last_user_flash_address;   magic_keyword_address = *(uint32_t*)(FLASH_BASE + (CFG_APP_START_SECTOR_INDEX * 0x1000 + 0x140)); last_user_flash_address = (((READ_BIT(FLASH->SFR, FLASH_SFR_SFSA) >> FLASH_SFR_SFSA_Pos) << 12) + FLASH_BASE) - 4; if( (magic_keyword_address < FLASH_BASE) || (magic_keyword_address > last_user_flash_address) ) {In particular the line:magic_keyword_address = *(uint32_t*)(FLASH_BASE + (CFG_APP_START_SECTOR_I

Hi i have a B-F446E-96B01A development Board.but i don't know this board's reference setting in cubeMX.plz help me

..

The hardware I have is the STM32G0 Discovery Kit. The sample code using this hardware works normally. I tried to rebuild a project using CubeMX. I found that it would be in CHECK_PE_FUNCTION_CALL (USBPD_PE_Init (USBPD_PORT_0, (USBPD_SettingsTypeDef *) & DPM_Settings [USBPD_PORT_0] , & DPM_Params [USBPD_PORT_0], & dpmCallbacks)) An error code USBPD_PDFU_NODATA appears. I cannot tell what went wrong with this error code. I increased the heap size and stack size according to similar suggestions, but it doesn't work. Maybe where is the problem?

Posted on June 17, 2018 at 12:09I'm reading data from a UART with DMA and want to write that data to an SD card (on a F722). Since the data is much longer than my buffer, I chose circular buffer for the DMA.The problem now is that I need to save the receive buffer to SD occasionally, but how do I know when I need to do this?Can someone recommend the best approach here, using Cube HAL: Should I chop my Receive_DMA() into smaller chunks of buffer size, and receive them individually?  (I may loose data.)Should I count the number of received bytes (how?) and save the buffer if some threshold is reached?Can I enable direct UART-to-SDMMC DMA?  (I don't even know what that means: Does the data go into an open file, and how can I remove the length header of the data first?)I'd really appreciate some ideas. The Cube examples are way too simple.#dma

I think I have discovered a bug in the way CubeMX behaves when both SPI and DMA are enabled. I am using the P-NUCLEO-WB55 board. If you look at the SPI_FullDuplex_ComDMA_Master example application, this runs fine on the P-NUCLEO-WB55 with a jumper between MISO and MOSI. However, if you exchange two lines in main.c so that we have:MX_GPIO_Init(); MX_SPI1_Init(); MX_DMA_Init();instead of:MX_GPIO_Init(); MX_DMA_Init(); MX_SPI1_Init();then the example fails. However, this is exactly what CubeMX does if we follow these steps:Create a new project for the P-NUCLEO-WB55-Nucleo (do not initialize peripherals in default mode)Enable SPI1 as full duplex master with SPI1_SCK on PA6Save and generate codeAdd SPI1_RX and SPI1_TX DMA requestsSave and generate codeThe problem does not occur if we don't save and generate code after enabling SPI1, i.e.:Create a new project for the P-NUCLEO-WB55-Nucleo (do not initialize peripherals in default mode)Enable SPI1 as full duplex master with SPI1_SCK on PA6Add

Hi,I want to use lfn feature in sd card and i use stm32f4 for this purpose i set _USE_LFN to 1 and _MAX_LFN to 255 . when i create the file , file is created but when i want to return file name , returns wrong.please guide me, how to return file name when i use lfn feature?i attache the code.unsigned char save_file_sd_log(void){ rtc_get(NO_CHANGE);delay_ms(5); if (INSERT_SD ==0) { res=disk_initialize (0); if (res==FR_OK) { rtc_get(NO_CHANGE);res=f_mount(&SDFatFs,"1:/", 1);if (res!=FR_OK && res!=FR_EXIST) { sprintf(str,"save log to sd ERROR f_mount:%d",res); debug(str); return 0; } res=f_mkdir ("1:/LOG");if (res!=FR_OK && res!=FR_EXIST){ sprintf(str,"save log to sd ERROR f_mkdir:%d",res); debug(str); return 0; } if(AA_SaveOnCycleFile==1){ sprintf(name_file_str,"1:/LOG/CYCLE%02d%02d%02d.log",year_shamsi,month_shamsi,day_shamsi); res = f_open( &SD_File , name_file_str ,FA_OPEN_ALWAYS | FA_READ | FA_WRITE);}else{ sprintf(name_file_str,"1:/LOG/EVEN

I am having a problem with a timer. I use CubeMX LL drivers, with basic time-base timer configuration.STM32L100RCT6, TIM6 and TIM7. Core Clock = 32MHz, PCLK1 (TIM6 and TIM7) = 32MHzPrescaller = 31, which should set timer to tick at 1us. ARR value is set to max, 65535, interrupts are disabled.Although my timer does tick at 1us, starting and stopping timer adds another few microsecond, which is unacceptable for my application. I added GPIO writes (directly using registers) and check timings with logic analyzer.Here is the pseudo-code of my test:// start timer <GPIO HIGH> LL_TIM_SetCounter(TIM6, 0); <GPIO LOW> LL_TIM_EnableCounter(TIM6); <GPIO HIGH> while(LL_TIM_IsEnabledCounter(TIM6) == 0) {}; <GPIO LOW>   // poll timer until value match while(getUsDelayTimerValue() < 99) {}; <GPIO HIGH>   // stop timer LL_TIM_DisableCounter(TIM6); <GPIO LOW>I assume that any of LL_TIM_x call would be in a range of a few nanoseconds, or at least far below

Specifically I'm looking for any app notes on using the USB s/w HAL and drivers on a STM32F7 based processor.

Hello,I want to calculate RAM requirement for one screen with some widgets and images.How can this be done.

Hello All,I am using the usbh_core module to enumerate mass storage devices as a host. I have had it work for plenty of USB 2.0 sticks (not for 3.0), but suddenly, a large batch of USB 2.0 sticks fail to work. After extending all of my delays, this seems to work more consistently, but I am still having issues, especially when inserting an extension cord. I understand that this may be electrical, but if anyone has any good resources that outline exactly what sequence of events occur in the enumeration sequence, that would be very helpful. I have already started looking through the USB 2.0 specification, and I can see some of the critical timing requirements, but it doesn't then actually provide a complete example of exactly what needs to happen in order in terms of control requests to get from the default state to the configured state. To me it seems like the first interrupt happens when DP goes high, then the BSP for the host waits 200ms. Then it pulls the DP line low for 100ms. Then b

Hello,I am using the STM32F7 for USB communication as an MSD host and using the usbh_core.c code and all of it's associated pieces. I have it working consistently on USB 2.0 devices (side note: I needed to insert an enumeration retry for certain non-USB compliant sticks), but it only works on certain USB 3.0 sticks. Also, it seems to error out at different points in the USB enumeration process on these 3.0 sticks, which has become more obvious now that I have implemented the enumeration retry. I am seeing that I occasionally manage to get the device descriptor, but that when I (the host) send the status packets of zero data length to confirm that I got the message, the USB is busy for a short while, indicated by it nacking the message (which is unusual, normally it is not busy at this stage), and then the endpoint stalls. This is all done on endpoint zero. I know that to resolve a stall you typically go through the software reset of the device by pulling the Dp line low for an extended

Hello,I am having an issue connecting to specific USB mass storage devices with my STM32F769 USB host using the BSP. It seems like the USBH_GetDescriptor function never returns for USB flash sticks with a specific HID PID combination. I am considering just putting a limit on the number of retries for this call and presenting the user with a message to try a different USB. If I do go that route, it would be good to know what # of USBs are use-able with STM32F7 with the USBH BSP. Has anyone else experienced this, and if so, how frequently? Thanks,Zach

Hi All,I have been utilizing the STM32F7 to take and store pictures on USB 2.0 sticks.I have repeatedly run into variation across sticks that requires that I modify the MSC Host HAL supplied by STM. The most recent issue that I have run into is getting the disk IO error message at the ff.c unit level. I connected the unit to a signal analyzer and can see that the USB is actually sending me the message below."A Disk Read Error Ocurred. BOOTMGR Is COMPRESSED".This USB stick works every time when connected to my computer, and it is formatted similarly to all of the other USB sticks that do work with my HOST. I've also checked the power line by powering the USB stick externally, and I get the same result. If anyone has any ideas or experience with this, please let me know.I also get a lot of dropped control requests in the enumeration phase. Which is a problem, but I have seen it on other USB sticks as well. And those USB sticks don't exhibit this BOOTMGR issue.