PSoC™ 4 Forum Discussions

Hello,

In case of the thread below, we can read uint8 array allocated in FLASH, we can get "test" variable that not used anywhere.

Placing uint32 array with compiler optimization "size"

volatile int32 g_vsin[360] __attribute__ ((section (".FlashData"))) = {}

volatile int32 test;             // for debug

       ...

test = g_vsin[100];          // break point for debug

we would like to let the linker allocate the array to FLASH. So, we will use

"__attribute__ ((aligned(CY_FLASH_SIZEOF_ROW)))".

If we use like below, the array cannot be read in bytewize.

const int32 g_vsin[360] __attribute__ ((aligned(CY_FLASH_SIZEOF_ROW))) = {}

volatile int32 test;             // for debug

       ...

test = g_vsin[100];          // break point for debug

And if we use like volatile, the array is allocated in RAM.

volatile int32 g_vsin[360] __attribute__ ((aligned(CY_FLASH_SIZEOF_ROW))) = {}

or

volatile const int32 g_vsin[360] __attribute__ ((aligned(CY_FLASH_SIZEOF_ROW))) = {}

Is it possible to read it allocated in FLASH in bytewize with compiler or linker option  with GCC or something?

Best regards,

Yocchi

I have a project where one of the IC need 31.25kHz oscillation to operate.

Until now I used a crystal on that device and used 4200 micro as my host controller. For low power I put the controller to deep sleep and it was woken up by interrupt from the other device.

Because the crystal is getting harder to source I wanted to generate the 31.25kHz from the controller. Because 4200 I was using only had 2% accuracy due to RC operation, I changed model to 4200 L and connected 24MHz crystal.

Using a PWM output to pin, the 31.25Khz signal is generated and the circuit works. However, I need to put the micro into a deep sleep mode to increase battery run time.

How can I keep the 31.25kHz running while 4200L is deep sleep and also, how can I get it ti wake periodically (every 1 second) to perform some non-interrupt functions that need to be done?

Thanks

Hello,

According to the history of CapSense component Ver7, version 7 is not compatible with the previous version.

Please tell me the API changed from version 6 specifically.

Component Changes

”This version is not backward compatible with the previous version. We tried to keep the established API, but your design may need to be updated to operate with v7.0.”

Best Regards,

Naoaki Morimoto

Hi everybody,

I'm working on CYBLE222014, to read data from an UV sensor from Vishay (VEML6070). This sensor has one write register(0x70>>1) and two read register(0x71>>1 and 0x73>>1), for UV MSB and LSB. In the  datasheet they say to inizialize the sensor with 2 step: first read ACK register(0x18>>1) and second write 0x06 in write register(0x70>>1); than you can read the UV value from the 2 registers, but if i run my code i read only 0x0000. I think i make a mistake in the read function, but I checked many times and seems OK.

Any idea to solve?

Best Regards

Francesco

There are two definitions with similar names but different values in CyBle_StackGap.h - CYBLE_GAP_ADDR_TYPE_PUBLIC (value 0), and CYBLE_GAP_PUBLIC_ADDR. (value 2). The structure CYBLE_GAP_BD_ADDR_T also has a field named type, which should be 0 for a public address and 1 for a random one.

I would like to clarify how I can correctly use those definitions - when or where is each one of them intended to be used?

Hi All

I have the UART to Ble central code running on a CY5677 dongle along with the UART to Ble peripheral code on a CY8C4248LQI-BL583.

I have a 2 CoolTerm windows on my PC, one connected to the CY5677 dongle and  the other connected to the CY8C4248LQI-BL583. module.

When I type in the dongle window I see the characters in the module window , and vice versa.

HOWEVER

When I uncomment

    #define     LOW_POWER_MODE

in the peripheral code main.h and rebuild, I only see traffic in the dongle to module direction.

I cannot see any traffic in the module to dongle (peripheral to central) direction.

Does any body know why ?

Tim

Hello All,

I'm new to 4100s plus. I'm trying to achieve a 'storage' mode for a battery powered application. It's a very simple circuit from a CR2032, a sensor and a couple of LEDs.

I've got the consumption at between 1..2mA and I'm disappointed. My expectations were <100uA and the datasheet seems to indicate this is possible.

The application is in deepsleep for 30 seconds at a time, then wakes to check the sensor @ 1mA for 270ms. My CR2032 is flat in 10 days at the moment.

I'm using the Capsense Low power example as a starting point and it uses the WDT interrupt to wake from deep sleep. Capsense is turned off, was removed from project, not needed.

Any thoughts?

What is the 4100S plus family capable of?

Project is attached. Readable, but it's a mess, still need giant cleanup before going to client. Don't judge me.

Thanks,

Brent.