All Forums
Browse the Community
USB
Universal Serial Bus (USB) forums have discussions regarding Low-Full & High Speed Peripherals, Superspeed Peripherals, USB Hosts Hubs Transceivers, and USB EZ-PD Type C product solutions for PCs and consumer device topics.
Wireless Connectivity
Power
Sensors
Memories
Memory Discussion Forums discussions regarding NOR Flash, SRAM, nvSRAM and F-RAM - performance and reliability with discrete memory densities ranging from 4K-bit to 2G-bit topics.
Other Technologies
Discussion forum regarding Other Technologies including Power Management and Clocks topics.
Security & Smart Card
Radio Frequency (RF)
Software
Software including ModusToolbox, PSoC Creator, WICED Studios and Wi-Fi Bluetooth for Linux .
Applications
Battery Management ICs
Infineon's TLE9012DQU is a multi channel battery monitoring and balancing IC for various lithium-ion battery applications, with integral functions like voltage and temperature measurement, cell balancing, and isolated communication with the main battery controller, including self-diagnosis features. The TLE9015DQU iso UART Transceiver IC is used in battery systems for enabling the communication between the main microcontroller and multiple TLE9012DQU units in a daisy-chain configuration. This forum welcomes discussions, queries, and insights on battery management systems and devices.
Featured Discussions
I'm trying to understand the USB setup. I have a board that has a USB connector connected to the DP and DM pins on the PSOC5. I copied the code from the USBFS example and it runs, but hangs when trying to check the configuration. That appears to be because the Windows 10 computer does not recognize the USB device. It shows up in device manager under "Universal Serial Bus controllers", as "Unknown USB device (Device Descriptor Request Failed)". I am not sure if this is a hardware or software issue. The various documents seem to indicate that I have to find and install a special Windows device driver for the USBFS. I followed the instructions to install it but when I selected the .inf file, I got a message that a compatible file was not found. (That was when trying to install the driver from the unknown USB device entry in device manager.)
In general, why should I need a special device driver? I want to produce a product that creates a com port for anyone who installs it into windows. Why won't the Ftdi drivers work? Is there any path to making them work?
But, from reading, I am not at all sure that this is a driver problem.
Help please.
Thanks Russ
Show LessAs metioned in "AURIX TC3xx Safety Manual v2.0.pdf - 6.38 SM[HW]:CLOCK:CFG_AS_AP", Registers of Clock System is protected by Master Tag based safety machenism. But I can't find related ACCEN0/1 register in "Infineon-AURIX_TC3xx_Part1-UserManual-v02_00-EN.pdf - 10 Clocking System".
Show LessI'm trying to install ModusToolbox on Linux (Ubuntu 22.04) but I fail to get past the login process.
I originally posted a reply to this thread as it looked similar to my issue but was asked to create a new thread instead.
I downloaded "ModusToolboxSetupInstaller_1.0.0.468_linux_x64.deb" from softwaretools.infineon.com and launched it.
I get the following log messages:
After clicking on "Login" nothing happens and I get the following log:
I don't know how to solve this issue as I don't even see a login prompt. I only get the error "Error: Failed to Login: 'process failed to start'"
Show LessI am modifying my UVC descriptors to enable MJPEG streaming in addition to uncompressed but am encountering an error where the device cannot enumerate. Using USB Tree View, I cannot see the specific error being encountered, only that it is not enumerating. This started occuring once I started modifying the wTotalLength field of my Class-specific VS Interface Input Header Descriptor so I think my calculation for this value is correct. My current way to calculate that value is the following:
...
VC-Specific VS Video Input Header Descriptor (size=0x0F)
0x01 larger than with 1 format b/c 1 extra format
VS Uncompressed Format Type Descriptor (size=0x1B)
VS Uncompressed Frame Type Descriptor (size=0x1E)
VS Color Matching Descriptor Descriptor (size=0x06)
Video Streaming MJPEG Format Type Descriptor (size=0x0B)
Video Streaming MJPEG Frame Type Descriptor (size=0x1E)
VS Color Matching Descriptor Descriptor (size=0x06)
...
So I am calculating that the wTotalLength field should be 7D. Is this correct? I am not sure if the Color Matching descriptors should be included in wTotalLength field.
Thanks
Show LessWe're considering a CYW54590-based wifi/BT module for use in an audio device, and it would be very useful to be able to perform (reasonably) accurate time synchronization between multiple devices. Does the CYW54590 firmware support any mechanism to do so? Support for IEEE 802.1AS (gPTP) clause 12 would be ideal but any other mechanism would be welcome too, even something as basic as the ability to cross-timestamp the TSF timer of the CYW54590 (which is already synced between all devices connected to the same wifi AP) by providing the TSF timestamp of a GPIO pulse.
Show LessStill getting used to the newer ModusToolbox apps, as we had used PSoC Creator for years. I created a new project based on the MPN using the BSP Assistant app. This project uses the CapSense library to create a touchpad. Using the CapSense Configurator app, I successfully assigned each of the Rows/Columns to a specific GPIO. This assignment was reflected in the Device Configurator app. However, now I would like to add a few more rows/columns to my touchpad. I labelled these GPIO in the "Pins" tab of the Device Configurator. However, these new GPIO don't appear in either the Device Configurator under the Peripherals>System>CapSense>MSC 0 Parameters window, nor do they appear in the CapSense Configurator under Scan Configuration> Pin. It almost seems like I am missing a step of either importing the Device Config to the CapSense Configurator or vice versa.
Here you can see I have configured the pin at Port 5, Pin 6 same way as the others and named it E45:
But when I then go to the Peripherals tab and try to assign Row 7 to it, it does not appear in the drop-down list:
If I check the CapSense Configurator, it also does not appear in the drop-down list:
None of the rest of the GPIO that I added show up either. What am I doing wrong?
Show Less
Hi,
I have designed a custom PCB with STM32H735 MCU and due to EoL and current unavailability of older HyperRAM S70KL1281 (that was originally used on ST-Micro's Discovery Kit) I decided to choose new HyperRAM S70KL1282. It's wired the same way as on discovery kit (including RWDS signal) and I was carefull about OSPI signal traces length matching.
I set up the MCU OSPI/HyperBus peripheral according to STM example and I use existing HyperRAM driver:
https://github.com/STMicroelectronics/stm32-s70kl1281
I fixed the initial latency from 6 to 7.
I can successfully read the device ID words and config reg 0,1.
The problem is that when I write some data at address 0 and read it back I found the data pattern writen with 8 bytes offset from the address 0 even I use always address 0 as argument to the R/W functions. I also tried enable memory mapped mode and access the RAM via pointer but I still got this strange offset. I also tried to lower the OSPI frequency by divider down to 33MHz but still any change. Contrary the users of old memory chip S70KL1281 doesn't report such problems. They shared the OSPI peripheral configuration that I tried to use so setting on MCU side (master) should be the same but I still have the 8B offset. I cannot get S70KL1281 to try. Any idea what's wrong? Do I need to set something in CR0/1 differently than POR values? Here are some of my code and debug terminal output to describe the issue:
{
uint8_t buff[64]={0};
int i;
buff[0]=0xab; buff[1]=0xcd; buff[2]=0xef; buff[3]=0xaa;
if (S70KL1281_Write(&XRAM, buff, 0, 16)!=S70KL1281_OK)
printf("Failed to write to HyperRAM\n");
for (i=0; i<32; i++)
printf("%02X ", buff[i]);
printf("\n");
if (S70KL1281_Read(&XRAM, buff, 0, 32)!=S70KL1281_OK)
printf("Failed to read from HyperRAM\n");
for (i=0; i<32; i++)
printf("%02X ", buff[i]);
printf("\n");
if (S70KL1281_Read(&XRAM, buff, 0, 32)!=S70KL1281_OK)
printf("Failed to read from HyperRAM\n");
for (i=0; i<32; i++)
printf("%02X ", buff[i]);
printf("\n");
}
The memory address is 0 but I get this:
Ext. OctoSPI HyperRAM ID: 0C81 0001
Manufacturer: Infineon, HyperRAM 2.0, rowbits: 13, colbits: 9
AB CD EF AA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
57 47 57 5D D5 D7 8C 15 AB CD EF AA 00 00 00 00 00 00 00 00 00 00 00 00 D5 D5 57 5F D5 D5 5F 75
57 47 57 5D D5 D7 8C 15 AB CD EF AA 00 00 00 00 00 00 00 00 00 00 00 00 D5 D5 57 5F D5 D5 5F 75
There's some garbage in first 8 Bytes (57 47 57 5D D5 D7 CC 15 - uninitialized memory?) followed by correct pattern AB CD EF AA and trailing zeros from buffer
And the memory mapped mode:
{
__IO uint32_t *mem_addr = (__IO uint32_t *)(OCTOSPI2_BASE);
int i;
if (S70KL1281_EnableMemoryMappedMode(&XRAM)!=S70KL1281_OK)
printf("Failed to Enable Memory Mapped Mode\n");
else
printf("Memory Mapped Mode Enabled\n");
mem_addr[0]=0xABCDEFAA;
mem_addr[1]=0x12345678;
mem_addr[2]=0;
mem_addr[3]=0;
for (i=0; i<48; i++); // a shot delay, 46 read ok, 47 read garbage
printf("%08lX\n", mem_addr[0]);
printf("%08lX\n", mem_addr[0]);
printf("%08lX\n", mem_addr[0]); // 57 45 57 5D = "WEW]"
for (i=0; i<32/4; i++)
printf("%08lX ", mem_addr[i]);
printf("\n");
for (i=0; i<32; i++)
printf("%02X ", ((uint8_t *)mem_addr)[i]);
printf("\n");
}
Output is:
Ext. OctoSPI HyperRAM ID: 0C81 0001
Manufacturer: Infineon, HyperRAM 2.0, rowbits: 13, colbits: 9
Memory Mapped Mode Enabled
ABCDEFAA - this read changes according to for loop short delay, for shorter times it reads ABCDEFAA, for longer times it reads 5D574557
5D574557
5D574557
5D574557 158CD7D5 ABCDEFAA 12345678 00000000 00000000 5F57D5D5 755FF5D5
57 45 57 5D D5 D7 8C 15 AA EF CD AB 78 56 34 12 00 00 00 00 00 00 00 00 D5 D5 57 5F D5 F5 5F 75
Please let me know other users of this memory chip if it works for you properly or not and on what MCU/platform.
Last few days when I zip my project and sent it to my friend, he found it error to build the project. It reported "No AURIX device is configured". Then I tried to re-sent the project for several times but the error still exist.
We also sent the project to others, but they all failed to build it. It seems that the project can only be built successfully in my computer. I read a discussion report the same question earlier and I agreed that it is a very 'early' compiling error because it seems like it is raised in the preprocessor phase of the compiler.
We both use ADS version 1.9.20 and i am sure that the project files are totally same. The error happens only because we use different computers.
Update:
I created a new project and send it to my friend again, but he still fails to build it. I will attach this project below and I wonder if someone could build it successful.
This problem has been bothering us for a few days now. Any help is appreciated!
Show LessI am trying to configure an Infineon Aurix TC334 Lite kit QSPI as master. So far, I managed to configure the necessary pins, change the polarity to work with Gyro 6 Click Gyroscope (bit order - MSB, sampling edge - riging). I using an SPI sniffler and as far as i can see data is being transmitted but i receive nothing on MISO. Do you have any idea?
I've attached a snip with the SPI MOSI/MISO and the code as well.
Show Less
Is it possible to use only one of the TMR wheatstone bridges in the TLI5590 as a magnetic field strength sensor?
If so, where exactly is the center of the sensing element - is it 250 um from the center of the package? Figure 3 of the datasheet shows 3 sensing areas, each 250 um apart, and Figure 6 appears to show the two signals 90deg out of phase on a linear magnetic scale of 1mm pole pitch.
Thank you!
Show Less-
TraveoII
UART buadrate Setting
by chandan1995 Jun 19, 2023