PSoC 4 MCU

Hello, I am testing a new design based on MagSense using a CY8CKIT-148 evaluation board. At the beginning everything was working but to use the tuner sw I had to update the firmware of the debug interface MCU on board. I updated it following the kit instructions apparently with success. After that I was not able anymore to program and debug the on board PSoC 4 MCU.

And I am not also able to update/program the on board firmware (I mean that of the hw debug interface MCU).

How can I re-flash that MCU?

Thanks,
Massimo

Hello,

Looking at J9 at SCHEM1 seems to represent J9 on SCHEM2 which seems to suggest that depending on the jumper of J9, the PSoC 4 and PSoC 5LP chips will be powered by either the USB's 5VDC or the 3.3VDC via the LDO power supply system. The jumper chosen on J9 will represent the VDD volatge throughout the parts connections. (Please confirm if I am assuming this correctly!)

In SCHEM3, we have VCCD??? Where does this come from???

Thank you 

All help appreciated

r

Hi 

I have a simple project with a pwm timer driving direct a GPIO out pin.

I have a motor driver on this pin. 

My problem is when the chip power up the pin state is low, which means that the motor driver is at max speed. The max out put is there until i initilze the PWM timer. 

How can i set the pins so they allways start up in tristate until at initialize them ? 

I tried to connect CY8CKIT-42-BLE-A with CYALKIT-E04 by reffering the CYALKIT-E04 S6AE102A and S6AE103A Evaluation Kit Guide, A.3: Programming Using PSoC programmer.

But the firmware programming of BLE dongle was failed due to this error: "The hex file does not match with the aquired device". The hex file I used is BLE_Dongle_256K.hex. 

I don't know the cause of the error. Should I use other hex file?

Also, I would like to send door sensor data over BLE to dongle by using the door sensor included in the sensor board of CYALKIT-E04 kit.

Do I need other firmware program for that?

If anyone has some examples, I would appreciate if you share the example.

I am very grateful for your advice. Thanks in advance.

Shu

Hello everybody,

I encountered some strange behaviour using UART.

I'm developing on a CY8C4126AXI-S445. I needed some debug outputs, so I decided to use a UART bridge project, which has already worked before.

As a bridge I use a CY8CKIT-059. It has a UART_in and a UART_out.
this is the entire user code in main.c:

int main(void)
{
  CyGlobalIntEnable; /* Enable global interrupts. */
  UART_in_Start();
  UART_out_Start();

  uint8_t uartChar;

  for(;;)
  {
    /* Place your application code here. */
    uartChar = UART_in_GetChar();
    if(uartChar)
    {
      UART_out_PutChar(uartChar);
    }
  }
}

However the problem seems to be in the CY8C4126AXi-S445.
I wanted to put out "Initialisation\r\n" during initialisation.
Put what I saw on my terminal was something like this: Initia[][][]\r\n

I tried different Texts and depending on the length the rectangles appeared at different spots. I tried changing several UART parameters like baud rate, oversampling etc. All with pretty much the same result.

I added texts and noticed that this error only occurs on the first output command.

I also noticed, when I put the command into the main loop, there is no error. So it only happens during initialisation. Has anyone else observed this behaviour before? Has anyone a solution to this problem?

Thanks for your help.
Please let me know if you need any project files.

Hello, further to a question I asked (https://community.cypress.com/t5/PSoC-4-MCU/Reversing-proxmity-sensing/m-p/270896#M39101).  After weeks of testing, I found that the CapSense values are very sensitive to the voltage of the power supply.  At 3.8v the raw value could be 8000, while 3.7v could be 1000 and even lower when approaching 3.6v. 

Since my system runs off a 3.8v battery as the power supply (connected to VDD of CY8C4245 directly). Is there any way to get a stable value from CapSense even the supply voltage drop a little? Like an internal regulator or something?  

Thank you!

Hi all,

We are facing one issue of hanging touch panel.

When capsense is not working, other ISR is working.

How can I detect a fault in cap sense ?

How to get an error code in this situation?

How to solve this issue ?

Hi,

Regarding the GND electrode and the shield electrode, the mesh width and the distance between the meshes are described in the reference manual in a fixed manner.
What is the rationale for this value?

Also, what are the negative effects of using a solid pattern instead of a mesh for the shield electrode?

Regards,

Naoaki Morimoto

Should I use the api "CapSense_Stop()"  before  "CySysPmDeepSleep();" and after WDT wakeup use  "CapSense_Start()"?

If I don't use these two api ,    CapSense_NOT_BUSY == CapSense_IsBusy()  can't  pass. When I use the api  "CapSense_Start()"  ,the current increase 200 ua.