Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I have the following wires connected from the MiniProg3 to my target board: VTARG to my 3.3V rail (PSoC supply). No other power applied to the board. There is no other significant load on this rail, maybe 30mA. GND to GND of course SCLK to PSoC pin 1 (P3_1) SDAT to PSoC pin 8 (P3_0)
The programmer cannot connect. It takes a long time, like 30 seconds, then shows the target as "Cortex-M0", but won't connect. Sometimes it doesn't even show that.
Put a scope on VTARG and it is slowly cycling on and off to 3.3V.
I have changed the chip, same result.
I have had similar issues with the standard 5 pin programming interface before, but only when I have needed to put wires to extend the programming interface. I have found that it will NOT detect the target if those wires are more than maybe 2" long. So in this case, because I have wires, they are about 1 inch long.
I see what may be a conflict in the Fan Controller datasheet where manual mode seems to suggest only the ability to use the PWM Duty cycle API a...
I see what may be a conflict in the Fan Controller datasheet where manual mode seems to suggest only the ability to use the PWM Duty cycle API and there is no response to fan speed, but a graphic further down in the sheet seems to imply that the desired fan speed API can be used in manual mode.
So I really need a clarification, before I start writing code.
I'm using the WFlash of a PSoC 6 for emulated EEPROM in a current project. I've noticed a problem in that every time I program the processor, it over...
I'm using the WFlash of a PSoC 6 for emulated EEPROM in a current project. I've noticed a problem in that every time I program the processor, it overwrites the WFlash sector. I seem to be able to avoid writing this section when I load the code through the PSoC Programmer software, but cannot find the means to do the same when programming through PSoC Creator 4.4. Is this option hidden somewhere that I haven't seen or is it just not possible? I'd rather not have to switch over to PSoC Programmer every time I want to flash a new build in order to maintain EEPROM values.