Hi,

I'm using PSoC 4 board, I'm also using the WDT0 and WDT1 as the system timers as they work in the sleep mode, So I had to use the WDT2 as the system watchdog timer.

The WDT2 generates an interrupt when it fires, So I reset the system in the interrupt.

So, I disable the WDT2 when I'm going to sleep mode, and re-enable it after I wake up.

I found that the system sometimes could not enable the WDT2 and stuck in this excessive loop.

        if(0u != (counterMask & CY_SYS_WDT_COUNTER2_MASK))
        {
            while (0u == CySysWdtGetEnabledStatus(CY_SYS_WDT_COUNTER2))
            {
                /* Wait for changes to come into effect */
            }
        }

I also found this comment

" * Enabling or disabling WDT requires 3 LFCLK cycles to come into effect.
* Therefore, the WDT enable state must not be changed more than once in
* that period."

So, I controlled the calls of CySysWdtEnable and CySysWdtDisable, and I made sure that they were not called within 3 LFCLK clocks, But this also did not solve the issue.

I also use a GPIO pin to measure the time between calling these functions(CySysWdtEnable, CySysWdtDisable), I found the minimum time is taken was 180us and the LFClK frequency was 32,768 kHz, So the 3 clocks should be 91.55us, So 180us should not makes any troubles.

So, If there are any solutions or guides to solve/avoid this issue will be very helpful.

Best Regards,

Khalil Azouz

I want to use DMA to transfer chunks of data (32 bytes at a time) into a component that I'm implementing with verilog. 

I plan to use the control register to transfer the DMA data into the component. One thing I don't understand is, within the veriolg code, does the component know when new data has arrived in the control register? Is there some sort of enable signal or handshake to indicate when a transfer is complete? I can't find this anywhere in the documentation. 

Hi,

I am using the XMC1300 to control a Boost converter in PCC mode. I have started with the project 'BUCK_PCC_FIX_FQ_EXAMPLE_XMC13' as this uses DAVE apps and makes it easy to validate. I have the control working in open loop, i.e, changing duty changes the output as expected. However, in Closed loop current control, the PWM signals experience false switching at the start of the switching cycle. The control somewhat works at low input voltages but always mis-triggers at higher operating input voltages. Hence, I would like to implement LEB.

I have ticked the blanking option and set the blanking time. I see that there is difference in the CCU4 timer configuration. But this does not make any difference to its performance. I have attached the snapshot of the configuration in Dave and the waveform as seen on the scope.

The inductor current is represented in yellow while the Low side gate voltage is represented in Blue. Switching frequency is 100 kHz.

I do not suppose any hardware modifications are required as the modules are internally connected. Is there something I have missed? Please let me know.

I have got a problem and need some help.I have designed a custom board refer to datasheet and a development board bought online.The board I desined contains two sensor OV5640 , two CYUSB3065，and a usb hub controller TUSB8020BPHP. (I want to send two sensor image to USB )

The question is that the board  I bought on online (only one  Cyusb3065) can download .img file to SPI flash，but custom board I designed cannot work as that.

When I connect my custom board to USB， EZ USB Suite  can identify the two CYUSB3065，but when I try to click "Program ->FX3 ->SPI Flash",One of CYUSB3065 can prompt me to select .img file, but after selecting .img file EZ USB Suite indicates "Programming of SPI FLASH Erase Failed",and I use oscilloscope but can not see the waveform of SPI SCK, MOSI,MISO,etc 

Another CYUSB3065 indicates that "Waiting for Cypress Boot Programmer device to enumerate" ->"Cypress Boot Programmer Device not Found".

It seems that  the configuration and driver of  EZ USB Suite  is correct, because I can burn the SPI Flash program normally with the same procedure on the development board I bought online (only one  Cyusb3065).

I need some help to solve the problem of my custom board,Thank you very much.

Hello,

for our application we would like to use USB virtual com port to send/receive status messages with FX3s. My understanding is that I will need a MANUAL_IN DMA channel to transfer messages to the FX3 CPU and a MANUAL_OUT buffer to send messages to the host PC. I have modified the USBUart example project, but have encountered a lot of errors.

1. When using a MANUAL_IN channel it appears the producer fills up our buffers and then quits producing events. We aren't sure how to consume the data in the buffers that producer events keep firing.
2. When using a MANUAL_OUT channel, the overall application is broken and the host can no longer connect to the serial port. The USB setup completes as our host PC can see the COM port, but is unable to connect.

Can someone please help us understand the steps needed to produce/consume data with manual DMA channels?

After quite some tinkering and many unsuccessful attempts, I created a method for loading firmware through ASC and (more important), enabling SWD when the only J-Link available doesn't support SPD (J-Link EDU Mini).

It's basically a python script that loads a .bin firmware through a cheap serial adapter using ASC protocol. It allows us to send a firmware that sets the BMI register to SWD debugging mode, making it possible to debug and flash with our J-Link EDU Mini.

Everything is on this repository: equipepucpr/xmc_loader: Infineon ASC BSL Script (github.com)

Hi, I got the same problem. "Why in manual mode the slave fifo interface flags don't change?" 

and I can not get the answer from this case. It has been a long time since this case created.

Hi,

I'm creating a component which uses a rising edge trigger input. The component uses two states. In the first state, the inputs are saved and the internal state machine switches to the next state on trigger, does some calculation and then switches back to the first state.

I wonder if storing the values in the first state should always be performed, leaving the trigger event to only change the internal state or saving the inputs only when the trigger is detected. Currently I can't see no difference, but my experience with hardware description is quite low.
Maybe someone can give pro/contra for each approach?

Regards

Dear Receiver,

There is an IoT device and it will be designed to connect to AWS (Amazon Web Service). 

Under this condition, do I need to select a MCU (PSoC_6, CYS0644xx) with Amazon FreeRTOS support ?!

I feel a little confused about...

If I select a MCU (PSoC_6, CYB0644xx) with only FreeRTOS support, dose this mean this IOT device can't connect to AWS ?!

Thank you so much.

I am using CY2305 with the configuration shown in the schematic below.

I measured the waveform of CLK1. It has a lot of jitter. (Approximately 2ns)

According to the data sheet, Cycle-to-cycle jitter is 200ps(max), but there is no Period jitter spec. Is this waveform normal? If yes, what can I do to reduce jitter?

I measured CLK1, but the waveform (jitter) is the same for the other output pins. It does not change depending on the load of the opposite device. Jitter tends to increase at high temperatures.

Thanks,
Tetsuo