Solved

Greetings,I have been working on the SensorTile.box and specifically the pedometer functionality (worn on wrist) for a while now and I am stuck right now.I want to optimize the algorithm to reliably count steps. To achieve this, I began optimizing it for myself, using Unico GUI, just to see, if it is possible the way I intended.For this purpose, I wrote a datalogger, which I pretty much confirmed to work in the way intended, I cut the accelerometer data using Matlab to verify, that I only use actual walking footage for the regression tool in Unico GUI and in the end got an error average of 0 when I fed new data to the tool. I also checked, if the accelerometer configuration is the same in the logger firmware, as well as in the step counter firmware. The data was collected at 104 Hz and sampled down to 26 Hz.I am forced to work with a full-scale setting of 16g because of other projects running on the same device. Using the C code generator inside Unico GUI, I turned the ucf fi

Thank you for helping.When building with sincos ()'sincos' was not declared in this scopeI get the error.What should I do?#include "math.h" is declared.Thank you.

Hey guys , I am trying to program custom stm32 board using stm32lorwan module using stlink v2 pins. I have configured debugger as followed.Can you tell me debug configuration?>>Connect to remote GDB server , port no 61234>>debug prob , stlink (stlink gdb server)>>Interface , SWD>>Access port, 0-cortex,m0plus>>Reset behaviour , Software system reset>>Debug In low power modes, Enable>>Suspend watchdog counters, DisableBelow is issue that I am having.Error in final launch sequence:Failed to execute MI command:target remote localhost:61234Error message from debugger back end:localhost:61234: The system tried to join a drive to a directory on a joined drive.Failed to execute MI command:target remote localhost:61234Error message from debugger back end:localhost:61234: The system tried to join a drive to a directory on a joined drive.localhost:61234: The system tried to join a drive to a directory on a joined drive.

There is a discrepancy between rev 8 of the datasheet and rev 7 of the reference manual regarding the PLL VCO output range parameter when the PLL is setup in wide VCO frequency mode.In section 7.3.10 of the datasheet, the VCO output range is between 192 and 960 MHz.In section 8.7.12 of the reference manual, the documentation regarding the VCC#VCOSEL bits in the RCC_PLLCFGR register specifies a VCO output range is between 192 and 836 MHz.I am pretty sure that the datasheet description is correct as I haven't encountered any issues configuring the micro with a 960 MHz VCO output, but would like an ST representative to confirm that and an assurance that the reference manual will be amended in future revisions.Cheers,Craig

My sincere apologies for what I am sure is an idiot newbie's error. Thank you everyone for your time.I have STM32CubeIDE and I do not seem to be able to read back values of SFRs (peripheral registers) while in debug. E.g. my code containsHRTIM1_MASTER->MCR = 0xD;In the SFRs panel both before and after this statement is executed, MCR is zero, which is its reset value. Same in pop-up window when I mouse over HRTIM1_MASTER->MCR in the source-code file.I see that e.g. the PLL is being configured correctly, likely in SystemClock_Config(). When I look at PLLSYSN at a breakpoint, it is not at its reset value and is at the value that it is set to in SystemClock_Config().STM32CubeIDE is 1.7.0 and my hardware is STM32G474E-EVAL1. I tried various combinations of settings in Debug Configurations -> Debugger. The debugger correctly connects in each case but my code appears unable to modify the SFR in each case, that is, I do not read back by the debugger the value I set in my user code.

I use the NUCLEO-L4R5ZI Evaluation Board.I use STM32CubeIDE with HAL and gcc.When i activate an Timer Output Channel (I have tried it with Output Compare, PWM, Forced Output) i get a Signal:0 in the gdb after the Timer init (e.g. after call of MX_TIM16_Init())If i don't use Output Channel or when i use an Input Channel for Timer everything works fine.I have this behaviour with all timers.For testing i have disabled the NVIC interrupt but this doesn't fix this strange-error.Is it possible that the timer output calls some function that is not defined ? I use APB1 and APB2 clock with 8 MHz.Thanks for your reply.

I have a version of nfcPoller linked against rfal v1.3 on Linux 5.10.17. This has been working fine with gcc 7.5/glibc 2.31. We recently bumped our toolchain to gcc 9.4/glibc 2.33 and now I get timeouts while reading anything with an NDEF field (or anything other than a header). I'm testing with an card that reports as:xampleRfalPollerActivation[exampleRfalPoller.c:900] INFO NFC-A T2T device activated exampleRfalPollerRun[exampleRfalPoller.c:343] INFO atqa_sak: 004400 exampleRfalPollerRun[exampleRfalPoller.c:366] INFO MIFARE Ultralight UID: 04B89DB22F6680The code that causes this is in st25r3911/rfal_rfst25r3911.c, line 1900: /* Only raise Timeout if NRE is detected with no Rx Start (NRT EMV mode) */ if( (irqs & ST25R3911_IRQ_MASK_NRE) && !(irqs & ST25R3911_IRQ_MASK_RXS) ) { gRFAL.TxRx.status = ERR_TIMEOUT; gRFAL.TxRx.state = RFAL_TXRX_STATE_RX_FAIL; break; }It seems I'm getting the NRE interrupt from the ST25R3911B interrupt register. I don't know how I get thi

I am miniaturizing the STM32F767ZI for a project I am working on and would like to have it function identically to the standard STM32F767ZI. Part of this includes having the ST-Link aspect of the board so we can program it via USB. I have not been able to find any resources detailing how this aspect of the board works beyond the schematic.

Hello,Has anyone ever used the emulated usart provided by ST (AN4457) based on timer and DMA?I need it for transmit, not for reception.In my test, most of the time TX characters are corrupted, sometimes it works.I checked with scope and it appears that the startBit is missing, but the rest of the byte is correct.Here example with the 'a', white trace is the correct one, yellow is the measured trace.It seems that the Start bit is present in the 'calculated' buffer for DMA, but the timer overflow early...Thank you,Pierre

I want to use MOVE and GOTO on some of the steppers at less than 15.25 FS/sec and with finer control than 15.25 FS/sec increments. Is there a way to specify MOVE and GOTO speeds other than by using the MAX_SPEED setting?

For example the custom command `0xAD` is "Read" and `0xCD` is "Fast Read". How should I determine when to use the fast version versus the non-fast version? How does this relate to the `data_rate_flag` in the `request_flags` byte of the RF request packet?Note that when I try using the fast versions of commands using the ST25 demo app, I always get "Tag not found" error using several modern iphone and Android devices. This is true with the `data_rate_flasg` both set and clear. Is this expected? Do I need to do something on either the tag or the phone to enable these fast mode versions of commands?

Clarification: Can I be sure that the case in Errata sheet ES0491 "Device may remain stuck in LPTIM interrupt when entering Stop mode" never occurs for certain LPTIMx if no interrupts within it are used to wake up MCU from Stop mode and disabling of LPTIMx by clearing the ENABLE bit in the LPTIM_CRx register can be used safely?

Hi,i'm using the LIS3DSH to read data in different sampling rates (from 25 up to 1600), but in some cases i notice the first data in Z axe is not correct (some times it's too low or too high, for example, first data is -0.7g (or -1.5) and the rest are around -1g) and this happen with a random sampling rate, somethings happen when i use 100 hz and sometimes when i use 400 or 800. i even changed the anti-aliasing but i had no luck, the only think i can do is to wait until the value is updated in the sensor so i can get the next value at the start.this is a snap of my code to about the state machine configuration this is the initialization section:AccelTxCmd(0x01, LIS3DSH_CTRL_REG3_ADDR); /* registers reset */ AccelTxCmd(0x00, LIS3DSH_CTRL_REG4_ADDR); /* make sure LIS3DSH is off */ AccelTxCmd(0x00, LIS3DSH_CTRL_REG3_ADDR); /* make sure IRQs disabled */ AccelTxCmd(0,LIS3DSH_CS_X_ADDR); /* constant shift for x axis*/ AccelTxCmd(0,LIS3DSH_CS_Y_ADDR);/* constant shift for y axis*/ AccelTxCmd(

Classic CAN configuration as below. when the line "if(HAL_FDCAN_ConfigGlobalFilter(...))" is removed, the CAN messages are received without issue. The transmitted message is set as ID: 0x111 . Confirmed by a CAN bus monitor.Configuration as below:FDCAN_FilterTypeDef sFilterConfig; sFilterConfig.IdType = FDCAN_STANDARD_ID; sFilterConfig.FilterIndex = 0; sFilterConfig.FilterType = FDCAN_FILTER_MASK; sFilterConfig.FilterConfig = FDCAN_FILTER_TO_RXFIFO0; sFilterConfig.FilterID1 = 0x111; sFilterConfig.FilterID2 = 0x7FF;  if(HAL_FDCAN_ConfigFilter(&hfdcan1, &sFilterConfig)!= HAL_OK) { Error_Handler(); } // If comment this one, it works. if(HAL_FDCAN_ConfigGlobalFilter(&hfdcan1, FDCAN_REJECT, FDCAN_REJECT, FDCAN_FILTER_REMOTE, FDCAN_FILTER_REMOTE) != HAL_OK) { Error_Handler(); } if(HAL_FDCAN_Start(&hfdcan1) != HAL_OK) { Error_Handler(); }

I am using OSD32MP1 (based on STM32MP157c) in Production Mode with OpenSTLinux on Core A7 and FreeRTOS on M4. One of the tasks is to timestamp ADC data acquired by M4 at very highspeed, very precisely (think it order of nanosecond to microsecond). Note that only time difference between measurements is important.On-chip RTC is available (it is assigned to A7 but registers are accessible to M4). However the subsecond precision is ~0.003s (PREDIV_S is 255 - See Reference Manual for Detail) so it is not good enough. This, this and this stackoverflow posts led to using DWT_CYCCNT i.e., CPU Cycle Counter to measure the time time difference. Relevant portions of the code is as following: On M4 Side:typedef struct tTimeStamp { uint32_t nCPUFreq; uint32_t nCPUCycles; ... }tTimeStamp; ...   tTimeStamp oTimeStamp;   ...   oTimeStamp.nCPUCycles = DWT->CYCCNT; oTimeStamp.nCPUFreq = HAL_RCC_GetSystemCoreClockFreq();The last 2 statements runs inside the FreeRTOS task

I use the viper06HS to generate +3.3V. i follow the reference design provided by eDesignSuite.When i turn on my system. the viper06HS provide 1.24V do you idea?I attach my schematic

Hello after importing NFC project example (X-NUCLEO-NFC05A1) to chip "STM32L051C8T6" I get an error: "undefined reference to `globalCommProtectCnt'"I made import of the NFC project many times but never get this error. Only difference from other is that now I have the same interrupt function for EXTI0 and EXTI1. So, instead of "void EXTI0_IRQHandler(void){"I have now "void EXTI0_1_IRQHandler(void)".During importing the project I did:add rfal and ST25R3911 library,add path to this library,add USE_LOGGER to symbol,add demo, logger, platform, spi and usart files to Src and Inc folder,add "st25r3911Isr();" into the folder stm32l0xx_it.c,in platform file change "EXTI0_IRQHandler" to "EXTI0_1_IRQHandler" .Thank you for your time and help,Domen

I'm developing a project using the STM32H745 HSEM and found a couple problems with the svd file that make debugging more difficult. My contact with IAR suggested I share my finding with ST to see if a working version can be supplied. 1) The svd file for the M4 core, STM32H7x5_M4.svd has the wrong addresses for the M4 core for its HSEM_ICR, HSEM_IER, HSEM_ISR, and HSEM_MISR register (the M4 core svd file has the addresses for the M7 core for these 4 registers) as they are identical in the M4 and M7 svd file and they should not be identical. Accessing those four registers from the debugger for the M4 is accessing the registers that belong to the M7 core.2) The svd file for the M4 core and for the M7 core have definitions to read all 32 of the HSEM_RLRx registers. The act of the debugger reading those registers through the compiler registers view window results in all of the semaphores that were unused to be locked to which ever core debugger read them first. Given that the debugger cause

The FRAM chip I'm using is cypress.For details, here's a screenshot of my chat with Cypress.Thank you very much.

I am currently experimenting with programming flash memory. I want to figure out how many sectors to erase before writing data into memory. I came across the following snippet uint32_t Flash_Write_Data (uint32_t StartSectorAddress, uint32_t *Data, uint16_t numberofwords) {   static FLASH_EraseInitTypeDef EraseInitStruct; uint32_t SECTORError; int sofar=0;     /* Unlock the Flash to enable the flash control register access *************/ HAL_FLASH_Unlock();   /* Erase the user Flash area */   /* Get the number of sector to erase from 1st sector */   uint32_t StartSector = GetSector(StartSectorAddress); uint32_t EndSectorAddress = StartSectorAddress + numberofwords*4; uint32_t EndSector = GetSector(EndSectorAddress);   /* Fill EraseInit structure*/ EraseInitStruct.TypeErase = FLASH_TYPEERASE_SECTORS; EraseInitStruct.VoltageRange = FLASH_VOLTAGE_RANGE_3; EraseInitStruct.Sector = StartSector; EraseInitStruct.NbSectors = (EndSect

I was going through embedded flash programming documentation of STM32F7 . I came across a term called "data read width". can some one explain this term ?Flash memory single bank organization (256 bits read width)Flash memory dual bank organization (128 bits read width)

ip4_addr_t remote_ip; struct netconn *clientConn; IP4_ADDR(&remote_ip, 192, 168, 0, 11); clientConn = netconn_new(NETCONN_TCP); if(clientConn != NULL) { conn_err = netconn_connect(clientConn, &remote_ip, 8789); if(conn_err == ERR_OK) { netconn_write(clientConn, message, 22, NETCONN_NOFLAG);  } } netconn_close(clientConn); netconn_delete(clientConn); osDelay(10);Ping works, TCP/IP Server also works, but the Client returns ERR_ABRT from the netconnect function.Since the netconn API Server code worked without any problems, I think there will be no problems with hardware and settings.So I'm looking for an example to refer to.I found examples of non-netconn APIs and examples of netconn API Server, but I don't think there are examples of netconn API Clients. (I've seen a few, but they look the same as the code above.)

..

I have a bug in the I2C bus where sometimes a glitch causes the BUSY flag to be setI found that the only ways to clear it is either by SWRST in I2C->CR1 or by resetting in RCC->ABP1RSTR->I2CxRSTRMy question is, is there any difference I should know about between these 2 types of resets or they're exactly the same?Thank you

Hi,Can SPC5-UDESTK JTAG debugger support  SPC584Bxx family ?The databrief specifically mentions SPC56 and SPC57 product family, but not SPC58x. Best regards,Sreejith