PSoC™ Creator & Designer Forum Discussions
In the ICE Cube user manual there is no spec shown for allowed
current consumptioin on target board, of 250 mA. Document should
be updated.
Regards, Dana.
Show LessI am using an application with a simple master (PSOC) and a slave device.
When I issue R/W commands to Slave, I accumulate the return values from the I2C API,
and then evaluate this for > 0 (errors), eg. looking for an error, to implement error handling.
If I disconnect clock or data line the I2Cm gets stuck in a I2Cm API, a function called clockstretch2.
So net effect is to take down entire application.
Code being used -
unsigned char I2Cok = 0;
I2Cok = ( I2Cm_fSendStart( SLAVADD, I2Cm_WRITE ) == 0 ) ? 1 : 0; // Send start bit
I2Cok = ( I2Cm_fWrite( memadr ) == 0 ) ? I2Cok + 1 : I2Cok; // Send command to read Tobject
I2Cok = ( I2Cm_fSendRepeatStart( SLAVADD, I2Cm_READ ) == 0 ) ? I2Cok + 1 : I2Cok; // Send repeat start bit
rxBuf[ 0 ] = I2Cm_bRead( I2Cm_ACKslave ); // Read low order byte
rxBuf[ 1 ] = I2Cm_bRead( I2Cm_ACKslave ); // Read high order byte
rxBuf[ 2 ] = I2Cm_bRead( I2Cm_ACKslave ); // Read PEC
Code works fine, until I disconnect a clock or data line to I2C slave, or if a loss of power to slave
occured. Clearly this should be considered a defect in I2C API implementation, inability to handle
a HW failure. I suppose a workaround would be watchdog, but that I think is a poor choice.
Is this also case for Creator ?
Regards, Dana.
Show LessHello,
PSoc creator has an issue where so-called unused variables are optimized out despite the fact they are written to more than once. C compilers are not supposed to do this. Is there something I can do without having to turn off optimization?
Show LessSeveral of the forum posters suggest periodically added features that
would be nice in Designer or Creator. But I do not see any Cypress
person responding, yay, nay, to the posts. At least a "we saw it....."
Would it be possible to do this ?
Regards, Dana.
Show LessI had work some weeks on a SD Card interface module for PSoC 3, the module is not stable yet, i get read and write operations, read operation work always fine, but write operation sometimes corrupt the file system. In this post you can find a binary hex file to program the PSoC 3 module in the CY8CKIT-001. The firmware contains a test program for any sd card capacity, the test program list the directories and files on the root directory, no write operation is implemented in the test program to avoid cases where any sd card could be damaged. All the information is transmited using the serial port in the development kit, working at 115200bps.
To get the test program working and dont damage the SD Card the development kit MUST be working at 3.3v. The SD Card pins can be conected directly to the pins of the PSoC. The pin conection im using looks like this:
SDCard DO pin to P0(1)
SDCard SCK pin to P0(3)
SDCard DI pin to P0(4)
SDCard CS pin to P0(6)
RX to P1(6)
TX to P1(7)
Get the program running is easy, you only have to program the PSoC 3 device, plug the RS232 port to the PC open a terminal, push the reset button and the directory listing will start.
Im sorry that source code is not avaliable because a commercial project is being developed using the module im creating, i hope psoc creator comes soon with the SD Card module by default, will be nice to have a customizer for easy configuration.
Victor Andres
Show LessWhen users configure analog chains on single supply applications,
confusion often rises as to offsetting and dynamic range and input
common mode range. Same is true of single ended vs differential
applications, like A/D as example.
PSOC designer has one component (may be more), Comparator, that shows
a graphical picture of analog I/O behaviour.
Why not in datasheet config for an analog module show a graphical picture,
for given G and offset, ref mux, and differential settings, show allowed CM range,
including, if applicable, RRIO effects, eg. capable or not capable.
So a basic pic of input range, output swing, for component settings. And show
relationship between input and output, including saturation region.
Regards, Dana.
Show LessWhen users configure analog chains on single supply applications,
confusion often rises as to offsetting and dynamic range and input
common mode range. Same is true of single ended vs differential
applications, like A/D as example.
PSOC designer has one component (may be more), Comparator, that shows
a graphical picture of analog I/O behaviour.
Why not in datasheet config for an analog module show a graphical picture,
for given G and offset and differential settings, show allowed CM range, including,
if applicable, RRIO effects, eg. capable or not capable.
So a basic pic of input range, output swing, for component settings. And show
relationship between input and output, including saturation region.
Regards, Dana.
Show LessOne of the most common errors users make is to not issue a module_x_start()
command. Causes lots of forum posts and Cypress employee time lost.
Maybe a check on this and a warning issued ?
Look at other common errors as well ? GPIO settings inconsistant with code use ........
If this takes a lot of build time, eg. additional scan of code base, make an option
in the compiler properties.....
Regards, Dana.
Show LessOne of the most common errors users make is to not issue a module_x_start()
command. Causes lots of forum posts and Cypress employee time lost.
Maybe a check on this and a warning issued ?
Look at other common errors as well ? GPIO settings inconsistant with code use ........
If this takes a lot of build time, eg. additional scan of code base, make an option
in the compiler properties.....
Regards, Dana.
Show Less