Interface and connectivity ICs

Hi,The ST4485EB IC mentions that it needs a 3v3 supply. How can we ensure that the A and B lines interoperate with other RS485 devices working at a 5V logic level as the datasheet mentions . Should I just provide 5V supply to this chip so that it interoperates? Will that be ok as the datasheet says the max Vcc is rated to be 7V.Regards,Nilav   

i have buy VNH5180A-E powersso-36 tp pakage some 20pcs but i check measurement not as per datasheetcan you let me knowdimension A /a2 = 2.53 mm  as per our  ( as per datasheet is 2.15-2.47mm)dimension H = 9.91 mm as per our ( as per datasheet is 10.10-10.5 mm)dimension D = 10.50 as per our ( as per datasheet is 10.10-10.50 mm )  

Where can I find documentation on the BLE attribute handle offsets? I was adapting code from the sensor demo for the BLE NRG 2 and am trying to understand the "aci_gatt_attribute_modified_event" callback. Through observation and experimentation I found that adding 1 to the attribute handle identifies write characteristic events from the BLE client and adding 2 to the handle identifies characteristic notifications being enabled or disabled. I haven't seen any description of this behavior in the BLE programming guide, but I would like to know all the available offsets and what they are for.

Hello everyone,I am currently working on a project where we are trying to send random data from an STM32 Nucleo-F429ZI to a Raspberry Pi 4 over the I2C interface. We have encountered an issue where the I2C address is not detected on the Raspberry Pi when we run the command "i2cdetect -y 1".Here is the sequence of steps we've taken:We are using STM32Cube IDE to create the code and flash the program to the Nucleo board.In STM32Cube IDE, we have configured the I2C settings. Specifically, we have enabled the I2C interface and set the primary slave address.We generated the code and flashed it to the STM32 Nucleo board.In raspberry pi , we flashed the code for receive data from the STM32 nucleo also.However, we still face the issue where the Raspberry Pi doesn't detect the I2C address.We have also tried checking the pull-up configuration. We pulled up the I2C pins on the Raspberry Pi to 3.3V and connected them to the STM32 Nucleo board, but this approach did not work. Interestingly, when we

I am wondering what the logic voltage is for the I/O pins on the STUSB4500L. Under operating conditions they are listed as 0V to 4.5V, but the example circuit shows I2C pullup resistors to 3.3V. Is it safe to connect these I/O pins directly to a 3.3V logic level microcontroller, or will that require a level shifter?

Hi All,I am using BlueNRG in my product for BLE communication. Able to detect peripheral devices in our central- Mobile Application and works fine but issue with Multiple peripheral device access where need to connect every time with specific peripheral device when need to access it.Issue:# Central Mobile App discovered multiple peripheral devices# Configured devices one by one Mobile App.# But during access, every time required to connect again to access the peripheral device.As per BLE spec, we can access multiple peripheral device on single central device without connect again and again with peripheral device.Please provide guidance for the same .Thanks,Anil       

Hi! We have designed our own custom board based on the X-NUCLEO-BNRG2A1, we bought the BLENRG-M2SP module some months ago. We discovered based on this, that these are coming empty (not flashed). We have flashed them using all the available images possible, for example the ones indicated in here, or the ones that you can download when reading UM3051 (DTM_Full.bin and/or DTM_LLOnly.bin). When we run our code in the X-NUCLEO-BNRG2A1 (together with the STM32 Nucleo-64 development board with STM32L476RG MCU --> the same MCU we have in our custom PCB), everything works properly. However, when we run our code in our PCB, the first frame we receive (SPI) after a BlueNRG-2 reset (RST line) is: {0x04,0xff,0x03,0x01,0x00,0x05} Note the last byte, which should be 0x01. After that, when we try to communicate again for example sending a reset command or asking for the fw and hw version, both end up in TIMEOUT. The only difference we have in our PCB with respect to th

Hi,I am trying to use S2-LP DK with a Nucleo + S2-LP Shield. I tried several combinations (4 computers (Windows 10), 6 Nucleo Boards (STML053 and STML152) and 4 S2-LP shields, S2-LP DK V1.2.0, 1.3.0, 1.3.2), I always get the error that I have the wrong firmware version although the S2-LP DK tool flashed it successfully. I am out of ideas. Can anyone help?

Android R can't get LSM6DSM HAL Accelerometer/Gyroscope data on iMX8MM board.following the steps as mentioned :1.copied the hal source code into hardware/STMicroelectronics/SensorHAL_IIO.2.Looking to the Documentation folder i have made the changes accordingly.First i have tried using the Selftest tool manual but lots of error get generated during the compilation and i don't see any binary as STSensor_selftest in the provided path as:/system/bin/STSensor_selftest.3.Then i tried for the Factory calibration option and modified the source code as mentioned Those modifications will touch:- device/{vendor}/{product}/BoardConfig.mk (modification)- device/{vendor}/{product}/init.{board}.rc (modification)- device/{vendor}/{product}/sepolicy/file.te (modification)- device/{vendor}/{product}/sepolicy/file_contexts (modification)- device/{vendor}/{product}/sepolicy/STSensors.te (add)but during compilation of AOSP i am getting the error regarding the sepoilcy changes as:[

After closing serial port, when i re-open serial port with the updated baud rate, I'm getting an error:  Failed to execute MI command:          -data-disassemble -s 4294967228 -e 4294967330 -- 3          Error message from debugger back end:          Cannot access memory at address 0xffffffbc 

Hello Everyone,I am looking for RF Chipset which is certified to be used in Automotive products with ASIL-D certified and other certification if any. Please let me know, which are the series of RF chipsets which I can refer to .Thanks in advanceRgdsShankar

Hello,I have created a pcb using RGB 8x8 leds. I'll refer to the RGB 8x8 LEDs as 'modules'. These modules are controlled via the LED2472GBTR. There are 10 modules, thus, ten LED2472GBTR's.This is all then controlled via a PIC18F87K22 MCU.At present, I can display whatever ASCII character I wish. That's not the issue. What I would like to ask about is the ROE/GOE/BOE output enables.My issue: When applying all three OE channels, if the ASCII character to be displayed upon a module has more than a few 'dots' (or RGB LED's) to light, the colour red seems to dominate. And I don't know why?Context for my issue:I have tried ROE = LOW, then GOE = LOW, then BOW = LOW without delay. Same issue persists.I tried the above with a small 1ms delay. Same issue persists.The modules are powered via 5V and the LED2472GBTR's are also 5V powered, as is the MCU. I thought, as an experiment, maybe the LED2472GBTR would work better with 3V. SO, set up level shifters and powered the LED2472GBTR's with 3V3. Sam

Hello everyone. I'm facing a issue when I try to use CODED_PHY instead 1M_PHY. When I start a GAP_GENERAL_DISCOVERY_PROC, the stack returns: 0xD1 (BLE_STATUS_INVALID_SCAN_CONFIGURATION).Could anyone help me? The scan configuration is (return 0x00 - OK):    ret = aci_gap_set_scan_configuration(DUPLICATE_FILTER_ENABLED, SCAN_ACCEPT_ALL, LE_CODED_PHY_BIT, PASSIVE_SCAN, SCAN_INTERVAL, SCAN_WINDOW); PRINTF("Scan configuration for LE_CODED_PHY: 0x%02X\n", ret);   and the start procedure function returns 0xD1 (NOK). variable phy = LE_CODED_PHY.    ret = aci_gap_start_procedure(GAP_GENERAL_DISCOVERY_PROC, phy, SCAN_DURATION/10, 0); if(ret){ PRINTF("start general discovery failed; err: %02X", ret); }   When using 1M_PHY it works well. I can't see more details about the functions and error troubleshooting in the documentation, so I'm looking help here.Best Regards,Leonardo

Hello,I have implemented test functions gci_le_transmitter_test() and hci_le_receiver_test() in our firmware for tests in lab. We have setup a test bench with one hand our product and on the other hand a STEVAL-IDB008V2 driven by BNRGUI software.We have been able to test transmission with our board with success. Unfortunately, it is not the case in reception mode where we always get a nb_packet received = 0. We have checked our STEVAL board with a Nordic tool to make sure there was transmission from the eval board, which is the case.I can't figure out why I have this issue (probably configuration or whatever). Please find below, some lines of my code if you have any idea.SYS_Status_e status = SYS_OK;char output[64] = {0};tBleStatus temp = BLE_STATUS_SUCCESS; temp = hci_le_test_end(&nb_packet);  //nb_packet is a global variable with the following declaration: uint16_t nb_packet = 0; if(temp)   //we always get BLE_STATUS_SUCCESS{status = SYS_ERROR;gCLI_M

Using the STEVAL-LNBH06 I am not able to achieve 93% efficiency as stated in the data sheet. Please advise why this might be.inout voltage: 12Vload: 43ohm power resistor for each channel (draw 420mA per channel)measured input power: 20.4Woutput power: 17.2Wefficiency: 85%

Hello Everyone!I think it's a weird question, however, I am new to NUCLEO-H743ZI2.  Actually, I am facing the issue of low-speed data transfer from MCU to PC (LabVIEW). Before, I was using programming and debugging USB ports to transfer data to LabVIEW. However, I was only able to transfer at a maximum of 115200bps (14400 Bytes ps). Although my requirement is 50,000 Bytes per sec. Then I found the USB OTG_FS Connector (CN13). However, I am not sure about the maximum speed through which I can transfer data. And what about the Ethernet port (CN14)? 

Hi team,Is there any transceiver that has 2 channels and is ISO14230 or ISO9141 compatible? The most important is that this transceiver must supports 24 V in VBB pin (vehicle batery). Also is important that there is a level changer internally.

Hello,to reply to your request of information: "One open question for you, what kind of antenna do you plan to use to cover both 433 and 868MHz with a single antenna matching circuitry ?"I attach a picture of the antenna vertical sleeve @ lampda/4 whip for 433Mhz that we plan to use to cover both 433 and 868Mhz with a single antenna matching circuitry.Best RegardsVincent Rizzo  

Hello. ST team.i'm using L9369's voltage measurement function.i read L9369 manual, and i send below SPI commands(no.0~6) for initial driving.(my purpose is to drive FET : HS1 A, B ON / LS2 A,B ON)00xb5019ff810xb5a15fef20xb720b54d30xb480aa9840x40a0000d50xbb8020ea60xc3a000f5after sending above SPI commands to check SH1/2_A/B's voltage AD read.140x0c20001f150x0d000010160x0e200001170x0f00000e180x1020001a190x1620001d200x17200012210x1800000d220x19200002230x1a000013240x11000015250x12200004260x1300000b270x14200003280x1500000c290x1b00001c300x1c200014310x1d00001b320x1e20000a330x1f000005after sending above SPI commands, i checked measured data, but the measured voltage is approximately 0.6V lower than the actual measurement value obtained through the oscilloscope.After completing the above operation, I send the following SPI commands(no.7~13) again.(my purpose is to drive FET : HS2 A, B ON / LS1 A,B ON)70xb5019ff880xb5a0bfea90xb7015548100xb4a0aa98110x4080000d120xbba020ea130xb401994dAfte

Hello, I measure the output differential voltage of the drivers (with 100ohm termination resistor) and it is always higher than 0.4V that is referred to the datasheet. What I measure is about 0.68V. Is that normal? Thank you in advance

Good afternoon, We are evaluating the possible consequence for the LVDS transceiver RHFLVDSR2D2 in case that it is supplied with a voltage above its absolute value which is 4,8V.In particular we are asked to evaluate the case that voltage applied to supply is 5V: can you provide us some information to analyse this failure? Is possible to have an equivalent failure impedance to be considered from supply to inputs/output pins?Also a very simple equivalent circuit of input/output would be very useful to analyse effects on interface in such failure case.Kind regards

Hello to everyone. I am trying to see the data via I2C with the capacitive sensor (FDC2214-Q1),but I see the values I have assigned as 0 in live experiment.I'm sure about the hardware part. I would be happy if you help.  /* Private define ------------------------------------------------------------*//* USER CODE BEGIN PD */#define FDC2214_I2C_ADDR_0 0x2A // Address is 0x2A (default) if 0x2B (high) //#define FDC2214_I2C_ADDR_1 0x2B#define FDC2214_DEVICE_ID 0x7F#define FDC2214_DATA_CH0_LSB 0x01#define FDC2214_DRIVE_CH0 0x1E#define FDC2214_DATA_CH0_MSB 0x00#define FDC2214_DATA_CH0 0x00static char value_str[10];uint32_t value = 0;uint16_t lsb_buffer = 0;uint16_t msb_buffer = 0;uint8_t *lsb_buffer_ptr = (uint8_t *)&lsb_buffer;uint8_t *msb_buffer_ptr = (uint8_t *)&msb_buffer;  //HAL_StatusTypeDef HAL_I2C_Mem_Read(I2C_HandleTypeDef *hi2c, uint16_t DevAddress, uint16_t MemAddress, uint16_t MemAddSize, uint8_t *pData, uint16_t Size, uint32_t Timeout)HAL_I2C_Mem_Read(

Hi ST community,does the STUSB4500L also supports negotiation for data communication?E.g. can I use D+/D- pins of the USB-C port while PD is negotiated by the STUSB4500L?The STUSB4500 seems to support that by setting the flag USB_COMM_CAPABLE within (NVM) configuration, while the datasheet of STUSB4500L does not mention anything about data communication nor the USB_COMM_CAPABLE flag.Thanks & best regards, Martin

I have run into problems trying to get voice data from the MP34DT05-A PDM Microphone on the BlueNRGLP eval board. Specifically, and after spending a fair chunk of time (using the BLE_Sensor_Demo_BlueMSApp demo code as a starting point), it appears the ADC register is not being updated while talking into the PDM mic. I was using the KEIL memory window to monitor ADC memory addresses and was looking at the Downsample and Decimation data output registers, which render 0x00000000 and 0xDA880000 respectively. They never change despite applying sound. This leads me to believe that either the PDM microphone or ADC is not being suitably initialized (or something else...that covers the possibilities). Anyone have any suggestions how to slay this beast?Update 07-11-22: Not using Downsample (DS) so that is not of concern. I am using the Decimation Filter (DF). Also learned PDM digital data comes straight from the MP34DT05-A chip and ADC performs decimation (at least I think that's how it works).C

Hello,I'm using a BlueNRG-2 via SPI from a main uC host. The BLE stays advertising and the main uC goes to Standby mode. When someone tries to connect to my device, main uC wakes up. Since I don't want to restart the BLE (this would reset our address, and we would lose information of the device that wanted to connect with us), I'm avoiding re-initialization of the module depending on wakeup flag.However, during first initialization, when setting up the GATT services, I received from the BlueNRG some service and characteristic handles. These are later used to exchange messages, so I need to know their value.When rebooting main uC, I lose this information. I thought I could do aci_gatt_disc_all_primary_services() in order to retrieve the handles, but is not working. I see some other services but not the one from my application (which I add at the first init, as primary service).I know the UUID (since I'm the one initializing the services and characteristics in first place), so I also tri