PSoC™ 4 Forum Discussions

 Hi,

Are there any examples of how to set EM_EEPROM to a specific location, and then change that location after a certain amount of writes?

My EM_EEPROM is set up like this:

// EEPROM Array

static const uint8 CYCODE eepromArray[ARRAY_SIZE]= {0};

// Sets up data structure for EEPROM storage

struct eepromData

{

    uint8 mode;             // Running mode

    uint8 program;          // Program selected to run in program mode

    uint8 speed;              // speed of programs

    uint8 brightness;       // brightness of colors 0-10;

    uint8 spectrum;         // color based on spectrum location    

    uint8 white;            // white level for spectrum use

    uint8 channels;         // stores whether there are 3 or 4 channels (RGB vs RGBW)

} dataLocal;

And written like this:

// Writes EEPROM structure into memory

void WriteEEPROM()

{   

    cystatus status; 

    // Writes EEPROM data

    status = Em_EEPROM_Write((void *)(&dataLocal),(void *)(&eepromArray),ARRAY_SIZE);

}

Thank you,

Tom

So I've browsed to forums, watched the videos, and this great tutorial, which I've learned from valuable info from all, but I want to ensure that a non-devkit application is going to work correctly.  I'm using a 222014 chip.  I have the module all well, and both have VREF pads with a 1uF bypass cap attached.  I'm running the bare chip on a CR2032 (3.3v), my ADC component is set to Internal 1.024 volts, bypassed, and my vref pin from the ADC is set to P3.6.  Measurement code is ready, using the script in the tutorial.

So, with that setup, would I:

a) connect pad P3.6 to pad VREF and done?

b) Have a voltage divider, from the CR2032, down to 1.024V into pad P3.6...?

    b.1) AND pad P3.6 to pad VREF?

c)  All sorts of NOPE, and better ideas?

Hi there!

I've searched quite a lot for my I2C-Problem wihtout any success...now I hope you can help me!

It seems that the I2C in MultiMasteSlave-Mode has kind of bug or undocumented state:

When I use the API MasterWriteBuf and there is no slave on the bus, the I2C (actually the whole device), "dies".

Acutally it gets stuck in an endless loop calling the I2C_ISR.

Looking at the Pins, the Master sends the address, doesn't get any ACK of course, and then holds the CLK low and loops inside the ISR.

And due to the loop, there is nothing I can do...(ok, a watchdog would do the job, but that is not what we want)

Setting the Component to MultiMaster without slave, everything works properly: MasterWriteBuf returns 0x00 and then MasterStatus returns 0x22, which is "write complete" and "addr not acked" - perfect!

Does anybody has any idea what is wrong? Am I missing something or is it a component bug?

Thanks!

UPDATE: I think it is something like a BUG/unhandled condition. Writing to your own slave-address causes the I2C to get stuck, as the slave-code seems to corrupt the status. I know this seems strange, but I am using the I2C only as a physical layer for a protocol, where every device has the same slave-address.

WORKAROUND: before writing to the bus, change the slave-address to something safe...and after the master is done set it back to what you want!

Maybe this could be handled inside the component in the future....i.e. prevent it from reading/writing to itself...

Part to program = CYBLE-022001-00

Using the MiniProg3 programmer and referencing the ppcli app notes.

Example : Programming a Chip

OpenPort MINIProg3/848E4756090B “c:/Program Files/Cypress/Programmer”

HEX_ReadFile "c:\\CYBLE-022001-00.hex"     //Does this specify the device being used???????

SetAcquireMode “Power”
Acquire
Calibrate
EraseAll
Program
Verify
VerifyProtect
Protect
CheckSum 0
HEX_ReadChecksum

 I have purchased and received the new BLE kit but have not yet dug into the features or tried to run it up.

Just had a quick question that someone who has already worked with it may be able to answer.

Does the module support SPP and are there any sample Android apps for routines available?

ie. I want to pair smart phone with the PSCO BLE device and transfer serial data in either direction.

I currently do this with an external Sena OEM BT module but would like to investigate lowered cost using the BT built into the new device.

Thanks

Hi,

Im trying to get the TFT touch screen v2.0 to work with my psoc 4 development kit but to no avail. I tried to follow both tutorials 72 and 73 but both didnt work. All i see is a white screen. I hope someone out there could share me a working code or tips to make this work.

Thank you.

Amos