Solved

Posted on June 14, 2017 at 14:43We've designed a product that uses the SPWF01SC + Sagrad antenna (as specified in the datasheet) and would like to consider migrating to the SPWF04SC + Sagrad antenna. Looking at the datasheets however, both modules have only been tested to EN 300 328 v1.9.1 whereas the new Radio Equipment Directive (2014/53/EU) appears to require testing to the EN 300 328 v2.1.1 standards which include a new receiver blocking test.We wish to use the Sagrad antenna with the SPWF04SC and so would need to repeat the EN 300 328 tests to v2.1.1 with our board and the antenna. I noticed that there's an 'etf_mode' configuration variable available but no documentation as to what the engineering test functions are for different values of etf_mode. I've therefore got a few questions about getting our product through the compliance testing:1) Are the etf_modes documented anywhere or can you tell me what they should be set to in order to test the module under E

Posted on June 13, 2017 at 08:51Hello,I am working on a firmware for the STM32F765.This MCU was chosen because of its double precision floating point capabilities.I manged to configure the FPU/Compiler (ARM GCC 5.4) to genertate correct DP native assembly instructions.When debugging, I can verify correct DP calculations.The only thing I cannot manage is to printf results in double precision.I have tried the formatters %f and %lf but on every printf only single precision is printed out (correctly rounded results but with too less digits).I am using newlib speed optimized (NOT nano), but also the lib stdc++ does the same.Has somebody ever seen the printf output in double precision for an embedded ARM Cortex-M7 code with GCC & if yes, how do I get it running ?Thank you in advance,Gahlen

Posted on June 12, 2017 at 17:08Hello to all,I'm new in STM32. I have to use the CAN peripheral on the STM32F091VCTx microcontroller.I'm able to send messages and receive messages in the FIFO0, but if I try to use the FIFO1 the software go down and go in an 'infinite loop' that I don't know what does it means. I have the last version of CubeMx and I use AC6 IDE.Could someone explain to me what is the problem with FIFO1? How I can use it?Thank you very much. 

Posted on June 14, 2017 at 05:44 Hi all, i generated the pwm related source code using CubeMX 4.21 but it dit not work. Target MCU : ST32F746NG The following general PWM code works normally but not with DMA Functions. HAL_TIM_PWM_Start(&htim1,TIM_CHANNEL_1);�? Inoperative code : HAL_TIM_PWM_Start_DMA(&htim1,TIM_CHANNEL_1, (uint32_t *)sendBuff, 16);�? Other MCU (as STM32F407 Discovery board, TIM4_CH1) was targeted and the code was generated with the smae rule (same method, same programs), it worked normally. also, when TIM1 was replaced with TIM3 on ST32F746NG, perfectly operation was performed. I debugged these problems and found a small buf. When using the TIM1 timer in Cube MX, HAL_TIMEx_ConfigBreakDeadTime is generated in the 'MX_TIM1_Init(...' The code to set the Busy flag (htim->State = HAL_TIM_STATE_BUSY;),but it did not exist to reverse the code. So, for functions that do not check the htim-State (READY), it works perfectly fine, but in the

Posted on June 13, 2017 at 14:12Hello,when reading out FLASH_OPTCR1 register I get boot addresses 0x00200000 and 0x00100000 for BOOT_ADD0 and BOOT_ADD1.Now I am doing the option byte unlock procedure and the OPTLOCK-bit in FLASH_OPTCR is cleared to 0.Then I write a new boot address for BOOT_ADD0 and lock the option byte by setting OPTLOCK-bit in FLASH_OPTCR.When reading out FLASH_OPTCR1 I get the new boot address for BOOT_ADD0 (and the old for BOOT_ADD1).But when I reset the MCU, my change to the BOOT_ADD0 is not persistently saved but the original value is retained.What is the right procedure to store the boot addresses persistently?Tank you in advance,Gahlen.#persistent #option-bytes #boot_add0

Posted on May 22, 2017 at 11:43Hello, I'm working with SPC56EL60L3 and SPC5STUDIO v5.0.I need to implement flash array integrity check,as part of the power on self test procedure.I got some sample code from ST application engineering, but I can't get it to work.The odd thing is that, if I try to run the code in debug mode, it works.. When I try to run it outside of the debig mode, I get an unhandled exception.Please find my code below (I made some little changes to the code provided by ST application engineer)./* flash array integrity test */#define PAR_CFLASH_MISR0 0xBFC5FC60#define PAR_CFLASH_MISR1 0x2D32A870#define PAR_CFLASH_MISR2 0xDAF09F36#define PAR_CFLASH_MISR3 0xC0DB86FF#define PAR_CFLASH_MISR4 0x00016014#define FLASH_PSW 0xF9F99999#define UT0_UTE 0x80000000U#define UT0_AID 0x00000001U#define UT0_AIE 0x00000002U#define UT0_AIS 0x00000004Ustatic int32_t CoreFlashIntegrityTest( void ){ int32_t retVal_i32 = CORE_TEST_ERROR; int8_t misrErrCounter_i8 = 0; CFLASH.UT0.R = FLASH_PSW;

Posted on June 01, 2017 at 08:58Hi,I want to use the ST-Link Utility command-line tool for production: flash a BootLoader and the current applicationdo production testsif all is OK - flash the production data (serial-number, timestamp, etc., ~50 bytes)Due to flash size-limitations, production data is located in a specific location, after the BootLoader vector-table (address 0x08000100). BootLoader can grow larger, if needed to upgrade.I want to flash a production-data file via ST-LINK_CLI.exe:ST-LINK_CLI.exe -c SWD -P ProductionData.bin 0x08000100 -Vbut without erasing the BootLoader.The ST-Link Utility GUI has a check-box: Skip Flash Erase.How can I do this via command-line?#st-link_cli #st-link-utility

Posted on June 09, 2017 at 16:29Hello, I am running into a problem while trying to put MCU into a STOP mode. I have tried to comment out all of the 'unnecessary' code but It does not work even if I leave just this in the source:HAL_Init();SystemClock_Config();MX_GPIO_Init();while(1){__HAL_PWR_CLEAR_FLAG(PWR_FLAG_WU); // clear WU FLAG HAL_PWREx_EnableUltraLowPower(); // Enable Ultra low power mode HAL_PWREx_EnableFastWakeUp(); // Enable the fast wake up from Ultra low power mode // Select HSI as system clock source after Wake Up from Stop mode __HAL_RCC_WAKEUPSTOP_CLK_CONFIG(RCC_STOP_WAKEUPCLOCK_HSI); // go to sleep with low power regulator ON // WFI = the device is woken up by any pending interrupt HAL_PWR_EnterSTOPMode(PWR_LOWPOWERREGULATOR_ON, PWR_STOPENTRY_WFI);blink_led();}It seems as if the processor never even entered the sleep mode (or woke up immediately after entering it) because the LED just keeps blinking. This happens even if I disable all interrupt sources using

Posted on June 12, 2017 at 17:51HiI created new STM32F103C8 project. I'm using STD Periph library. STM32F103 works with 8Mhz HSE oscillator. But I did not get 72 Mhz. I'm measuirng PLLCLK frequency with MCO.  RCC_MCOConfig(RCC_MCO_PLLCLK_Div2); I was only 4 Mhz with the MCO. So PLLCLK is 8MhzHow to increase the SYSCLK frequency to 72Mhz?I attached the project file. Thanks#frequency #stm32f103 #72mhz #sysclk

Posted on June 12, 2017 at 17:12Hello,I tried my LCD with parallel FMC-16bit on the NucleoL496 kit. All is working so far so good.Now I working on my board and this is a L471 processor.The problem is that it crashes when I try to writing to FMC(0x60000000). It goes directly in hardfault.Only FMC is activated and the difference between the two project are the number of pin (100 vs 144) and the model (L471 vs L496)An idea what happens?Pierre

Posted on June 12, 2017 at 11:17Hi everyone,In my project, I need to generate a PWM with some parameters which need to be changed during runtime.Here are the parameters : - Duty cycle- Period- Voltage level (I think this one is not possible... maybe there is an alternative way you may know?)First of all, I generate the PWM without troubles.I am able to change the duty cycle on runtime using __HAL_TIM_SET_COMPARE(__HANDLE__, __CHANNEL__, __COMPARE__) macroNow, it is possible to change the period while runtime using this kind of macro? I can't find it.Thank you very much,Marc#pwm #timer

Posted on June 11, 2017 at 12:05Hello allI have an eBay ST-LINK V2 with an STM8S003F3P development board. Following the tutorial I have managed to get the project compiled without errors and set up the debugger options as instructed with the SWIM ST-LINK option. However when I attempt to start the debugger I get the Target Selection dialog which is fine but then the following error.Starting debug session... -> Emulator reset (usb://usb)...  ** Connection error (usb://usb): gdi-error [40201]: can't access configuration database -> Failed to connect target.The tutorial did not mention I had to include the header file so is there a database that I am supposed to find. Anybody know where it is or what it is called?#stm8s003f3p #st-link-v2

Posted on June 09, 2017 at 13:42I have started development with the AS3992, which has been bought by ST. I have also bought the AS3992 MICRO demo kit to get a feel of what the device can do. I need some support compiling and locating the origional code, to do some testing in direct mode. I plan to use the 3993 device for the product I am deeveloping.https://community.st.com/tags♯/?tags=uhf%20rfid%20reader%20st25ru3993Please advise.#uhf-rfid-reader-st25ru3993

Posted on May 17, 2017 at 22:47I need a datasheet for the spc58ec80e3.#spc58

Posted on June 03, 2017 at 01:44In TN0018 'Surface mounting guidelines for MEMS sensors in an LGA package', on Page 5 it offers different guidance on land pad dimensions depending on whether the 'LGA pin spacing' is (a) greater than 0.2 mm or (b) equal to or less than 0.2 mm. If (a), it says oversize the land pads by 0.1 mm in both length and width; if (b), the land pads are not oversized.QUESTION 1: Does the phrase 'LGA pin spacing' mean open space between pins or pin pitch? I don't think I've seen a part with 0.2 mm pitch, to say nothing of less than that; the smallest microBGA parts I've seen have a pitch more than 0.2 mm. Anyway, the LMS9DS1 has a pitch of 0.43 mm, but its open space between pins is exactly 0.2 mm. Do we go by pitch, and oversize the land pads by 0.1 mm in both length and width? Or do we go by open space between pins, and not oversize the land pads? Or...?QUESTION 2: In this thread -- <LINK NO LON

Posted on February 05, 2017 at 08:44using CubeMX V4.18.0. and uV5,  stole parts from the '091 examplesI can see the ACK from the slave device, on the Oscilloscopebuttrying to send 0x68, 0x0E,0x00,0x00 as a packetit sends 1 byte the 0x68 and stops.while(HAL_I2C_Master_Transmit(&hiic2_Rtc, (uint16_t)I2C_ADDRESS, (uint8_t*)data, TXBUFFERSIZE, 10) != HAL_OK) exits with HAL_I2C_ERROR_AF  ,  after just one byteI am probably doing something wrong.mbed works properly on the port.what s the best advice for running the IIC port on a STM32F091 ?

Posted on May 12, 2017 at 11:11 Hi all, I'm trying to use the SPWF04SA module in SPI mode. So far I've managed to put it in such a mode either with the AT commands or just by pulling high the IRQ line, however it seems to be stuck without any response and only very few times it recovers by starting to blink the LEDs and toggling the IRQ line. Which is the correct configuration and startup procedure? Here are mine: - SPI CLK polarity low, first edge triggered. NO PULL on this line. - No pull on both MISO and MOSI. - Pull-up on IRQ line and CS from the very beginning. - Startup: 3.15V supply goes high, RST goes low for 100 ms, then goes back high. After startup is done, the IRQ is triggered by the module at least once, but then it remains low most of the time with no LEDs blinking. Sometimes it recovers after a while with LEDs blinking and IRQ toggling. I would really appreaciate any help, for the documentation is really lacking of details about this. Thank you, Daniele #spwf

Posted on May 18, 2017 at 11:33Hi,Is there a way to disable the ''Flash sectors protection'' through USB (DfuSeDemo/dfu-util/...)?It can be done using the STM32 ST-LINK Utility,by going to Target > Option Bytes, and unselecting all the sectors under ''Flash sectors protection''and pressing Apply.Note that the sectors were Read/Write Protected.As described in the last post on this topic: https://community.st.com/message/60940 I would have to put the chip protection level to 1 and switch it back to 0 while changing the PCROP bit.How would i go about doing this through the dfu-protocol or is this not possible.Regards,Michiel

Posted on May 21, 2017 at 00:24Hi all!I'm trying to read/write data to an SD card from my STM32F072 Discovery board.I configure SPI1 on CubeMx and the FatFs middleware. I've written the user_dsikio.c and the Input-Output functions based on the STM32F072 Eval board, but I can't make it work.When I try to open a file, or format the SD, the microcontroller stops there and finishes at the Default_Handler, as I can see with the debugger.Where can I find an example of a STM32F072 Discovery board with an SD?Can anyone help me?Thanks!!!!!!!!!!#sd-card #stm32f072 #stm32f072-discovery

Posted on June 07, 2017 at 22:50Hi,I tried this code :void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef *htim){/* USER CODE BEGIN Callback 1 */    if (htim->Instance == TIM2) {    HAL_GPIO_TogglePin(GPIOA, GPIO_PIN_5);        __HAL_TIM_SET_PRESCALER(&htim2, 30000);  }/* USER CODE END Callback 1 */}but gave me :../Src/main.c(286): error:  &sharp20: identifier '__PRESC__' is undefined../Src/main.c(286): error:  &sharp20: identifier '__HANDLE__' is undefinedBut if I tried :__HAL_TIM_SET_COUNTER or others macro, there was no error...Any clue on how to resolve this ...Thank you#__hal_tim_set_prescaler

Posted on June 08, 2017 at 16:23Dear SupportI am using the M24SR64 on a Mikroe 1726 board. The board has NO power to it and we are using the RFID energy to power the chip. We wrote an NFC app for a smart phone and the App and everything works OK most the time but what we are finding that 1 in 20 - 30 times the M24SR64 chip locks out and the system data and memory data can not be read and we are unable to write to the chip afterwards. We find the only way to recover is simply use the ST25 NFC App to read and then write any characters back. is it possible you can advise us data messages and commands you use in the ST25 NFC App?We found the problem appears to exist with Android 5.Also are you aware of this problem?Thanks

Posted on May 26, 2017 at 10:21Hello I'm working with SPC56EL60L3, and SPC5STUDIO v5.0.I need to have a section of code running from RAM, a function more specifically.How do I do this in SPC5Studio? I guess I need to add a directive like:__attribute__ ((section ('.ram_code')))before the function declaration, where ram_code is the defined in the linker script.Could you, please, provide an example?Thank you.RegardsAlessandro#spc5studio #ram #code #spc56

Posted on June 06, 2017 at 09:51Hi!I am using the SPWF04S module configured in MiniAP mode. I've created a file in RAM memory using the AT+S.FSC command.I am reading the file using the AT+S.FSP command. After about 450-500 successfully readings, the module responds with Low Memory and resets itself (watchdog) after 20 seconds. Sometimes the respond is 'WIND:8:Hard Fault:ConUart:0002b290:20030000:07fd5003:08023588:47938cc4:fb3f49b6:080bb3e0:21000000' instead of Low Memory.The same happens if I am creating the file using POST messages to the module. In this case I have the following steps:1. I send this from client PC: curl -i -X POST -H 'Content-type: multipart/form-data' -F 'data=@FileSetX' 172.10.20.12. I read the module using 'AT+S.FSP=FileSetX,,'. The content of the file are read correctly.3. Repeat 1 and 2. After about 400-500 success, the module is blocked (Low Memory / Hard Fault or maybe something else...)Thanks.

Posted on May 30, 2017 at 13:35Hello All, I am working on SPC560B54L5 board using SPC5studio version 5.2.3.I am trying to implement the checksum calculation on the C-flash memory in my application. In order to implement checksum I am making use of ''pCheckSum( &ssdConfig, c_dest, c_size, &c_sum, (tpfNullCallback)NULL_CALLBACK);''  API of the flash driver component. In the ''SPC560Bxx_RLA Flash Test Application for Discovery''  I have found that after calculating the checksum, sum value is compared to 0x000000000.My concern is that, in my application the calculated checksum is not equal to zero. Please explain what is the need for comparing the calculated value to Zero in Flash test application. (Is it due to the pre-calculated value of checksum is equal to zero).Whereas ''Standard software driver for C90LC Flash'' document clearly describes the sum value will lie in 0x00000000 - 0xFFFFFFFF range.Kindly explain the need for comparison of sum with 0x00000000 in th

Posted on April 28, 2017 at 23:16I want to run some Chibios demos in SPC5Studio. When you downoad the latest ChibiOS distro it tells you many of the files called out in the ChibiOS demos are NOT in the ChibiOS distro, they have to be requested from ST. Can somene tell me which of the many ST SW suites I have to request to get the ST files compatible with ChibiOS? Thanks., I want to run some Chibios demos in SPC5Studio. When you downoad the latest ChibiOS distro it tells you many of the files called out in the ChibiOS demos are NOT in the ChibiOS distro, they have to be requested from ST. Can somene tell me which of the many ST SW suites I have to request to get the ST files compatible with ChibiOS? Thanks.#spc5studio