We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hi all, I am new to 32bit computing and I have choosen lpc2148 to start with. I am using uVision v4.00... I have a LPC2148 dev board for which i have written a led-blink program and certainly it doesn't works. Now what I have done is.
1. Created a new project. uVision asked for adding "startup file" I said yes . 2. Wrote a down to earth simple led blink program. 3. Build hex without error or warning. It 'ran' with meaningful results in debugger too. port getting written and erased, all's well. 4. Downloaded the hex file to my LPC2148 board with philips utility software. AND IT DOESN't WORKED. DID IT AGAIN N AGAIN. NO SUCCESS YET !
My only question is Does the startup.S file that is added automatically by uVision WORKS ???
"Include the project configuration values" What that refers to ? IS it "options for target1 WINDOW " ? I have checked that every setting is same in the "options for target window". The only thing that was different was the file count in respective directories. In my custom made project directory(led blink project) there are 16 files including the hex. In the sample project directory(led blink sample project ) there are 25 files including the hex.
The extra files have extensions as " sct, BAK, uvopt, ". I think "bak" files are just created by uvision as the sample project was originally compiled via a older uvision version. The led.sct is "Scatter-Loading Description File generated by uVision" and The led.uvopt is a xml file.
Where else can the difference be ?
There are multiple tabs for "Options for Target" - have you compared the settings for all tabs?
Do you have a JTAG adapter, so you can debug?