Browse the Community
Discussions regarding PSoC and MCU products.
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.
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.
Discussion forum regarding Other Technologies including Power Management and Clocks topics.
I have a EVAL-M1-101T board which has IMC101T -T08 MCE on it. the eval board also has XMC4200 as the onboard debugger. The board is connected to PC via J Link and Matlab can see the COM port.
How can I read the registers and send command using Matlab?
Thank you for your help!Show Less
We are using the S70KL1282 HyperRAM chip with the i.mx rt 1064 and for now we've only been using the IP Bus. We've managed to read all registers on the part shown below:
FlexRAM Config Reg0 - Die 0: 0x8f2f
FlexRAM Config Reg0 - Die 1: 0x8f2f
FlexRAM Config Reg1 - Die 0: 0xffc1
FlexRAM Config Reg1 - Die 1: 0xffc1
FlexRAM Die Manuf - Die 0: 0x3030
FlexRAM Die Manuf - Die 1: 0x3030
FlexRAM ID Reg0 - Die 0: 0x0c81
FlexRAM ID Reg0 - Die 1: 0x4c81
FlexRAM ID Reg1 - Die 0: 0x0001
FlexRAM ID Reg1 - Die 1: 0x0001
I've hooked up a scope and writing the data all seems correct, however on the read I am always getting 4 bytes of "garbage" data, in this case 0x0051dd5d. I've mostly been trying to read/write from memory address 0, but it seems I always get the "garbage" bytes with any memory address. Any help or suggestions on where to go would be appreciated.Show Less
Can't find the soldering peak reflow and also MSL documents for the 1EDN7550U gate driver on the product web page. There is a good board assembly app note with soldering guidelines, but customer is looking for the peak reflow specification.
Please send, thank you!
Infineon PSS FAEShow Less
Is it possible to create an SDIO interface on a PSoC 63 in a WLCSP?
Specifically; is it possible to either split the SDIO to multiple ports or route a UDB based SDIO interface to one of the ports with six or more signals?
There is support for creating a UDB based SDIO interface @ https://github.com/Infineon/udb-sdio-whd
The available library supports an SDIO interface on one of three different ports: P2, P9 or P12. The SDIO interface requires six (6) signals on whichever port is selected for SDIO. Reference the table under "Whats included" @ https://github.com/Infineon/udb-sdio-whd
It appears only a maximum of five (5) signals are available for any of those three ports on a PSoC 63: P2, P9 or P12.
Other ports on the PSoC 63 in a CSP have six or more signals including: P0, P5, P6, P7, P8, P10 and P11.
Reference Table 7 in PSoC 63 CY8C63x6, CY8C63x7 Datasheet @ https://www.infineon.com/dgdl/Infineon-PSoC_6_MCU_PSoC_63_with_BLE_Datasheet_Programmable_System-on-Chip_(PSoC)-DataSheet-v16_00-EN.pdf?fileId=8ac78c8c7d0d8da4017d0ee4efe46c37
We are using a PSoC5LP and just implemented our bootloader. We are going to program the bootloadable application via the i2c bus from another microcontroller.
The other microcontroller is responsible for sending a "Reset" command to the PSOC to get it into bootloader mode.
What is the correct sequence in the PSOC for the bootloadable application to issue a reset command so it can go into the bootloader, and then wait for the specified host link time in the bootloader?
This forum post [Link] says to do the following in the bootloadable application:
However, when I browsed the generated source code of Bootloader.c, it appears that if SCHEDULE_BTLDER is set, then it will wait forever for the command, and not even check the wait time set in the bootloader component.
If CySoftwareReset() is used without setting the run type, does the PSOC reset to the bootloadable or bootloader?
We used a PSOC4 in a different application, and our reset process was to enable the watchdog so we could reset from that. PSOC5LP is different, because the watchdog API is not as flexible as the PSOC4. Our watchdog is already going to monitor the application, and the timeout is too much for us to use for this purpose.Show Less
 chapter 126.96.36.199 states "The ECC error detection can be triggered on purpose to test the detection itself and the associated trap routine. This test option is available for RAMs". So, previous stated chapter describes how the RAM ECC error detection can be tested. That’s fine.
My question: How can the flash ECC error detection be tested?
Question reason: In  chapter 188.8.131.52 I see the flash ECC description. But I don’t find in  a chapter for the flash, which is similar to (above stated)  chapter 184.108.40.206.
I am using XMC4800 controller having 144 pins and 2mb size (XMC 4800 F144x-2048). Previously in my project we use 3 SPIs and now we add another SPI i.e, total 4 SPI we are using and every SPI is in MASTER and Full Duplex mode and we use SPI_MASTER_0 for communicating with Flash 1 and Flash2 which are same MAKE and it's working fine. Now we add SPI_MASTER_3 and SPI_MASTER_0 is used for Flash1 and SPI_MASTER_3 for Flash2. In the attached image we use different pinouts for different SPIs. SPI_MASTER_0, SPI_MASTER_1 and SPI_MASTER_2 are working properly but SPI_MASTER_3 we are not able to communicate with Flash2.
Is there any issue with this controller by using 4SPI's?
Overcurrent Protection No hardware shutdown. Software interrupts do not have the highest priority, why?
The optimal solution should be a hardware shutdown.
Hi community ,
I am using CCg3PA in my project, is there a way to read D+ /D- line status or voltage from we as source and DUT as sink. Is there a specific function for this requirement.
I followed this link to enable XMC_DEBUG/printf() function.
However, I got this error at the end. Can you guide me to resolve this? Thank you
"\"C:\\Infineon\\Tools\\DAVE IDE\\220.127.116.11105191637\\eclipse\\ARM-GCC-49\\bin\\make\"" --output-sync -j8 all
arm-none-eabi-gcc: fatal error: c:/infineon/tools/dave ide/18.104.22.168105191637/eclipse/arm-gcc-49/bin/../lib/gcc/arm-none-eabi/4.9.3/../../../../arm-none-eabi/lib/nosys.specs: attempt to rename spec 'link_gcc_c_sequence' to already defined spec 'nosys_link_gcc_c_sequence'
'Building target: 1300_LC.elf'
'Invoking: ARM-GCC C Linker'
make: *** [1300_LC.elf] Error 1
"C:/Infineon/Tools/DAVE IDE/22.214.171.124105191637/eclipse/ARM-GCC-49/bin/arm-none-eabi-gcc" -T"../linker_script.ld" -nostartfiles -Xlinker --gc-sections -specs=nano.specs -specs=nosys.specs -u _printf_float -u _scanf_float -Wl,-Map,"1300_LC.map" -specs=rdimon.specs -specs=nosys.specs -mcpu=cortex-m0 -mthumb -g -gdwarf-2 -o "1300_LC.elf" "@objects.rsp" -lm
makefile:54: recipe for target '1300_LC.elf' failed