PSoC™ Creator & Designer Forum Discussions
Hi,
The built in API CyBle_AesCcmEncrypt shows a 27 byte size limit for the data encryption. Is there a reason that 27 is the limit? Any way to bypass?
Thanks, Dave
Show LessHi everyone,
Me and my colleague would like to work on the same project or Workspace, on two different Windows computers.
We want to develop different pieces of the same project or Workspace, so that we can develop it at the same time and in much less time. Can someone help us?
Is there an option that does it on PSoC Creator 4.2? It's important for us to do it so we can develop a project much faster.
I have attached you a PSoC Creator 4.2 setup.
Thanks in advance,
Daniele
Show LessI'm a newbie to Cypress, I'm picking up where other people left off...
When using 4.x cyelftool, what causes this message to occur? This message does not occur using the 3.3 version of the tool on the same input file.
Show LessHello.
Can anyone help with this:
The code below is where the problem occurs.
uint8 frameBuffer[600][400] __attribute__ ((aligned(),section(".frame_buffer")));
And, It is my "Custom Flags".
-Wl,--section-start=.frame_buffer=0x20000000
Below is my error message.
This error does not occur in Creator v3.3 and i confirmed that it is not related to GCC version.
I don't know why occurs build error in Creator v4.2.
Show LessI've been using PSoC Creator 4.2 on a project for 4 days with no problems. When I started it up on the fifth I was greeted with scores of "Object reference not set to an instance of an object" errors. Now I can't even create a new project. The previous project opens fine in PSoC Creator 4.1. Tried re-installing PSoC Creator 4.2 but that made no difference.
.
Show LessHi
We've been using CyBle_AesCcmEncrypt and CyBle_AesCcmDecrypt and were getting some random NOMEM global interrupt hangups.
It turns out that you have to check the BLE stack state before calling this function, however the documentation doesn't say this.
So some feedback for users who find themselves in a stack trace containing things like llh_load_encryption_key, wondering how a strh r0,[r1, #0] is causing a memory issue when all parameters are correct and there is sufficient stack and heap available, might find that they need to do something like this:
while((CyBle_GetBleSsState() != CYBLE_BLESS_STATE_EVENT_CLOSE));
eret = CyBle_AesCcmEncrypt(edActiveKey, edActiveNonce, data, chunksize, out, intmic);
At least, this works for me.
Perhaps Cypress can comment on the recommended way of calling the function or checks to do before executing?
Thanks, Dave
Show LessHi,
I've some projects which build fine, but they're always throwing some kind of "ghost" errors. Those errors are from components which don't exist anymore in the design or from design errors (e.g. forgot to connect an input terminal).
From the forum, there are some other topics regarding the same issue:
https://community.cypress.com/thread/36109
https://community.cypress.com/message/146504#146504
On the first mentioned topic, Cypress stated that this will be investigated, but the topic has been locked. Any news on this? Deleting the CyFitter file as mentioned on the 2nd post didn't help.
Regards
Show LessI really enjoy working with PSoC and Creator 4.2. However, being someone who doesn't know when to keep his trap shut, there's a few things I really miss. Maybe they already exist - I just haven't worked out how to find them yet.
So, anyone think these might be useful additions to PSoC Creator?
1. Separate button for hardware compiler only. So you can quickly see what reassigning pins will do to the (analogue) routing.
It would be really nice to move pin placement and see what impact it has on the analogue routing but without having to wait for the whole compilation process to complete.
2. Sometime Build does not build all the changed files. You can click debug, see a build but get the old code running.
If I click 'Debug', it does a quick build and run but doesn't always take into account code changes. I have to do a 'Clean and Rebuild' to be certain.
3. Have a facility to print out the pin diagram with the assignment table.
I generally press 'Print Scren' then use mspaint.exe to crop and print.
4. A utility that assesses the design for the lowest-cost part that will accomodate it.
I'm using a CY8C5888 for this design but maybe I could use a cheaper device in the same package. Nice to have a utility that finds the most basic part that will hold the design without having to go through them one-by-one.
5. A PDF with all possible connections for programming port configurations and bullet points to help choose.
Just an app note to make it clear whether pull-ups are needed, which pins are optimal to use, etc. It's in the datasheet, of course, but a more readily accessible source of debug-specific info. How about having the debug connection as a 'component' that can be configured on the schematic just like other components with its own datasheet?
6. A debugging 'pause' point. It stops, updates the watches and then continues.
This I'd really like. It would be nice not to have to click run or press F5 when you want to run the code but also get regular updates to the watch variables.
7. Add c preprocessor #define as text to schematic page so that enabled pages can activate associated code.
Writing test programs for hardware peripherals, it would be nice if one could put a text line like '#define TESTTHISPAGE' actually on the schematic page so that if it is disabled, the code bounded by #ifdef TESTTHISPAGE ... #endif elsewhere in the project is also disabled.
Thanks for reading this. Sorry if I've posted it to the wrong place.
- Richard.
Show LessHi,
I am using PSoC Creator 4.2 to build a project sample code from Cypress (CYPD3171-24LQXQ_cla). I need to use my debugger (Miniprog3) to step through the code. At first the "Debug" button in the software is greyed out, but after disabling the "bootloadable" component in the project, I am able to use the debugger.
However, when I start my debugging session, I get the following error:
Error: dbg.M0023: There was an error while programming the device: PSoC Programmer reported error (100 - FAILED! Hex File parsing failure. Checksum of Main Flash does not match Hex Checksum record)
Is this checksum mismatch due to the fact that I removed the "Bootloadable" component and now the program size doesn't match the expected checksum? If so, how do I re-calculate/re-config the expected checksum value?
Thanks,
Jonathan
Show Less