Others: hardware and software

test

Hi everyone, I saw that ST give a C driver for STUSB4500 and even have a binary to test the 4531 on some boards.Can ST provide a C library for this chip ? Thanks.

I'm designing a USB-C charging circuit for a battery-powered device using the STUSB4531 for PD negotiation alongside a BQ25792 buck-boost battery charger. The BQ25792 handles the full VBUS power path internally (inrush limiting, reverse current protection, OVP, and dead battery support), so I'm trying to understand whether the external P-FET that STUSB4531 normally drives is still required. Specifically: 1. Can the GATE pin be left NC or tied off without affecting CC detection and PD negotiation? Or does the IC require a valid FET load on GATE to operate correctly?2. If the GATE pin must drive something, would it be acceptable to connect GATE to the BQ25792's CE (charge enable) pin instead of a FET gate — effectively using it as a charger enable signal rather than a loadswitch?3. Dead battery / no battery scenario: I need the system to power up from VBUS even when the battery is absent or fully depleted. The BQ25792 already supports dead battery mode on its own. If the external FE

Hi,We are using the ST Micro Devices SLVU2.8‑8A1 TVS array on the primary side of the Ethernet connector for ESD protection in a 1000BASE‑T Ethernet design.It is observed that when the SLVU2.8‑8A1 is mounted, the 1G Ethernet link reports FCS errors with ~100-metre cables, whilst shorter-length cables work error-free.When the device is removed, the Ethernet link becomes fully stable and error‑free on the same hardware with longer length cables.Ideally the device should not interact with the Ethernet data being transmitted. Please check how the device can interact with normal datalink propagation. The problem is observed in designs with PHYs from two leading manufacturers. Attaching the images of the device as well.Thanks & Regards,Rohit Dixit

Hi everyone,I'm currently working on a project involving a stepper motor controlled by an STM32 microcontroller, and I wanted to share a quick overview of how I set it up using STM32CubeMX.Hardware:STM32F103C8T6 (Blue Pill)Stepper Motor (28BYJ-48)Stepper Motor Driver (ULN2003 or A4988)Steps I Followed:STM32CubeMX Configuration:Created a new project for my STM32 board.Enabled GPIO outputs for the control pins connected to the driver.Set up a Timer for delays or PWM (if using A4988).Generated code with HAL libraries.Coding in STM32CubeIDE:Wrote a simple function to send step pulses and direction signals.For A4988, I toggled the STEP pin with a delay and used the DIR pin to control direction.For ULN2003, I used a stepping sequence on 4 GPIO pins.Testing:Got the motor running with basic forward and reverse motion.Planning to implement acceleration profiles and microstepping next.Let me know if anyone needs sample code or has tips on improving the motion control. Also, is anyone using FreeR

The ST1S06xx datasheet (https://www.st.com/resource/en/datasheet/st1s06.pdf) contains an error: Figure 10 "Input voltave vs output voltage" has the axes labels swapped:A correct version of the Input voltage vs output voltage characteristic can be found in figure 7 of Application Note 2371 https://www.st.com/resource/en/application_note/an2371-st1s06-high-frequency-synchronous-buck-converter-stmicroelectronics.pdf : The datasheet is also missing details on a crucial characteristic: output voltage vs current. In my circuit I have R1=18k, R2=5.6k. Nominal output should be Vout = 0.8V*(1+18/5.6). With a load of 600mA I measure Vout = 3.36V; increasing the load to 800mA, Vout = 3.16V. Another crucial characteristic that's missing detail is dropout voltage: the only indication is figure 11 mentioned above, which suggest for a 1.2V / 1.5A output the dropout voltage is approx 1.1V, but there's no indication of how that changes with input/output voltage or current.

Is Cosmic license delivery service still working ?I submit the request, but I didn't get any answer! 

Are the pin configurations for TSV321RAILT and TSV321RILT exactly the same?I'm having trouble finding this information in the datasheet.

Hello Everyone,I am attempting to debug code on the STM32 Blue Pill board. The project compiles successfully, but when I start a debug session, it fails with the message “Launch debugging failed,” along with additional error details shown below. I would appreciate any guidance on resolving this issue.Note: I am using an ST-Link V2 programmer (A2020 version).Wiring is done correctly checked multiple time.I had doubts about the Debugger configurations. Are there any other settings must be modifiable, or any other ways arethere?" Error in final launch sequence:Failed to start GDB serverFailed to start GDB serverError in initializing ST-LINK device.Reason: (18) Could not verify ST device! Abort connection."

Good morning everyone, I have this Mini STM32F103C8T6 CH340 board which supposedly has the original chip (photo), I configure it as suggested in a post I saw here but it gives an error (attachment).Does anyone have a solution?Edited to place Images in-line for easier viewing:  

Hello,I am currently developing a presence detection system using the STHS34PF80 sensor. My goal is to detect a person at a distance of approximately 2.5 meters.I am experiencing an issue regarding stationary subjects. While the sensor successfully detects a person entering the Field of View (FoV) at 2.5m, the TPRESENCE signal (read from TPRESENCE_L and TPRESENCE_H) gradually decreases over time if the person remains completely still. Eventually, the value falls below the threshold, and the sensor no longer reports "Presence."Please refer to the attached graph below.

Title edited to flag that it's a clone ST-LinkI’m trying to flash an STM32G431CB on a B-G431B-ESC1 ESC board for a reaction wheel-based attitude control system. So there’s three ESCs each. For every one, I soldered 4 wires to the J4 SWD pads (SWDIO, SWCLK, 3V3, GND) and connected them to an ST-LINK V2. Just to clarify on my end, the wire colors don’t really follow any convention, so the red wire isn’t 3V~ I followed the schematic image where the actual pinout left to right is SWDIO, SWCLK, 3V, GND, which matches the correct J4 order. STM32CubeProgrammer is not detecting the chip. The error reads: UR connection mode is defined with the SWrst reset mode; but I am getting a target voltage at 3.25V (power is fine), but SWDIO/SWCLK don’t seem to be communicating. All target fields show dashes.I’ve confirmed that the wiring order matches ST-LINK V2 pinout, tried different connection speeds in CubeProgrammer, change the stlink v2 pinout, even changed my ESC (!) and I have the same i

i couldn't find the datasheet here. Does anyone have the datasheet for this part# STHV1600L? or STHV1600?

Buenos días a todos, Me presento, soy Hugo un alumno de universidad que está preparando su TFG, acerca de la IA preventiva, para ello me gustaría hacer una demostración y es ahí donde me surgen las dudas, que ojalá me ayuden a resolverlas. Quiero instalar distintos sensores (medir vibraciones, consumo de energía y temperaturas) en plataformas elevables de construcción, para que pueda recoger en directo métricas recogidas por estos sensores y volcar estos datos en una base de datos para trabajar más tarde con ellos, mis preguntas surgen desde qué sensores me recomendaríais comprar (entendiendo que soy un alumno y tampoco tengo el presupuesto de una empresa), como puedo instalarlos correctamente y como puedo hacer para que según va recogiendo datos en directo, poder volcar estos mismos en una base de datos. Agradecería cualquier ayuda, muchas gracias de antemano.Un saludo, Hugo G.Google translation:Good morning everyone, I'm Hugo, a university student preparing my final year pr

Hello,I'm working on a project to increase the detection range of the STHS34PF80. During my tests with different LPF and Threshold settings, I noticed that TPRESENCE_L often drops to 0 and stops updating entirely.It feels like the internal algorithm is "absorbing" the signal or the filter is too aggressive.Does changing LPF settings require a specific reset sequence to prevent this?Are there known limitations when trying to push the range beyond 2.2m using software parameters?Any help would be greatly appreciated. Thanks!

 Hello,We are currently looking for a 2-terminal active (ideal) bypass diode that can be directly soldered to the ribbons inside our solar modules. Please note that the component must be able to withstand the lamination process.We previously evaluated the SM74611KTTR; however, our new module design requires a higher current rating of approximately 25A or more.Could you please recommend any alternative products that meet the following specifications?Forward Current: 25A – 30AReverse Voltage: 20V – 40VMaximum Thickness: 2.0 mm or lessRequirement: Must be an active/MOSFET-based (smart bypass) diode to minimize heat generation.Thank you for your time and review. We look forward to your recommendation 

We are pursuing UL3141 for Power Control Systems (PCS), this includes UL991 which is the Standard for Tests for Safety-Related Controls Employing Solid-State Devices, and it requires a critical component analysis.In our particular design, the STPM34 is a critical component used in our PCS. To avoid hardware redesign to add sensor redundancy or a self-test circuit, we can use a "computational method" by considering component FIT data.Typically we expect FIT data on the order of 10^6 or 10^9 hours.Do you have FIT data available for the STPM34, that is measured to an applicable standard?Does STMicro have critical component analysis data available for the STPM34?Does STMicro have internal resources to support customers with critical component analysis?Kind regards,Bryn

I want to become a person who can develop MCU based products. How can I improve on my skill. How can i Achieve my goal? Eg. Currently I have been given AVAS system development task. 

We have 2 nos of STEVAL Drone 02. 1)We assembled correctly the motors CW & CCW 2) Propellers are also correctly assembled. We are using STBLE Drone androidapp. We are facing same problem for both the units.Propellers rotates in proper direction  but its not lifting up.instead it lifts slightly 25 cm above ground & then starts rotating around itself & moves horizontally uncontrolled. Then we have to stop it.VIDEO of Drone behaviour attached.Please suggest RegardsShirish 

Hey guys.. new here.. I’m building a small STM32F103 board to read temp and pressure sensors… prototype works fine on breadboard but now want to make PCB..Problem is.. I tried to route VCC and GND planes in KiCad, but when I refill copper zones some areas near STM32 pins stay unconnected.. DRC shows some warnings for vias too..Should I place more vias near STM32 or maybe change copper zone settings?? Also decoupling caps.. some are far from pins because of routing.. will that cause issues?? I’m little worried about noise and stability.. never made 2-layer pcb with stm32 before..

I am working on a project that uses the ST67W611 for cloud connectivity, but I am experiencing some issues when trying to connect to AWS IoT Core.Note: The NCP is already flashed with the T01 binary.The AWS endpoint is correct — for the sake of this question, let’s assume it is:xxxxxx-something.amazonaws.com.What WorksBroker: test.mosquitto.orgI am able to publish data to the broker and receive data from it when using test.mosquitto.org.However, I am now trying to get it working so that our custom device can connect to AWS IoT Core.MQTT Configuration(This is my current MQTT configuration.) #define MQTT_BROKER "xxxxxxxxxxxxxxxxxxus-west-1.amazonaws.com" #define MQTT_PORT 8883 #define MQTT_CLIENT_ID "Thing01" #define MQTT_USE_TLS 4 #define MQTT_KEEPALIVE_S 60 static const char s_aws_ca_cert[] = "-----BEGIN CERTIFICATE-----\r\n" "Conten........\r\n" "Conten........\r\n" ..... "-----END CERTIFICATE-----\r\n" static const char s_aws_client_cert[] = "-----BEGIN CERTIFICATE---

Hi,I am doing the evaluation of ST33KTPM2X-i2c on my Linux v6.1.70 embedded system.According to the 'Enabling TPM support in the Linux kernel from the version 6.1' from an5714-integrating-the-stsafetpm-trusted-platform-modules-with-linux-stmicroelectronics.pdf, :From the version 6.1, the TPM support can be enabled with a short method, which is available in the [TCG-TPM-I2C-DRV] github in Section 1: Open-source software resources.I understand the driver is available within the Linux v6.1 already. What I need to to is to enable the tpm_tis_i2c.c and add device node into my DTB. Done!But when I looked into the source code of Linux v6.1 (mainline or https://github.com/raspberrypi/linux/blob/rpi-6.1.y/drivers/char/tpm/tpm_tis_i2c.c#L385), the driver is not presented there - where I expect something like: .compatible = "st,st33ktpm-i2c". Could you help me?

ST10F276Z5T3 DC is newer than last shipment date.Last time Delivery 2022-03-11label DC is 23+

Hello everyone,I want to share some issues and their fixes when migrating the .ioc file that was created for the Riverdi 10" STM32 display with template 4.1.0 to the newer version of CubeMX ver 1.16.0, STM32Cube FW_H7 V1.13.0.My environment is:Target: Riverdi STM32 10" Display RVT101HVSNWC00-B TouchGFX 4.26.0, CubeMX ver 1.16.0 STM32Cube FW_H7 V1.13.0, CubeIDE ver. 1.19.01. The build in CubeIDE fails with multiple errors searching for the "cmsis_os2.h" file.     Fix: Include paths are missing. Manually add the following include paths in both the Include Paths section of MCU GCC Compiler and MCU G++ Compiler (In CubeIDE)     (Riverdi_101STM32H7_1_6_CM7-->Properties-->C/C++ Build--> Settings-->MCU GCC Compiler-->Include Paths)            The paths to be included are:     " ../../../Drivers/CMSIS/RTOS2/Include" and  "../../../Drivers/CM

Hi friends, Again I have come with a problem. Please see my code. PWM works as usual. But it is made to stop by resetting PC3 bit, PWM does not stop rather, it behaves randomly. Sometimes the PWM channels are driven high, driven low or PWM pulse is there. Many modifications has turned futile. Hence I seek your support. Regards ankhola Main,c /* MAIN.C file * * Copyright (c) 2002-2005 STMicroelectronics */ #include "stm8s.h" #include "ccp.h" void inv_on(void); void inv_off(void); void sw_state(void); unsigned int pwm_duty1 = 40; unsigned int pwm_duty2 = 50; unsigned int i=0; unsigned int duty; unsigned char toggle=0; unsigned char off_state; unsigned char on_state; unsigned const int table []= {0, 16, 32, 48, 64, 80, 96, 112, 127, 143, 159, 174, 190, 205, 220, 235, 250, 264, 279, 293, 307, 321, 335, 349, 362, 375, 388, 400, 413, 425, 437, 448, 460, 471, 481, 492, 502, 511, 521, 530, 539, 547, 555, 563, 570, 577, 584, 590, 596, 602, 607, 612, 616, 620, 623, 627, 630, 632, 634