Cypress CY8CKIT-059

model: CY8CKIT-059

Cypress Device Programming Specification: PSoC 5LP, PSoC 4, PSoC 3,

Cypress application notes: AN60317 I2C bootloader, AN68272 UART bootloader, AN73503 USB bootloader,

forums: PSoCDeveloper, Cypress Developer Community : PSoC5, Software, PSoC Creator,

projects: FluxEngine,

Links

www.cypress.com/CY8CKIT-059, PSoC Creator, Wikipedia: PSoC, WineHQ AppDB: Cypress PSoCCreator,

more links

cypress_linux_tools, cybootload_linux, m8cutils, cyflash, KitProg, PSOC_Programmer, PSOC_Compiler, psoc_flash, Hackster.io USBUART Bootloader,

articles

Achieving 1 mega-sample-per-second off of a device, PSoC 5LP USB Dual COM Port, 11 serial ports with PSoC5, PSoC 5 Port Of the Grbl 1.1 CNC Controller,

local links

[FluxEngine], PSoC Creator, U35JC Windows, bb - ASRock BeeBox-S 7100U Debian,

Back to FPGA page.

History

2021-08-01: I re-created this page on my self-hosted web server.

2019-03-27: soldered up a 34-pin IDC connector to a CY8CKIT-059 'Rev *C' today.

2019-03-06: Cypress store - FedEx has delivered my 2 kits to Bitraf. Nice. The new CY8CKIT-059 are labeled 'Rev C' and one of the has '1905SO00796' the other '1905SO00358' so perhaps that last bit is a serial number. The first kit I got is labeled 'Rev B' and '1813SO03526'.

2019-03-05: Cypress store - I got a shipped notice in email.

2019-03-04: bb - permissions for the FluxEngine

tingo@kg-bsbox:~$ cat /etc/udev/rules.d/98-fluxengine.rules
# FluxEngine - rules to let users in 'dialout' group access the device
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="6e00", GROUP="dialout"

use udevadm to reload rules

tingo@kg-bsbox:~$ sudo udevadm control --reload

ok

2019-03-04: bb - testing - ah, the floppy drive cable I use only has one connector and it is after the twist. So, drive 1 it is

tingo@kg-bsbox:~/personal/projects/psoc/fluxengine$ .obj/fe-rpm -s :d=1
Rotational period is 166 ms (361.446 rpm)

ok, it works.

tingo@kg-bsbox:~/personal/projects/psoc/fluxengine$ .obj/fe-testbulktransport
Transferred 1048576 bytes in 1170 (874 kB/s)

better than 600 kB/s - good.

2019-03-04: bb - testing -

tingo@kg-bsbox:~/personal/projects/psoc/fluxengine$ .obj/fe-rpm
Error: cannot find the FluxEngine (is it plugged in?)

permissions problem, needs to be fixed

tingo@kg-bsbox:~/personal/projects/psoc/fluxengine$ sudo .obj/fe-rpm
Error: failed to receive command reply: Input/Output Error
tingo@kg-bsbox:~/personal/projects/psoc/fluxengine$ sudo .obj/fe-rpm
Error: failed to receive command reply: Input/Output Error

hmm, bad drive? Powered the drive from a 5V PSU - no change. No light in the drive LED.

2019-03-04: bb - connecting the FluxEngine to my Debian machine, I get this in /var/log/messages

Mar  4 15:08:19 kg-bsbox kernel: [967809.590491] usb 1-1.3: new full-speed USB device number 29 using xhci_hcd
Mar  4 15:08:19 kg-bsbox kernel: [967809.696195] usb 1-1.3: New USB device found, idVendor=1209, idProduct=6e00
Mar  4 15:08:19 kg-bsbox kernel: [967809.696199] usb 1-1.3: New USB device strings: Mfr=2, Product=1, SerialNumber=128
Mar  4 15:08:19 kg-bsbox kernel: [967809.696201] usb 1-1.3: Product: FluxEngine
Mar  4 15:08:19 kg-bsbox kernel: [967809.696203] usb 1-1.3: Manufacturer: Cowlark Technologies
Mar  4 15:08:19 kg-bsbox kernel: [967809.696205] usb 1-1.3: SerialNumber: 76000218160D2874

lsusb output

tingo@kg-bsbox:~$ lsusb -d 1209:6e00
Bus 001 Device 029: ID 1209:6e00 InterBiometrics

lsusb -t output

tingo@kg-bsbox:~$ lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 3: Dev 29, If 0, Class=Vendor Specific Class, Driver=, 12M
        |__ Port 1: Dev 26, If 0, Class=Hub, Driver=hub/4p, 12M
            |__ Port 2: Dev 27, If 0, Class=Hub, Driver=hub/4p, 12M
            |__ Port 3: Dev 28, If 0, Class=Hub, Driver=hub/4p, 12M
        |__ Port 4: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 480M
        |__ Port 4: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 480M
    |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 3: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 4: Dev 8, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 4: Dev 8, If 0, Class=Wireless, Driver=btusb, 12M

ok

2019-03-04: bb - test hardware - I'm using a Panasonic JU-256A 3.5 inch floppy drive to test this thing. Status of the drive is unverified.

2019-03-04: bb - build FluxEngine client (after fixing missing dependency - libusb-1.0-0-dev)

tingo@kg-bsbox:~/personal/projects/psoc/fluxengine$ make
meson .obj
The Meson build system
Version: 0.37.1
Source dir: /zs/tingo/personal/projects/psoc/fluxengine
Build dir: /zs/tingo/personal/projects/psoc/fluxengine/.obj
Build type: native build
Project name: fluxclient
Native cpp compiler: c++ (gcc 6.3.0)
Build machine cpu family: x86_64
Build machine cpu: x86_64
Found pkg-config: /usr/bin/pkg-config (0.29)
Native dependency libusb-1.0 found: YES 1.0.21
Native dependency sqlite3 found: YES 3.16.2
Native dependency zlib found: YES 1.2.8
Build targets in project: 46
ninja: Entering directory '.obj'
[126/127] Running all tests.
1/6 DataSpec                                OK       0.01 s
2/6 Flags                                   OK       0.02 s
3/6 FmMfm                                   OK       0.02 s
4/6 BitAccumulator                          OK       0.02 s
5/6 Kryoflux                                OK       0.02 s
6/6 Compression                             OK       0.01 s
Full log written to /zs/tingo/personal/projects/psoc/fluxengine/.obj/meson-logs/testlog.txt.

ok.

2019-03-04: FluxEngine hardware - I soldered up a 34-pin IDC connector to the PSoC per building instructions. I also soldered a pin header to VDD and GND, so I can use female jumper wires to connect power to a 3.5 inch floppy drive.

2019-03-02: Cypress store - I see that the CY8CKIT-059 is only USD 10 from Cypress store (shipping is USD 15.) so I order two kits.

2019-03-02: u35jc - PSoC Creator - I build the FluxEngine project, then program it. That procedure works. Nice.

2019-03-02: u35jc - I clone the FluxEngine project with the help of git.

2019-03-02: u35jc - PSoC Creator - after upgrading firmware on the KitProg, I could program the target. The only thing it does is blink the user LED (LED1). But at least it works.

2019-03-02: u35jc - PSoC Programmer - I used the tool (Utilities tab) to upgrade the firmware on the KitProg - I had to try twice before the upgrade worked.

2019-03-02: u35jc - PSoC Creator opened blink example, built it, and tried to program it, but got a messages saying that my programmer firmware (2.19) was out of date.

2019-03-02: u35jc - I connected the PSoC 5LP kit to my win7 machine. on KitPRog LED3 lights up green, and LED2 orange, On target, LED1 blinks blue.

LED1 - (blue) user
LED2 - (amber / orange) power - via PCB usb
LED3 - (green) status -

2019-01-03: connecting the kit to my Debian workstation, I see

tingo@kg-bsbox:~$ lsusb -d 04b4:f139
Bus 001 Device 013: ID 04b4:f139 Cypress Semiconductor Corp.

and

tingo@kg-bsbox:~$ lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/4p, 12M
            |__ Port 2: Dev 8, If 0, Class=Hub, Driver=hub/4p, 12M
            |__ Port 3: Dev 9, If 0, Class=Hub, Driver=hub/4p, 12M
                |__ Port 3: Dev 13, If 3, Class=CDC Data, Driver=cdc_acm, 12M
                |__ Port 3: Dev 13, If 1, Class=Vendor Specific Class, Driver=, 12M
                |__ Port 3: Dev 13, If 2, Class=Communications, Driver=cdc_acm, 12M
                |__ Port 3: Dev 13, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 4: Dev 7, If 1, Class=Human Interface Device, Driver=usbhid, 480M
        |__ Port 4: Dev 7, If 0, Class=Mass Storage, Driver=usb-storage, 480M
    |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 4: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 4: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M

so a 12M device then. From /var/log/messages

Jan  3 20:59:35 kg-bsbox kernel: [ 7820.093325] usb 1-1.1.3.3: new full-speed USB device number 13 using xhci_hcd
Jan  3 20:59:35 kg-bsbox kernel: [ 7820.215545] usb 1-1.1.3.3: New USB device found, idVendor=04b4, idProduct=f139
Jan  3 20:59:35 kg-bsbox kernel: [ 7820.215552] usb 1-1.1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=128
Jan  3 20:59:35 kg-bsbox kernel: [ 7820.215557] usb 1-1.1.3.3: Product: Cypress KitProg
Jan  3 20:59:35 kg-bsbox kernel: [ 7820.215560] usb 1-1.1.3.3: Manufacturer: Cypress Semiconductor
Jan  3 20:59:35 kg-bsbox kernel: [ 7820.215564] usb 1-1.1.3.3: SerialNumber: 08190DF301237400
Jan  3 20:59:35 kg-bsbox kernel: [ 7820.218464] hid-generic 0003:04B4:F139.0005: hiddev0,hidraw4: USB HID v1.11 Device [Cypress Semiconductor Cypress KitProg] on usb-0000:00:14.0-1.1.3.3/input0
Jan  3 20:59:35 kg-bsbox mtp-probe: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.3"
Jan  3 20:59:35 kg-bsbox mtp-probe: bus: 1, device: 13 was not an MTP device
Jan  3 20:59:35 kg-bsbox kernel: [ 7820.237895] cdc_acm 1-1.1.3.3:1.2: ttyACM0: USB ACM device
Jan  3 20:59:36 kg-bsbox kernel: [ 7820.240669] usbcore: registered new interface driver cdc_acm
Jan  3 20:59:36 kg-bsbox kernel: [ 7820.240674] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN

good.

2019-01-02: I got a text message from UPS, informing me that the package had been delivered to a pick-up point. Later in the evening I picked up the package (pick-up point was around the corner from where I live, very convenient). tracking history

Customer Collection     02.01.2019 20:39    OSLO, NO    

Past Event
    Delivered to a UPS Access Point location    28.12.2018 13:03    Oslo, NO    

Past Event
    Delivery Attempted  28.12.2018 11:12    Oslo, Norway    

Past Event
    Shipped     25.12.2018 22:06    Louisville, KY, United States   

Past Event
    Label Created   24.12.2018 12:04    United State

2018-12-24: Digi-Key has shipped the package.

2018-12-22: I ordered 1 x CY8CKIT-059 from Digi-Key. Price was NOK 126.71 and shipping was NOK 145.- a total of NOK 271.71