PSoC™ 4 Forum Discussions
HI
I am attempting to control an LED through an Android device by the software of App Inventor 2. The LED is part of the PSoC 4 micro-controller, which I will use the software of PSoC Creator 4
How do I make it work when I have to concatenate the psoc4 service and characteristics with the UUID?
I will ask for your help. I have included an easy-to-understand attachment.
I am using the c# dlls to create a windows pc app, and I am having trouble figuring out how to programmatically set the security level, and the bonding option. I know how to do this in the CySmart app (Configure master settings -> security parameters -> security level and bonding), but I dont know how to use the api to do this myself. Any help is appreciated.
Thank you!
Show LessI have to measure my battery level by the time that passes,
every 5 minutes dropped 1% (range of between 100-0)
How do I implement this? Are there any examples?
thanks
Show LessI want to connect my BLE peripheral (PSoC4 BLE) device with an Android-App using pairing/bonding features.
The app for testing at the android sideis the CySmart-App.
The security settings in the peripheral device are the followings:
Security mode: Mode1
Securitylevel: Authenticated pairing with encryption
Strict pairing: Yes
I/O cap.: Display
Bondinmg req.: Bonding
Encryption Key size: 16
When I used the CySmart-App running on an Lenovo Tablet (TB3-710F) with Android 5.01 or
on a Samsung Galaxy S7 with Android 7.0 all works fine incl. pairing and bonding.
If I’m running the CySmart App on anNokia8-Phone with Android 8 the pairing procedure doesn’t work.
In this case is it possible to enter the passkey at the CySmart-App on the Nokia-Phone but the device will not pair.
No error code reported. If I break up the App at the Nokia, the connection to the peripheral
will still remain (the peripheral device is not advertising) until I switch off the Bluetooth at the Nokia-Phone and switch it on again. Then the connection
breaks.
Are there any known issues for such a behavior of the CySmart-App when it runs under Android 8?
Show LessHello PSOC people!
I am currently working on a project which requires at least 16 pin interrupts, and I have been trying to implement this.
The idea is that a set of pins are grouped in one component (number of pins = 7 in the topdesign file) , and they share an ISR which will check the previous values across these pins against the current logic levels.
My 'block' of pins is labeled 'Pin_D' and I would assume that to read the pins it would be as simple as using "value = Pin_D_N_Read();", where N is the pin number I want to reference but when I try to do this I get an "Implicit declaration of function 'Pin_D_N_Read' is invalid in c99" warning.
Am I doing something wrong or should I just ignore this warning and pray that it doesn't come back to haunt me later?
Psoc 4.2 updated the em_EEPROM element. Well, not updated, completely replaced with it
with a new one that breaks all existing projects using it. It would have been far smarter (and nicer)
if they had given it a different name. The notes says it was done to meet customer expectations.
That is true if the customer expects to be put in a bad spot and have to miss a critical deadline
because the programmer thought things should be done differently.
In any case, there is a major problem I have no idea how to fix. I have implemented the em_EEPROM
element according to the new documentation. The symptom is that it reports success in writes but it
mostly erases the contents and occasionally writes one of the parameters. The first write does nothing
and leaves the values at the compile defaults. The second write destroys the contents. This all worked
fine before the "upgrade". My first choice would be to get the old version back but that does not seem to
be an option.
Initializations
static const uint8 eepromArray[Em_EEPROM_1_PHYSICAL_SIZE]
__ALIGNED(CY_FLASH_SIZEOF_ROW) =
{0x01, 0x05, 0x03, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05, 0x03, 0x00, 0x00, 0x01, 0x00, 0x10,
0x0f, 0x0f, 0x0f, 0xf6, 0xf6, 0xf6, 0xb3, 0x20, 0x05, 0x01, 0x01, 0x10, 0x04, 0x04, 0x03, 0x01,
0x87, 0x00, 0x10, 0x00, 0x12, 0x34, 0x56, 0x78, 0x60, 0x0c, 0x01, 0x00, 0x00, 0x30,0xaa, 0x55
};
In main()
returnValue = Em_EEPROM_1_Init((int32) &eepromArray[0]);
Write and read routines
uint8 writeeeprom(uint8 dta,uint8 offset){
// uint8 status = Em_EEPROM_1_Write(&dta,&eepromArray[offset],1u);
uint8 status = Em_EEPROM_1_Write((int32) offset,&dta,1u);
return status;
}
uint8 readeeprom(uint8 offset){
// uint8 volatile val = eepromArray[offset];
uint8 val;
uint8 status = Em_EEPROM_1_Read((int32) offset,&val ,1u);
return val;
}
Anybody make this work with a CY8C4245?
Thanks.
Show LessHi cypress:
Question 1: when i use CY8C4014LQI-422 for touch, as i know , P3.0/P3.1 is the debug port in SWD way, but customer choose other GPIO, as it show below,
can you tell me if there is a way to debug the chip in p0.0/p0.1;
Question2: when i choose CY8C4014LQI-422 as touch and want to communicate with other MCU like ST89C51, I want to know how CY8C4014LQI-422 communicate with ST89C51, can you provide the manual to explain it , how MCU detected in the touch of CY8C4014LQI-422 in IIC mode, and to realize low file:///C:/Users/A89114/AppData/Local/youdao/dict/Application/7.5.2.0/resultui/dict/result.html?keyword=power file:///C:/Users/A89114/AppData/Local/youdao/dict/Application/7.5.2.0/resultui/dict/result.html?keyword=consumption . thanks;
Show Less
■English
Is there a way to create a Hex file whose "User's Flash (Program)" area is All "1"?
■Japanese
「User's Flash(Program)」領域がAll「1」のHexファイル作成する方法はありますか?
本質問は以下スレッド続きとなります。
Show LessHello to all.
I have to implement a single wire bidirectional UART communication with PsSocCreator 4.1 for the PSoc4 Analog coprocessor.
Do you have any tips / examples to give me?
Thank you
Show Less