I have a cy8ckit-059 and I would like to power it using a 3.7V battery previously used in a drone. I would like to have a button that turns the sy...
I have a cy8ckit-059 and I would like to power it using a 3.7V battery previously used in a drone. I would like to have a button that turns the system on and off from the battery and also I would like the battery to be charged when the board is connected through the USB port. As I'm really a newbie to this world can you please guide to how can I make it work if it is at all possible?
The battery has all the required protections built in so if I connect it to a 5V 1A source (regular USB charger or PC) it can be charged without any trouble.
The modification is that if the keypad input is 1, which is '1' (ASCII representation) is converted to represent hex 0x1 and then the same is written to the RTC (using Byte() API's) using Write_RTC() function. And then the time and date info is read back in the same Write_RTC() function, using RTC_Read() function.
So, now the problem that I notice is at lines 271 and 272, when I am again trying to call RTC_Read() function, the program directly starts reading and printing some random dataonto the Terminal (No input is taken) when any button on the keypad is pressed.
When the data is read back in the Write_RTC() function (commenting lines 271 and 272), everything is working fine. But, when uncommenting lines 271 and 272 (reading the RTC at some other time, after configuring), there is no response and i am not able to reach any conclusion as to what might be causing the issue.
In order for you to test this, try entering "48592331011209" (SS MM HH Day Weekday Month YY) using the keypad in the firmware (attached) as is (commented 271 & 272) and you can see that the date and time are read back properly. Then try the same after commenting lines 271 & 272, the firmware is struck.
Hope you got what I wanted to ask your help about. PS: I am a novice programmer, so bear with me a bit please.😅
I'm willing to use the SAR ADC with 12-bit resolution to sample the analog output (60KSPS/channel) of the 3 axes of the Accelerometer. Before the input, I have to filter the signal before with -30dB attenuation at half the sampling frequency.
Can I achieve simultaneous sampling for the 3 axes with the S/H? If not I have to have a minimum sampling of 180KSPS and divide it into 3 to achieve 60KSPS.
Then, I need to transfer the data of the Accelerometer to an ESP32 with SPI then transmit it wirelessly (UDP) (I think this will be another topic)
So I have multiple beginner questions. (I think I will receive some replies that I need to read the datasheet😅)
1) Can I use a power bank to power the PSOC using 5V USB? What about the Vref of the ADC (VDDA VSSA etc.) can they be powered internally? If my application is to be battery powered, do you advise me to use a battery instead of the USB powering?
2) Which ADC SAR inputs (pins) do you advise me to use? Can I use the kitprog's and work only with it? Or do I have to involve the target?
3) I have no idea about how can I filter internally the input. Can you give me some insights?
4) In the screenshot, I need to check if I forgot something, and ask you what should I put as configuration for the ADC if I power the MCU with USB. Vssa to Vdda?
The SPI connection and filtering are my next steps, just when I'm sure I'm on the right track
I am sorry for the beginner questions but I'm still learning so I rushed to post a thread to receive advice from experienced people in the field. Feel free to reply even if just to tell me go work on your datasheets or other constructive remarks😂
I'm looking to choose a PSoC component for a new design and I'm a little lost with all the PSoC families.I need a co-processor (no nee...
I'm looking to choose a PSoC component for a new design and I'm a little lost with all the PSoC families. I need a co-processor (no need for high processing capabilities), ultra-low power, to interface with all kinds of sensors, so I need configurable analog and digital blocks.
Are old components like PSoC 3 still a good option ? Aren't PSoC 5 or 6 overkill ?
Apologies for bothering you again. The current thread is an extension to the earlier thread where I was seeking your assistance link.
As mentioned in the earlier thread, I am trying to get the PCF 8563 RTC module to work with the PSOC 5LP over the I2C interface, but sadly, I am not able to do so. I have tried the I2C write and read operations as mentioned in the I2C component datasheet with the slave address changed, but that didn't help. Also, I tried the implementation mentioned in the thread which is DS1307, but that implementation didn't work out either.
I have been inventing a ultra low power IoT Bus network that will outperform RS485/UART power consumption to about 40 times at 125kbps, does not need ...
I have been inventing a ultra low power IoT Bus network that will outperform RS485/UART power consumption to about 40 times at 125kbps, does not need crystal stabilized timing, is physical fault proof, e.t.c. I want the bus network to become open standard. I have made several tests and made UDB component that performs the transaction on datapath and gate array level. Currently I have only tested it on PSoC 5 but would also like to port it to PSoC 4 with less capable UDB. The first test production evaluation boards with PSoC 5 are in production. I am looking for engineers who are willing to evaluate and participate the bus network development. More info about the evaluation board can be found at Wired IoT Bus Evaluation Kit – Tauria OÜ and Energy Consumption by Wired Internet of Things – Tauria OÜ .
The PSoC™ 5LP, PSoC 2 and PSoC 1 Forum discusses - 24-bit Digital Filter Block (DFB), 24 UDBs, DMA controller and integrating AFE, digital logic with user interface ICs with an Arm Cortex-M3 CPU solutions.