PSoC™ 5, 3 & 1 Forum Discussions

I have developed an application using the USB UART for my PSoC 5LP, and I'm trying to use something like minicom on linux to talk to it. I realize linux isn't "supported" for development, but I'm not trying to program it or anything just communicate via the micro usb port. It works just fine on windows (using putty, 9600 baud), but nothing happens when I try it on linux. I've followed this tutorial but even the "loop back" doesn't work. Testing a USB-Serial Bridge Controller Configured as USB-UART with Linux® – KBA92551

When I do lsusb I see a Cypress device, and I have no errors running `minicom -D /dev/ttyACM0 -b 9600`, it just simply doesn't work. Is this possible or am I just crazy?

We migrated our design from a PSoC Cy8C3246 to a Cy8C3466 and moved some pins in the PCB in order to optimize our hardware design for the analog parts. Now we see that the total current consumption during sleep () is elevated from 8µA in the original design to a variable range from 200µA to 1200µA.  In order to be able to pinpoint the source of this current, we've built a dummy project configuring all pins in the proper mode and level acoording to the hardware design. We use a sleep mode with a 1PPS wakeup timer. The proper functioning of the sleep function is monitored using the uart_putchar() function. All hardware pins have been measured with an oscilloscope  in order to detect unaccounted signal levels . Internally no devices other than the uart  for debugging purposes and all hardware pins are defined in the TopDesign level. Even removing some components from the PCB did not solve the problem. Furthermore, the problem is found in all tested devices of our production batch. We suspect that the current leaks are an internal issue of the PSoC processor. What could cause this type of leaks? What precautions can be taken to prevent this leaks? And why is the leak current so variable?

Thanks in advance for your help,

Kris

I have run into a weird situation.  I am downloading Firmware for another PSoC via USB and storing it in FLASH - later I will bootload the other PSoC with this saved firmware.  To be more efficient, I am buffering the download from the USB and writing using Em_EEPROM in 256 byte chunks.  At then end, I have 10 bytes left to write and when I call Em_EEPROM with that last 10 bytes, it never returns from the call and reboots!  If I change the last write to 256 bytes, it writes to Flash and doesn't reboot!

Mike.

Hi folks,

I'm working on a project to use a PSoC 5 MCU to add extension capabilities to a vintage pocket computer. The pocket computer uses an LH5801 CPU running at 1.3MHz.

I've set up GPIOs to read the 16 bit address bus, read and write the 8 bit data bus, and read the R/W pin. CS for the MCU is by matching 1000 from the upper four bits of address. I have also set up indexed DMA to handle data writes to the MCU memory. Basically, a status register uses some bits from the upper address to get a page offset within a 4K buffer array in MCU memory (4K starting at 0x20002000), and the lower address 8 bits provide the rest of the indexing into the buffer. I grab the buffer address when CS goes high, then read in data when R/W goes low while CS is high.

This mostly works. The problem I'm having is that I can write into MCU memory, with the correct offset into the buffer, and read the data back out, as long as the data value being written doesn't start with 1000. If the data value does start with 1000, it seems like the low pulse on the R/W line is never caught.

This is a bit bizarre for a few reasons:

1. 1000 just happens to be the CS trigger. Coincidence?

2. I have tried implementations without DMA and had exactly the same problem.

3. When I have tried implementations that wrote to a single address in memory, instead of a range of addresses, I had no problem with 1000 values (e.g. 129 or 143).

I'm really pretty stumped now. I would have thought switching to a completely different way of doing things would at least have resulted in different problems.

Any ideas what might be happening or how to further troubleshoot this?

Thanks,
Paul