Keil uVision and PSoC5LP

Well,I re-targeted the design for a CY8C5868AXI-LP035 part (because that's what I have on my board), picked a pin with an LED on it, rebuilt, and exported to uVision. Then I opened the project in uVision and programmed the part. The LED glows on. I ran the debugger and stepped through the code. It worked fine (your delay routine is very fast and so the LED looks permanently on).

So I am not sure why you are having problems. One thing I fall for all the time is to remember that the ULINK does not power the board (it is easy to forget this because the usual USB cable to Cypress kits is strong enough to power the hardware). I apply power through the USB port on my 050 kit. It all works fine. If I unplug the USB cable then I get the following error when I try to download:

Error: Flash Download failed  -  Target DLL has been cancelled

This is not the error you reported - but I am just trying stuff out!

So, I have now changed the device back to the LP039 part in Creator and have re-created the uVision project. It is attached. Please try it and let me know what happens.

Here are screenshots of the setup screens. Do you see anything in here that is different?

Check the part number and ROM/RAM addresses.

Check you are set up for a ULINK2/ME.

Is the RAM for algorithm correct?

Can you see the device?

If you still have problems with the attached project then I suspect the problem may be with your uVision driver setup.  Let me know what happens and we'll poke at that tomorrow.

-- Mark.

Hello, thanks for testing my program. I try to run it , but get same errors.
Now comes the fun part, by following exporting guide i was able to make it work with IAR ARM, and guess what, same problem. I can flash program with no errors, debug it by steeping each line and it is working from IDE point of view. What is strange that i can't see any activity on pins even with scope, i try to use other pins, but get same result.

So now i started to think that maybe that is strange hardware problem.I am using 3.3V for all IO banks, and Vccd is unconnected but bypassed, and voltage reading is 1.8V on Vccd, same apply to Vcca, it is only bypassed to ground with 1uF capacitor.

As you mentioned earlier, i do supply power to PSoC5LP with on-board 3.3V LDO, and i don't have any problems with drivers. Also i can detect device, and i am not running debugger in simulation mode . uVision settings looks the same as in your pictures, and SWD can detect arm m3 core as you shown in pictures. I have no idea what's wrong.I checked all pins under microscope, and i have connections without any shorts. Also, if i can debug program, how can it don't work ? that is what boggles me the most

The specified item was not found.

I will try to run this code on PSoC4 and if that fails, that means i have some strange hardware non-related problem.

Hello, bottom line is this. I don't have SWD that can work with PSoC Creator and i need to be able to program PSoC5LP and PSoC4. Since i have Ulink-me, i try to export my project from PSoC Creator to uvision. When i connect Ulink-me i can't upload program because i get verification failure, if i disable that, it looks like code is uploaded, but i don't see any activity on any pin ( like led toggle or constant PWM). Same apply if i try to debug project. I can enter debugging session, step in code, but again, no activity on GPIO

Ok, since i have IAR ARM (STM32F429 is programmed via IAR) so i tried to do the same, since i can export files from PSoC Creator to IAR ARM. As with uVision, i was able to compile and even upload without any errors code to internal flash, also can debug it by stepping code and it looks like processor is running, like stepping over Delay(0xFFFFFF) take some time. But again, no activity on GPIO (like led toggle or constant pwm). IAR ARM use STLink V2 programmer as my original GUI controller

I have no idea what is wrong. That is ruff start with new platform for sure

With PSoC4 pioneer dev kit and PSoC Creator i never had any problems, it just worked and was able to rewrite code in seconds

This is what I think is happening...

1.We have a problem setting up the ULINK with PSoC.

2. The ST box is not programming all memory spaces.

We have never tried the ST debugger with PSoC. I assume it reuses the ULINK flash loader files but it is very possible that the ECC memory is not being programmed with your HW configuration. When this happens your program looks "right" in the debugger because the code is correctly written in flash. But it does not work because the pin, in your case, has not been initialized to be a strong drive output.

Please add the following line in main(), before the loop, and see what happens in IAR.

LED_SetDriveMode( LED_DM_STRONG );

If the above is right then we'll know that your PSoC is alive. Unfortunately,it will also point to a problem with the debugger probe setup, which I am not sure I will be able to troubleshoot, since I do not have one and no-one at Cypress has ever tried to use with our devices.

In an hour or so I have a meeting with our programmer team - I will bring this issue up with them and see if I can get some new ideas on fixing the uVision/ULINK problem.

-- Mark.

Well, i added this line, nothing happened.
It uses $TOOLKIT_DIR$\config\flashloader\Cypress\PSoC5LPFlashLoader_xx8.board flash loader file (attached to this post)

as uVision, IAR ARM can verify downloaded code and yes, as it turns out i have errors while uploading.

You changed the project. I assume you are now driving the LED with a PWM. Would you attach that project please? I can check there is not a new problem on my hardware.

-- Mark.

well. Since i had STLink connected, i try to run your program from post, just switched from Ulink-me to STlink, and i get same error ( i mean in uVision, not in IAR)
But, when i switch back to Ulink me and tried to run program, it worked , i don't know why.

Now, if i remove this code line it still works, anyway, thanks for help. It looks like my problem is inverse to remaining time to exam in university, as exam gets closer, problems usually disappears inviting me to stop learning and go programming

Sounds like it just needed a little kick!

I want to make sure you are really working. You have already spent too long on this! Can you try the attached project on your kit for me?

The LED should glow quite dimly because I am driving with a small duty cycle from a PWM. If you step through the code in main() you should see the LED turn on quite brightly (50%) and then go dim when I reduce the compare value for the PWM.

-- Mark.

what is pin number for this project, can't found it in uVision ( i mean, don't know where to looks, in PSoC creator is very easy to see in )
LED on my board is P1[2],
ok, i found, is P0[0], and it was connected to 2.2uF Low pass filter capacitor
anyway, recompiled to get it working on P1[2] and yes, i have low duty cycle square wave

It is good to get stuff not working, so you can debug and learn how to deal with problems. But after some time problem should go away, and this is the case for me.
Now i can start to work on my project

lets make it more fun :

void delay(int g)

{

    while(g>1)

    {

        g--;

    }

}

int a;

int main()

{

    PWM_1_Start();

     PWM_1_WriteCompare( 15 ); 

     a=0;

    for(;;)

    {

            while(a<254)

            {

                a++;

                delay(0xFFF);

                PWM_1_WriteCompare( a );

            }

            while(a>1)

            {

                a--;

                delay(0xFFF);

                PWM_1_WriteCompare( a );

            }         

    }

}

and if i try to compile it and download code to flash, i get pulsing led , what a surprise

Yes,P0[0]. I thought that would be OK. Can you see that one? I can remake it you need me to.

-- Mark.

no need to do that, it is working just fine now . Thank you very much for help and support

No problem.It's good to hear we got it working. I think it might have been a USB port hang-up.

Hope the project goes well from now on. Post a picture up when you're done!

-- Mark.

No problem.It's good to hear we got it working. I think it might have been a USB port hang-up.

Hope the project goes well from now on. Post a picture up when you're done!

-- Mark.