Welcome to the Infineon Developer Community

[1:43 PM] Petar Acimovic(C)

Hello!

Details of the project layout:

In my project I am using PSoC 6: CY8C62xA, and in the flash memory I store 2 identical images (1MB each in size). That enables me to upgrade image easier and switch between them. I use RTOS on the CM4 core, and CM0p is baremetal.

Plan:

I wanted to place an application bootloader at the beginning of the image to handle some additional logic and in future use it to enable the rest of the application to be position independent code. That application bootloader would still be in flash and start where normally the image would at the beginning. I modified linker to shift the application image by the size of the bootloader and added the jump logic from bootloader to an application:

1. dissabling IRQs and clearing pending ones

2. dissabling all enabled interrupts in NVIC

3. dissabling all enabled peripherals that might generate interrupt

4. dissabling SysTick and its exception pending bit

5. properly excuting__set_MSP, __set_CONTROL, and __set_PSP functions

6. jumping to application using function pointer and going directly to Vtable address for cm0p core

This will jump to the CM0p code of the application where Cy_SysEnableCM4(m4_addr) will start the cm4 core as well. RTOS tasks will run with no issues, everything works correctly except adc.

Problem:

I narrowed down the problem to cyhal_adc_read() funciton on cm4 side of the application. Adc init is fine, but the program stops when trying to execute this function. The interrupt is not starting, but I am not sure if the adc interrupt or IPC one is messed up.

When I halt the CPU, I can see through JLink that there is no hard fault and PC is not stuck at one place. When checking the map, everything is okay, vector table is where it should be.

I checked the map, everything is okay, vector table is where it should be, it is filled correctly.

Does anyone have any ideas what to look for, what could be wrong?

Please let me know if you have some questions or if I need to provide more details.

Thank you!

I'm currently working on motor driver wit usage of #MOTIX 6EDL7141 # for gate drivi

Unfortunately I have some concerns about my implementation of the chip or my configuration.

Every time when I enable driving via EN_DRV pin I am getting BUCK_OCP_FAULT. I have measured every voltage and everything seems fine, I don't know if it is normal behaviour or should I be concerned.

I also noticed that driver is getting quite hot while basically doing nothing - 0% PWM. I have tested both 3 and 6 PWM mode and both behave the same. Driver gets up to 55° after couple of minutes doing nothing which I consider quite hot since there is no load.

Could give me some advise what should I look at, and maybe someone has encountered similar behaviour?

I'm currently working on motor driver wit usage of MOTIX 6EDL7141 for gate driving.

Unfortunately I have some concerns about my implementation of the chip or my configuration.

Every time when I enable driving via EN_DRV pin I am getting BUCK_OCP_FAULT. I have measured every voltage and everything seems fine, I don't know if it is normal behaviour or should I be concerned.

I also noticed that driver is getting quite hot while basically doing nothing - 0% PWM. I have tested both 3 and 6 PWM mode and both behave the same. Driver gets up to 55° after couple of minutes doing nothing which I consider quite hot since there is no load.

Could give me some advise what should I look at, and maybe someone has encountered similar behaviour?

Good afternoon, would it be possible to replace the IGBT module 2mbi450vh-120-51 with the model ff450r12kt4, for use in a powerflex 753 frequency inverter?

Hi,

I was going through document AN2358 which suggests an approach to implementing a Manchester decoder.

I have a query about the implementation.

IEEE 802.3 Ethernet standard states that the input data (Manchester encoded) may have a jitter of +-18ns. Now if this is used in a decoder with a fixed delay count (3/4) to sample an input data bit, how will this circuit sample the correct data and produce the recovered output?

Is there any other way this jitter in the input data can be handled to recover the correct data bit?

Thanks

Pulkit

Hello, 

I want also design the USB3.0 to HDMI use CYPD3120, as described here: Solved: CYPD3120 USB3.0 to HDMI - Infineon Developer Community

But MCDP2900 is not recommended for new design.

Can you recommend me an alternative?

I also found the PS186, but no way to order this chip.

Thanks for an answer

Best Regards
Jakob

Hi

I have downloaded the XMC flasher tool, and when I opened it and tried to connect for the first time I was prompted that there was a new version of the firmware, so I clicked install. But I think somewhere in the installation process it failed, so now the XMC1300 wont connect anymore. I have tried to connect to it using Memtool, but without success.

I have selected device name as 1302-200 (as stated on the chip) and I have selected the connected emulator.

The error log in the XMC flasher is:

INFO-com.infineon.XMCFlasher.MainAppController-main: Logger Name: com.infineon.XMCFlasher.MainAppController
INFO-com.infineon.XMCFlasher.SeggerLibLoad-configureLoad: Not Found property: xmcFlasher.JLink.dllPath Searching in registry key
INFO-com.infineon.XMCFlasher.SeggerLibLoad-configureLoad: Setting property: bridj.JLinkARM.library to: C:\Program Files\SEGGER\JLink_V796e\JLinkARM.dll
INFO-com.infineon.XMCFlasher.SeggerLibLoad-configureLoad: Not Found property: xmcFlasher.JLink.dllPath Searching in registry key
INFO-com.infineon.XMCFlasher.SeggerLibLoad-configureLoad: Setting property: bridj.JLinkARM.library to: C:\Program Files\SEGGER\JLink_V796e\JLinkARM.dll
INFO-com.infineon.XMCFlasher.SeggerDLL-checkAvailabilityAndLoad:  Loaded JLink DLL 7.96.e
INFO-com.infineon.XMCFlasher.MainAppController-start: Starting Application in process ... 
INFO-com.infineon.XMCFlasher.view.RootLayoutOverviewController-handleChangeDeviceName: Setting Device Name configurations
INFO-com.infineon.XMCFlasher.view.RootLayoutOverviewController-handleChangeEmulator: Setting Device Name configurations
SEVERE-com.infineon.XMCFlasher.ErrorLogCallBack-apply: Communication timed out: Requested 8 bytes, received 0 bytes !
WARNING-com.infineon.XMCFlasher.view.RootLayoutOverviewController-handleConnect: com.infineon.XMCFlasher.DebuggerExceptions: Error get BMI value
INFO-com.infineon.XMCFlasher.view.RootLayoutOverviewController-handleChangeDeviceName: Setting Device Name configurations

What can I do to re-flash it?

I have attached an image of XMC flasher