PSoC™ 5, 3 & 1 Forum Discussions

Hi Guys, (and Gals, (and Those)),

I am using PSoC Creater 4.4 with a CY8CKIT-059 Prototyping Kit.

I am unable to locate example code "USBFS-UART" in PSoC Creator.

Pease help me with a link to this example.

Chuck

1) Implement an interrupt-based program for LED brightness change using a PWM module to Gradually, increase the brightness of the LED from zero to maximum in 3 seconds. And turn off the LED for the next two seconds.

2) Repeat this pattern periodically.

Please help how to do this step by step on PSoc Creator4.4?

the PLL is looked to ext very low jitters clock what the contribution of the PLL to the jitters on master clock.

Hello,

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:

    Bootloadable_SET_RUN_TYPE(Bootloadable_SCHEDULE_BTLDR);

    CySoftwareReset();

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.

Hello,

I am using an external microcontroller to write to the bootloader on a PSOC5LP via the i2c interface. I have successfully compiled the .c files provided by Infineon for the bootloader and I can successfully write the new bootloadable image to the PSOC.

However, I am having a trial-and-error approach when it comes to delays between writes and reads.

The internal code for transferring data has no delay between the write and read.

I have found that if I do not add a delay after the write in the WriteData callback function, then the program will fail immediately because the PSOC does not have time to fill its i2c buffer before the external microcontroller calls the ReadData callback function.

I want to be able to program as fast as possible, so I started experimenting with different delays after writing. I found that if I use a delay of 15 milliseconds after each write, then the program-row reads all come back successful. However, I believe one of the last commands after programming is to verify the application, and it seems like the PSOC takes longer to respond to that command. If I use the delay of 15 milliseconds, which works fine for all rows, then the last command always fails because the PSOC responds with all 0xFF's (I don't think the PSOC finished verifying the application, or whatever function it was doing).

If I set the delay to 50 milliseconds after each write, then it successfully programs, and the last command passes as well.

However, I want to be able to program the new image as fast-as-possible, and it seems I only need that 50 ms delay for the final write.

What is the recommended method for i2c programming as far as delaying the read until the PSOC is ready? Is there a GPIO that could be toggled so my external micro knows that the PSOC has filled the i2c buffer?  The "TransferData" command inside the PSOC source files has no indication of what type of packet it is sending, so I am not sure how I could add logic to delay a different amount based on what type of command is being requested.

Is there an option inside the reprogramming source code for retry attempts?

Thanks,

Jason