PSoC™ 4 Forum Discussions
I kind of remember reading somewhere about the limitation that you cannot run debug (icon is grayed out) when your system is configured with a for OTA programming. Is that true? (appears to be the case) and why the limitation? Disabled the bootloadable and Debug still appears to be disabled.
Show LessHi,
Here's a weird question. Is there some way I can short two pins together inside the PSoC (in firmware) ?
I want to use an SCB UART, and route its TX output to some other digital components inside the PSoC. Obviously I can't do that in the same way I could with a UDB UART, because the I/O connections aren't available for connection.
What I'm doing instead is to externally connect the UART's TX pin to another pin on the chip, then routing that pin to other internal components.
But I'm thinking that there might be some (unconventional) way to do this in firmware. Is there some way, in firmware, to connect the SCB UART TX pin to the Digital System Interconnect, and route it also to another pin?
Hugo
Show Lesshello:
I used s34ml02G100 before , i fond a new ic " S34ml02g200 " is similar to it
My question is
1 what’s the main difference between these tow IC?
2 Which ECC type ( 1bit ecc /528byte or 4bit /528 byte) should I applicated on each ic ?
3 Can I use 1bit ecc/ 528byte on s34ml02G200 ?
looking forward your reply! thanks
note : this topic have declared on the nand flash bbs zone ,but nobody answered.
Show LessHello,
I purchased a CY8CKIT-142 to experiment a bit with the bluetooth LP radio. I am very familiar with cypress's tool chain, since I've been using cypress PSoCs for several different projects over the past 4 years, and I found it very simple to use.
Right out of the box, I snapped off 5 male header pins, stuck it in my miniprog3, and then stuck the 5 pins (triple checking my orientation) into the kit-142. Unfortunately, through PSoC Creator, the miniprog3 didnt see the PSoC4 on the kit-142. I tried many different settings, including powering it at 3.3V and 5V. As well as power cycle and reset acquire modes, different clock frequencies, and even toggling between 5-pin and 10-pin connectors. NOTHING. I have replaced the 5pin header thinking the contacts may be too short with standard 22AWG wire, still with same result.
Unfortunately the only thing I have to work with at home is my DMM, and my CY8CKIT-050. On Monday I can use my scope at work to further probe around, but I was excited to get some prototyping done this weekend.
I have verified that at least the 10-pin SWD setting on the miniprog3 works by just connecting it to my kit-050. It detects the PSoC5 just fine.
I would greatly appreciate if anyone had any ideas/tips.
Show LessHi all,
Im new to Cypress Psoc4 BLE, my abstract is to take the data from the user i.e (any value like character saying 20 people then ill switch ON the relay so that it only allows 20 people in a slot to room.)
so here i dont know how to capture the User given data from CySmart Android app or Bluetooth Dongle.
Can any one guide how do get value from user.
Thanks in advance.
Show LessHi,
CySmart displayes only empty strings on the Device information - except for the Manufacturer Name set in the profiles settings.
Calling f.ex. CyBle_DissSetCharacteristicValue(CYBLE_DIS_SERIAL_NUMBER, sizeof(serialNumber), (uint8 *)serialNumber); seams not to have any effect. Taken from the BLE_DEVICE_INFORMATION example.
How is the strings filled from the main.c ?
Thank You
Show LessIs it possible to use different methods for upgrading a BLE device (eg, OTA, upgrade via UART) for a given system, or does the use of one method preclude the use of the other?
Show LessHi,
I implemented BLE OTA in a 256kb PSoC 4 , it is working fine, but I want to know if is possible the Launcher main project get stuck and how to recover from this without physical reprogramming.
Regards
Show LessHello,
I have a problem with my interrupts. First of them appears every 30 seconds (it's interrupt on timer), and the second appears when there is a "1" on one of the pins. The problem is that both of them triggers the same function, so I would like to have some kind of protection to be sure that when one of the interrupt already triggered this action, the other won't do that, because it's pointless and it causes troubles. How can I achieve that? I tried with :
if((flag_interruptclock == 1) && (flag_pir == 1)){
flag_conflict = 1;
}
for (i = 0; i < CMD_BUFF_LEN; i++) buffer = 0;
if ((flag_interruptclock == 1) || (flag_pir == 1))
{
if(flag_conflict == 0){
WIFI_SEND();
flag_interruptclock = 0;
flag_pir = 0;
}
}
but now it never triggers WIFI_SEND. I'm not sure what am I doing wrong. I'm attaching my whole project. Could anyone give me a hand?
Show LessI am new to PSoC and using PSoC4 CY8CKIT-049 kit. I tested it with LED blink program and its working fine. Now I tried to see result for ADC but I am getting error- Bootloader reported error 'Packet data invalid': The packet sent to the bootloader does not conform to the required packet format.
The program I wrote is a simple one. Programm inside for loop is:
aVal = ADC_GetResult16(0);
LED_Write(!LED_Read());
if(aVal> 2047) aVal = 2047;
if(aVal<1) aVal = 1;
aVal == aVal/2 +100;
CyDelay(aVal);
Show Less