「ARM GCC 5.4-2016-q2-update」、「ARM GCC Generic」、「ARM MDK Generic」
実際にBuild出来るのは「ARM GCC 5.4-2016-q2-update」のみです。
２．「ARM GCC 5.4-2016-q2-update」を最新バージョンに変更することは問題ありませんか？
３－２．BLE OTA External Momory対応のプロジェクト（２つのプロジェクトから成り立つもの）もEXPORTで出来るのでしょうか？Show Less
I am using the CYBLE222014-01 in an application where I need to put the entire module to sleep in the lowest possible power mode. When in this mode, there is no BLE activity or MCU activity other than an accelerometer programmed to wake the module up with motion. Then the module will do a rest and start from the beginning.
The purpose of this operation is to store the device on the shelf for several weeks in this ultra sleep mode and then wake up when the device is moved.
The battery is 300mAH. Reading through all of the datasheets for this module, if both the BLESS is in deep sleep mode and the system MCU is in hibernate, the current should only be around 25uA. I am drawing 260uA and cant see why.
The only other two devices on the board are the accelerometer and an eeprom. Both of those combined draw less than 10uA.
I have confirmed by reading the BLE state prior going into system hibernation, it comes back as BLESS_DEEPSLEEP. I know the MCU is going into hibernation because the board will auto reset when it receives the interrupt from the accelerometer. Only hibernation mode will do an auto reset. I have also tried CYBLE_Stop(). It gives the same results.
I have changed the SWD pins to GPIO and that didnt change anything.
I am using a timer, I2C, ADC and PWM modules. I run the stop function for all of those before going to sleep.
The I2C pull ups are 2.2K to 3.3V supply.
Anyone have any ideas as to what is causing the extra current?
I am really struggling to implement a fixed duty (50%), variable frequency pwm output (controlled by a pot). - I am trying to generate a variable (+modulated) clock frequency for an external chip.
The only way I seem to be able top do it is by adjusting both the period and compare (as period/2) simultaneously, which feels a little clunky.
would anyone have any other suggestions how this could easily be done?
Any pointers how this might be done would be greatly appreciated.Show Less
Hi Cypress Developer Community,
Customer Support directed me here to determine if there is a recommended substitute for CY8C27543-24AXI .
I appreciate you help.
Liner ManufacturingShow Less
I am using PSoC4 CY8C4247AZI-M485 to measure 8 currents and i also want to measure a thermistor. I can not seem to get PSoC to build this is there another way I can do this?
Does CYBLE-022001-00 module passed TUV certification？
IF not, what is the tool and guideline about Bluetooth fixed frequency test？
Can we use MBT for test？
I later realized that EXTCLK could not be entered into the PLL.
Eventually, a crystal oscillator will be connected to the ECO.
Regarding the current situation, is it possible to input a rectangular wave of a crystal oscillator with the same amplitude as the power supply voltage of the PSoC 4100S Plus to exco.eco_in on P0.6?
I am using the bootloader host to program the KtiProg to be an oscilloscope/function generator as shown in this project outlined here . It works well for me, but there is a problem when some of my students try it. (The tcl program that controls the Ktiporg Scope can not find the com port assigned by bootloader host and crashes.) It can happen on Intel and AMD machines.
After some debugging it looks like the bootloader host uses COM3 no matter what. When it works I get:
"Selected device: Intel(R) Active Management Technology - SOL (COM3) - UART
Generic Serial Port " after loading the program into the kitprog.
When it is does not work (some students) IT will program the kitprog but it will give:
"Selected device: Standard Serial over Bluetooth link (COM3) - UART" It looks like COM3 has been assigned to a blue tooth device. Can you change which port it uses? Bootloader host gives no error, but the software that uses the Ktiprog as an oscilloscope/function generator crashes when it tries to use it. I have even programmed the CY8CKIT-043 and got everything working on one machine, only to have it fail when trying to use the software that controls the KitProg. Maybe this is a Windows issue with COM3?