I have a PSoC 4 MCU that I want to program using a Linux machine (raspberry pi, to be precise). Unfortunately, I couldn't figure out how to do it ...
I have a PSoC 4 MCU that I want to program using a Linux machine (raspberry pi, to be precise). Unfortunately, I couldn't figure out how to do it and would appreciate any help.
I have MiniProg3 and MiniProg4 available.
I can program the device from Windows using PSoC Programmer (3.29.0) without any issue with both programmers. However, this program does not have a Linux port, so I can't use it on Linux systems.
I tried to program the device with MiniProg4 and Cypress Programmer (still on Windows). Unfortunately, this fails when I try to connect to the device (log attached - as docx cause .txt or .log extensions didn't work). I tried to do it because the programmer has an option to choose the platform of PSoC 4. Since PSoC 4 was not described as supported for the Cypress Programmer I assume that this is not working. It always fails when I try to connect to the device, regardless of the configuration I tried to connect to the processer with.
Should the Cypress Programmer be able to program PSoC 4 devices? If not, is there any other option to program the device using a Linux machine?
I understand that I can write my own software to program PSoC devices using the SWD protocol, but want to avoid doing this if possible. Since I am running from a Raspberry Pi I am not able to run virtual machines to program the PSoC, so unfortunately this is not an option as well.
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 syst...
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.
for a project I'm doing I needed a voltage regulator with different terminals than your voltage regulator. I was looking at your video about creat...
for a project I'm doing I needed a voltage regulator with different terminals than your voltage regulator. I was looking at your video about creating custom components but am still feeling a bit lost on how to create my specific voltage regulator. I have chosen a specific voltage regulator and other custom components for my project and was wondering how easy is it to create them in psoc? I'm struggling for this big project but have done simple projects such as interfacing thermistor and a dc motor with psoc but still I would appreciate it if you could give me any tips.
Due to unavailability of 212019 we must migrate an existing design to 214015, which is available. We found no way to use the SCB in SPI-Mode because S...
Due to unavailability of 212019 we must migrate an existing design to 214015, which is available. We found no way to use the SCB in SPI-Mode because SCBx_CLK can only be output to P0.7 which is used for debugging. Is it correct that the 214015 has a dedicated SPI_Master which is not mentioned in the datasheet but the outputs can be routed to any GPIO ( or is it a UDB used for that )?
Also for using CapSense, in 212019 we had to add a capacitor to Cmod (P4.0) which is not present in the 214015 but the Port 4.0 appears in the Pin-List (33 of 32) of the creator. Is it an internal Pin of the module, which is in turn connected to this 2n2-capacitor?
Would be nice to have this clear before making new PCB's