Others: hardware and software

Hi, In our schematic, the IC’s SD card pin is connected to the controller pin of the STM32H753VIH6, and the IC’s controller pin is connected to the SD card. Could this connection cause any issues during SD card read and write operations? I have attached the schematic for your reference. https://drive.google.com/drive/folders/1fHC0aW8OWq_DrnzWL8WemED_ALq8BC_0?usp=sharing

I am trying to create a codeplug for my TYT MD-2017 handheld radio.  I have gotten to the point where the radio is listed in Device Manager under "Universal Serial Bus Devices" as "Digital Radio in USB mode" with no error icons.But when I attempt to have CPS talk to the radio it says it is disconnected.  I have been working for several days on this issue with no success.  The radio IS in DFU mode and is seen by Device Manager. I am using GD77 CPS and it's driver.  I have used Zadig to load the WinUSB driver.  Perhaps I should blow all of the GD77 stuff away and use default MD-2017 radio STM software and driver?  If so, is there any installation procedure info for this approach?Any help appreciated!  What additional info is needed?73, WhiteBeard

Title edited to flag that a Blue Pill is being used.Info : [STN32F103c8Tx.cpu] Examination succeedInfo : starting gdb server for STN32F103C8Tx.cpu on 3333Info : Listening on port 3333 for gdb connectionsError:[STM32F103C8Tx.cpul clearing lockup after double fault Polling target STM32F103C8Tx.cpu failed, trying to reexamine Infò : (STM32F103C8Tx.cpu] cortex-M3 rlp1 processor detectedInfo : [STN32F103c8Tx.cpuj target has 6 breakpoints, 4 watchpointsInfo :[STM32F103C8Tx.cpuj Examination succeed Info : accepting 'gdb' connection on tcp/3333Info : device id = 0x20036410Info :flash size = 64 KiBInfo : accepting 'gdb' connection on tcp/3333[STM32F103C8Tx.cpu] halted due to debug-request, current mode: Handler HardFaultXPSR: 0x21000003 pc: 0xfffffffe msp: 0x200008be[STN32F103C8Tx.cpu] halted due to undefined, current mode: Thread XPSR: 0x61000000 pc: 0x2000003a msp: 0x200008b0.Error: Fail reading CTRL/STAT register. Force reconnectInfo : dropped 'gdb' connectionError: Fail reading CTRL/STAT re

Best Microsoft 365 Tenant-to-Tenant (T2T) Migration SolutionPlanning a Microsoft 365 Tenant-to-Tenant (T2T) migration?A successful cross-tenant migration requires detailed assessment, secure identity mapping, phased data transfer, and zero-downtime execution across Microsoft 365 workloads like Exchange Online, Teams, SharePoint, and OneDrive.For organizations undergoing mergers, acquisitions, or tenant consolidation, CloudBik delivers secure, scalable, and enterprise-ready T2T migration services with complete data integrity, permission preservation, and seamless business continuity.

 CAN Bus Error and Reception Not Working – STM8AF5268Hi,I am working with STM8AF5268 and implementing CAN communication using the STM8S/A Standard Peripheral Library.Hardware SetupMCU: STM8AF5268CAN Transceiver: SN65HVD1050CAN Analyzer: Waveshare USB-CAN-FDBaud rate: 100 kbpsTermination120Ω across CANH and CANL at STM8 sideUSB-CAN-FD termination enabledMeasured ≈ 60Ω across CANH–CANLSN65HVD1050 VCC = 5V (verified).Common ground connected between STM8 board and analyzer.Clock Configuration  CLK_DeInit(); CLK_HSIPrescalerConfig(CLK_PRESCALER_HSIDIV1); CLK_PeripheralClockConfig(CLK_PERIPHERAL_CAN, ENABLE);   CAN Initialization  CAN_Init( CAN_MasterCtrl_AllDisabled, CAN_Mode_Normal, CAN_SynJumpWidth_1TimeQuantum, CAN_BitSeg1_11TimeQuantum, CAN_BitSeg2_4TimeQuantum, 10 // Prescaler );   CAN Transmit Code  uint8_t test_data[8] = {0x22,0x33,0x44,0x55,0x56,0x66,0x77,0x66}; CAN_Transmit( 0x321, CAN_Id_Standard, CAN_RTR_Data, 8, test_data );

Title edited to note that this is a clone ST-Link.Using a WeAct mini STM32H723 Core board which seems to be working fine via SWD and a gold STLInkV2 USB stick. (STLinkV2 firmware V2j46S7).Using STM32CubeProgrammer v2.21.0 seems to work ok, connected under SWD, 4kHz, Normal mode, S/w reset, reliable speed, non shared (my usual settings that work with all the other STM32 boards I have).But when I tried the "Full chip erase" (or erase selected sectors), it merely reports erase successful with no errors. However the flash remains unchanged.Using STM32CubeIDE 2.0.0 however, I can successfully download my code to the board (which proves the flash can be erased using the STLinkV2 h/w).Not sure where the problem lies as yet, but have put this issue up here in case others have the same problem with STM32CubeProgrammer.Will post an update here or on the WeAct github site if I make progress to finding why its not working.

Title edited to flag that this relates to a Black Pill & Clone ST-Link After much too much time searching and following advice from for the most part, outdated forum posts I have been unable to resolve my issue with win 11.I have a windows 11 machine (Microsoft Surface) up to date as of 28th January 26.ST Link Utility installed and wokingStCubeProgrammer 2.21.0 and working (apart from not seeing the STLink v2.0 hardware).Both installed as Administrator.Cube Programmer however refuses to acknowledge the STLink v2 when connected even though the driver reports it is working and indeed it shows up in Device Manager. I did try reinstalling and the other common resolve I see is to switch to Shared Enabled in the right hand panel.The odd bit is it just works on my Mac M2 Tahoma without any issues and displays the correct serial numberI would like to get it working on my Surface laptop as well as all my programming is normally done on that machine (XGecu T48).Here are some screen shot

hi all,which firmware to use for STEVAL-STWBXCS1?  datalog2 or ai monitor?regards,

Hola a todos, he estado revisando temas en esta comunidad sobre desarrollo, soluciones técnicas y optimización de sistemas, y me parece muy útil cómo los usuarios comparten conocimientos y experiencias para mejorar el rendimiento y la interacción con diferentes tecnologías.Mientras exploraba otras plataformas digitales y analizaba cómo gestionan la experiencia del usuario y sus servicios online, también encontré fortuna paraguay  y me llamó la atención cómo algunos sitios estructuran su contenido y facilitan la participación de los usuarios.¿Alguien aquí analiza otras plataformas digitales para evaluar su usabilidad o experiencia de usuario? Me gustaría conocer sus opiniones. 

HiI am using the MAX17261 fuel gauge IC and my MCU is STM32U5G7VJTXQ. According to fuel gauge's datasheet, the ALERT pin (active low pin) is asserted under the following conditions:SOC changeSOC crossing minimum or maximum thresholdsVoltage crossing minimum or maximum thresholdsOther configured alert sourcesI have implemented the initialization sequence as recommended in the device’s Software Implementation Guide .Expected BehaviourWhenever an alert condition occurs:The ALERT pin is asserted low.The corresponding bit in the STATUS register is set.The MCU detects the alert via an interrupt (triggered on a rising/falling edge).In the interrupt handler, the STATUS register is read and cleared.Once cleared, the ALERT pin should de-assert, allowing subsequent alerts to generate new interrupts. Observed IssueFor most cases, the behavior works as expected - each SOC change triggers an alert, the MCU receives the interrupt, and the STATUS register is cleared in the interrupt handler.

Hi everyone,I’m currently working on a design to integrate an ESP32-C6 with the ST85MM PLC modem, and I’m hitting a few roadblocks regarding the best hardware architecture and communication flow.To be honest, I'm also a bit confused about the specific differences between the ST8500 and the ST85MM. I’ve been reading documentation for both, and while they seem very similar (same package, similar pinouts), I'm not clear if the host interface or boot behavior differs significantly between them.Crucially, I haven't been able to find any firmware examples or reference code for either chip. I feel like I'm flying blind regarding the actual host communication implementation. If anyone has a code snippet, a repository, or a specific application note that shows how to initialize the modem or handle the host exchange, that would be appreciated.My main goal is to use the ESP32-C6 as the host controller to manage the ST85MM, specifically for loading firmware

Hello everyone,I’m working with an STM32F103C8T6 (Blue Pill) development board and facing an issue while trying to program/debug the MCU using ST-Link V2.Board used:https://robocraze.com/products/stm32f103c8t6-arm-development-boardIssue details:STM32CubeProgrammer / STM32CubeIDE does not consistently detect the targetSometimes shows “No target connected” or fails during connectionTried SWD mode with NRST connectedBOOT0 is set to 0 (Flash mode)Power supplied via USB (5V) and also tested with external 3.3VChecked SWDIO, SWCLK, GND continuityI’m not sure if this is related to board configuration, clock settings, or ST-Link connection parameters. I’d appreciate guidance on:Recommended ST-Link connection settings for STM32F103C8T6Any known issues with Blue Pill boards (pull-ups, reset circuit, USB power, etc.)Whether enabling connect under reset is mandatory for this MCUI’m still getting familiar with the forum and STM32 ecosystem, so apologies if I’ve missed something obvious. Looking forw

Title edited to flag that this relates to a Blue PillI'm trying to connect an STM32-STLink-V2 with three wires via SWD (GND, SCLK,SDIO). Was able to run a firmware upgrade, now V2J46S7.Clicking on Connect gives:15:35:11 : UR connection mode is defined with the HWrst reset mode 15:35:11 : ST-LINK SN : XXXXXXXXXXXXXXXXXXXXXXXXXX 15:35:11 : ST-LINK FW : V2J46S7 15:35:11 : Board : -- 15:35:11 : Voltage : 3.02V 15:35:11 : SWD freq : 4000 KHz 15:35:11 : Connect mode: Normal 15:35:11 : Reset mode : Hardware reset 15:35:11 : Device ID : 0x410 15:35:11 : Revision ID : Rev X 15:35:11 : Debug in Low Power mode is not supported for this device. 15:35:12 : UPLOADING OPTION BYTES DATA ... 15:35:12 : Bank : 0x00 15:35:12 : Address : 0x4002201c 15:35:12 : Size : 8 Bytes 15:35:12 : Bank : 0x01 15:35:12 : Address : 0x1ffff800 15:35:12 : Size : 16 Bytes 15:35:12 : UPLOADING ... 15:35:12 : Size : 1024 Bytes 15:35:12 : Address : 0x8000000 15:35:12 : Read progress: 15:35:13 : Error: Data read failed 15:37:1

Hello,I use a STSAFE-A110 chip on a own board based on STM32 MCU.As I was unable to integrate the STSAFE library provided by ST on my specific fw, I wrote features whom I need as as echo, generate random, retrieve product data, generate host key, retrieve product data partition, read/update NVM.All works fine but when I am unable to read a NVM zone with 'host' access condition. NVV zones with no specific AC are well read. Find below configuration of the NVM of my STSAFE chip.+=======+================+==============+========+==============+========+==============+| Zone | Data segment | Read AC | Read | Update AC | Update | One-way || index | length (bytes) | change right | AC | change right | AC | Counter |+=======+================+==============+========+==============+========+==============+| 0 | 1000 | False | always | True | never | False, 0 || 1 | 700 | True | always | True | always | False, 0 || 2 | 600 | False | host | True | always | False, 0 || 3 | 600 | True | always | True

I have been using Scool together with Keil for years, but last tuesday after I started my PC and a win11 update was installed, I started Scool but got this error: "The PC/SC access cannot be enabled for the reader (driver not installed?) SdtReaderDllLoader Function name:ENABLE_PCSC_ACCESSParameter 1:SCtool Virtual Reader" When trying to update driver in Device Manager, I get code 31. (Well known win error code it seems, and I've tried all sugested solutions from AI and others without success.)My HW card readers also failed, but I managed to find and install newer drivers for them from the internet, so they are running again, only Virtual SCtool drivers I can't find, so the question is, are there any new win11 drivers for SCtool? (My present SCtool Virtual Driver is version 1.1.0.0) Helpdesk sugested I tried to install Scool on a new PC win11 25H2, and drivers worked fine on that. (My present PC is version win11 23H2, and my collegue has exact same PC and win version, where dr

Title edited to correct part number: it is a Geehy APM32F103CBT6 - not an STM32.See this post.Hi everyone,I am working on a project using the STM32F103CB MCU and implementing Standby (low-power) mode in the firmware. Development is done using Arduino IDE v2.3.2. I want the standby mode to be implemented to reduce the current consumption since my device is battery-operated. Problem OverviewThe firmware flow is as follows:On power-up, setup() runs.In loop(), if the reset reason is a power-on reset, the device enters Standby mode.The MCU wakes up from Standby via an interrupt on PA0 (Wakeup Pin).Execution flow and timing are monitored using the Serial Monitor.With the same firmware and library versions, I am observing different behaviour on two PCBs that:Have identical schematicsAre manufactured by the same vendorObserved BehaviorWithout Standby mode implemented, both PCBs behave correctly.With Standby mode enabled:Serial prints before entering Standby appear corr

Hello,I am trying to integrate an STSAFE-A110 chip into my product for keys/data securely storage.The communication with the chip works fine (approved by simple command as echo or generate_random).So I tried to generate a key in a local envelope key slot (first step of command flow in the "Local envelope wrapping/unwrapping" process). For that I queried the STSAFE-A110 to randomly generate a local envelope key in slot #0 and #1, using the STSAFEA_CMD_GENERATE_KEY (0x11) command.> 11 07 00 00 AF C1> 11 07 01 00 B6 19The chip answers OK as status code (correct crc) but I missed to keep data.But when I query the STSAFE-A110 to retrieve local envelope keys information (slot number, presence & key length), I get a key presence flag to 1 but with zeroed key length for the 2 slots.> 14 07 89 09< 00 00 09 02 00 01 00 01 01 00 FC 88status=OK(0x00)slot_nb=2Slot #0:- key_presence=1- key_length=0Slot #1:- key_presence=1- key_length=0How is it possible?Unable afterwards to gene

We have provided SWIM, 5V, and GND connections to the microcontroller for programming and debugging purposes. Is it possible to program the ST8S001J3M3 MCU using the ST-Link V2 or V3 via the 5V, SWIM, and GND connections?Please find the attached reference schematic for your review. Additionally, if there are any recommendations or required corrections in the schematic related to programming connection, kindly let us know. We look forward to your valuable response.

I am performing a thermal analysis with component M24C04-DRMF3TG/K TSSOP8 package.  The datasheet does not contain any of the typical thermal resistance information:  thetaJA, thetaJC_bottom, thetaJC_top.  Is this information available?   Thanks, Andrea

Edited to place the image in the post - for easier viewing.Hello, This is my first time posting. I am trying to find the P/N from the part's marking. If you know it, please let me know.Engraving: GP229Guess: Schottky barrier diode STPS2L60 - 2A, 60V. Is that correct...?If you have any information, please let me know. Thank you.  

See the subject, what t is the standard lead time of the demo board STEVAL-CCA044V1?

Title edited - part number added (not an ST part)After commencing debugging with the JLink, these faults persistently occur after approximately 30 seconds. However, this JLink functions correctly when debugging IAR. What might be the cause?The actual chip used is the STM32F407VET6.JLink keeps disconnecting from CubeIDE for some reason. Debugging frequency SWD=500kThe ST Community moderator has edited the post to comply with the forum language guidelines. The language of the Community is English. For more information, see: ST Community Terms and Conditions

I am trying to get wake-up from HALT mode working on the STM8L151 using the RTC, but without success. I tried two approaches:using the RTC wake-up counter to wake the device after 10 seconds andusing the RTC alarm to wake it up every minute.Neither approach was successful — once the MCU enters sleep, it no longer wakes up. I have the feeling that the issue is not so much directly in main and in the CLK + RTC configuration, but rather in the ISR, IQR handling setup. At this point, however, I’m not sure what to add, what to check, or in which files (stm8_interrupt_vector.c, stm8l15x_itc.c,....).I would be very grateful if someone could advise me on what belongs where, so that I can understand the entire interrupt chain and which additional files in the Inc directory need to be adjusted. In parallel, I also have several related follow-up questions:I am using STM8L15x_StdPeriph_Driver (downloaded from ST as STSW-STM8016 version 1.6.2) — is this version up to date?In the examples, there are

Hi. I am university student and This is my first time using the blackpill for my project . I am having trouble in uploading my code to my blackpill using the stlink. I have make sure that i connected to the correct pin from the stlink to blackpill. However when i pressed uploading in keil it kept saying no stm32 target found. I try to boot to connect to programmer but it kept the same error. I have read others similar problem and tried their solution but it still wouldnt work. Please help me.

I'm running example 03_ECDH from https://github.com/STMicroelectronics/STSAFE-A120_examples/tree/main/Applications/Projects/03_ECDHI modified the example to use ED25519 / Curve25519. I pasted the public key of some key I generated on my PC into the C source. After a power-cycle the asymmetric key info of the A120 looks like this:  ----------------------------------------------------------------------------------------- Global usage limit : 65535 ------+---------------------------------------------------------------------------------- | ASYMMETRIC KEY INFO ------+----------+------------+---------------+------------+---------+------------------- SLOT | PRESENCE | TYPE | EdDSA Variant | Gen Key AC | Sig Gen | Key establishment ------+----------+------------+---------------+------------+---------+------------------- 0x00 | x | NIST_P_256 | None | Forbidden | x | . 0x01 | x | ED25519 | Pure | Free | x | . 0x02 | . | . | None | Free | x | . 0x03 | . | . | None | Free | x