If a pin is configured as "High Impedance Digital", as an input, there should be

a caution about the pin potentially drawing input current if left floating.

If this is true docs to be affected, TRM, AN72382, AN60580, AN77900.

Bob, who is the contact inside Cypress to handle this ?

Regards, Dana.

 Ok here we go:

*** ERROR L220: INVALID INPUT MODULE

    MODULE:  .\DP8051\DP8051_Keil_903\Debug\UM6 Sensor Test.lib (-----)

*** Internal Reference: processlib3The command 'LX51.exe' failed with exit code '3'.

If I put Browse Information to FALSE in the Compiler's Build Settings it

links correctly but cannot (obviously) debug otherwise it gives that error.

This is weird !

On a build I am seeing this error:

prj.M0120:expected '=', ',' , ':', 'asm' or __attribute__' before typedef

This is on line 41, stdint.h

I am trying the example bootloader from AN73503.. using a 5LP

I am using W8.. is this a W8 error waiting for the next release?

--thanks

  -chane

After upgrading to PSoC Creator 2.2 and rebuilding a project I get the following message when attempting to program the device:

"This device was recognized, but PSoC Creator does not support using it at this time"

is this chip discontinued?

flypfc.net/jjfiles/object_error.png

Not a very helpful error. Any ideas?

Thanks.

 An LED driver component for matrix and 7 segment displays.  some of the feautres are:

1.) The component supports 1 to 8 commons.  
2.) The segments and common signals can be inverted for use with driver transistors or for common anode / common cathode displays
3.) The brightness of each common can be controlled with an optional PWM built into the component.
4.) A macro is included that breaks out all the signals to make it much easire to get started
5.) API are included that make it very easy to display numbers (signed decimal and hex) as well as strings for use with 7 segment displays.
6.) All hardware based solution, no interrupts or CPU time required.  "set it and forget it" operation.

My first component submitted to the community!

I  have an irritating issue with PSoC Creator version 2.2 and PSoC5 running under Windows 7. When I am in one of the editors and want to proceed to debugging I click on the debug icon (looks like an ant) and the software does its own thing (compiling when necessary etc.) and then moves into the debug environment.  The problem is that maybe 60% of the time, it doesn't set the pointer/ProgramCounter to the first instruction in the main procedure, it simply opens a Disassembly tab and seems not to place the ProgramCounter anywhere, or maybe above the first line in the window (I can't tell- there is no yellow arrow). Although I am sure it is irrelevant, the first line in the debugger is:

0x00000000 <__cs3_interrupt_vector>:

 Trying to run results in indeterminate results. The only way is to click on the Reset icon (double rewind arrow) and sometimes you even need to do that twice. If you are in the disassembly window it will take you to the correct point, but still in the Disassembly tab.

I have tried to find any pattern as to when I invoke the debugger (like completely build before I start) but I can find no pattern to it.

Is anyone esle seeing this problem?