Messages

1

NXP^TM LPC2XXX and LPC17XX / Re: LPC24XX vs uTasker tutorial - irregularities

« on: May 14, 2013, 05:34:58 PM »

Got another question.

I'm using Olimex LPC2468 demo board, and I tried flashing already prepared *hex file onto my board. The file was prepared for 2478, my board is 2468. It doesn't work. I flash it using flash magic, connect my PC and demoboard via etheret cable, set my ethernet interface to a proper subnet (192.168.0.xx), but I can't neither ping nor connect via browser to the board.
Is this a normal behaviour and 2478 file doesn't work on 2468 or is something wrong again, probably my fault?

Here's the file I flash:
http://www.utasker.com/software/LPC23XX/uTaskerV14_LPC2478-STK.zip

2

NXP^TM LPC2XXX and LPC17XX / Re: LPC24XX vs uTasker tutorial - irregularities

« on: May 06, 2013, 09:50:07 PM »

Yes, it's working now without any errors.
What was the problem? I was following the official tutorial, which stated that it's *dsw file that is to be opened. Since I am using VC2012, it is *vcxproj file that should be run. Outdated tutorial + following it blindly = problems

Thank you for your help!

3

NXP^TM LPC2XXX and LPC17XX / Re: LPC24XX vs uTasker tutorial - irregularities

« on: May 05, 2013, 11:46:52 PM »

Rebuilding it doesn't do the job - still the same error codes.

Running it on VS 6 works just fine - no errors, no problems. It is still very impractical, though, as I am running on Win7, which VS 6 doesn't cooperate with.

4

NXP^TM LPC2XXX and LPC17XX / LPC24XX vs uTasker tutorial - irregularities

« on: May 03, 2013, 12:32:46 AM »

Hi all

I'm new to the uTasker. I've just started getting to know it with help of the demo tutorial. While I was going through it, I noticed that in few places (I'm only few steps into the tutorial) outcome from Visual Studio is quite different than what the tutorial states. I'm not quite sure whether it is a big deal, so I thought it would be better to simply ask. So here goes:

I'm opening VisualStudio workspace and going through basic preparations (chip type, header, ip address). When I try to execute it, there's this message:



I find it really no big deal, so I just go with it. Visual Studio builds the project just fine. But then, another error message appears on the screen:



And the reason to this is quite obvious. Files in \Debug\ folder are named differently than the uTasker expects them to.



So I just rename them, deleting "V1-4" part. But it's only a workaround, not a proper solution, because after renaming them, when trying to start the demo, this screen appears:



If I press "yes", it starts correctly and seems to be working fine (can ping it, can access the http server through browser). Anyway, I was hoping I could tweak some lines in order to get rid of these errors, as I fear that although the demo works just fine now, later on there could be consequences.
So, long story short, the question is - how to get rid of these errors? What lines to change? Where to look for them? So far I've been unsuccessful in finding the code that is resposible for such a behaviour.

If it matters, I'm using Visual Studio 2012 Express for Desktop - just as you can seen on one of the screenshots.

Many thanks for your responses
Rafal