We are sending data using MasterWriteBuf API of I2C.

Its API is defined below.

uint8 I2C_MasterWriteBuf(uint8 slaveAddress, uint8 * wrData, uint8 cnt, uint8 mode)

According to this API, since wrData is uint8, it is 256 pieces.

.

We would like to transmit more than 256 data.

Is it possible to realize it?

Good evening. I have a test project running on CY8CKIT_059 that uses both the USB UART and the UART (Kitprog port). The protocol used by both ports is configurable.

I am able to read data from PSOC on the two ports at the same time with two PUTTY sessions. Problem is that when I turn off the session reading from USB COM port, the other port will halt sending commands.

This is because I write to both ports, and on USB side there's the 'classic' cycle that waits the USB to be ready for transfer:

while (0u == USBCOM_CDCIsReady());

USBCOM_PutString(s); 

This does not happen on the serial port.

What's the best strategy to detect full buffer (or better COM port not open by any program/not active)? Also is there a way to detect port reopening as to suspend send and clear the buffers befrore restarting the serial stream?

Thanks

Marco

hello I am currently using PSoc5 LP-096 in my project and i have 2 questions

1)On the  board I wanted to messure the voltage between the 5V and GND(ground) how ever when i messured it the voltage was 4.06V and not 5V why is that ?

2) I am using ADC block and my question is what is default Vref ? the reason i am asking is that if the Vref is 5 and in real messirment it gives me 4.06V it gives me wrong answer of the Output of the ADC 

Hello,

I have a CAN based Bootloader and I managed to flash a PSOC5 board with specific code. It works as expected until I disconnect the power supply. Then the bootload process remains in the WAIT_Forever state even though I set the Bootloader component to wait for command a specific time (5 seconds).

I think my problem is related with this thread Serious bug in bootloader component.  Is there a workaround? I tried to add CySetTemp() in bootloader project before CyBtldr_Start() and it does not works.

We would like to be able to operate SD card from PC using USB and emfile component in PSoC 5LP.

Is it possible to combine these two components?
Do you have such experience in the past?
We would like to obtain a sample project if possible.

Hi,

I'm trying to get bootloader with SPI transport to work. I have something that usually works, but it's very fragile - basically the PSoC bootloader logic doesn't handle extra bytes in the communication very well.

The issue with SPI (vs UART) is that the host need to send data in order to read data from the slave (=PSoC). This data ends up in the incoming buffer on the PSoC side, and the bootloader will fail when it contains unexpected data. We have tried to send 0x00 and 0x01 from the host as dummy data (while reading data from the slave), but in both cases it fails.

The bootloader protocol should allow both these numbers as 'dummy data' that is thrown away - the bootloader doesn't seem to have proper parsing (that is, erroneous data in the incoming buffer should be thrown away).

Our current 'solution' is having sleeps here and there in the host code that make sure that we only read when the PSoC is ready. However, this is very error-prone and slow.

Is there a solution to this? I know I can fix it on the PSoC side by overriding CyBtldrCommWrite, parse the data received and only deliver it to the bootloader logic in case it's valid bootloader protocol data - but should I really have to do that? It really should be handled by the bootloader internally.

Thanks, Jacob

Lately I find that Microsoft Windows 7 thinks it knows what is best. I have disabled and uninstalled the Microsoft's driver

associated with my CY8CKIT-059 PSOC 5LP Prototyping Kit multiple times. Then I unplug the board from my hub and

reinstall it. I tell it to use the location of the ProgKit driver and it responds that it has chosen the best driver which of

course is the Microsoft driver.

The debugger port does get to use the KitProg driver (setup as a USB bus controller -> USB Composite Device). Its just the Human Interface Devices -> USB Input Devices which seems to use the Microsoft HID driver. See the attached picture. Any ideas ?

Randy