This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LPC2468 uVision bugs

Current setup:

LPC2468
uVision3 V3.1.0.903 with flash magic
LPC2300.s as the start up file

We have a simple C file to set GPIO's as outputs and set them high. It compiled correctly and was programmed into the ARM successfully. The voltage measured on these GPIO's was a strange 2.3v where it should have been 3.3V. Some of the GPIO's do have a correct 3.3v, but not all of them. We then used a LPC2400.s startup file from the trial version of uVision4 to compile and program. The same issue persisted and, in addition, the software debugger would throw an error executing the startup file.

Using the above C file along with the trial verison of uVision4 and the LPC2400.s startup file, the GPIO's behave as expected.

We are using uVision3 because that is what our license covers and we have gone over the file size limits of the trial version. Our small school budget does not allow us to renew our license.

-Students from the University of Florida

Parents
  • Check if the addresses for the GPIO registers are correct in the header file for the processor. Same for all registers used to control if pins are GPIO or mapped to peripherial devices like I2C, SPI, ...

    2.3V is a possible value if the GPIO is set as input and with internal pull-up/pull-down deactivated.

    Since you do have a working setup and a non-working setup, it should be possible to compare the contents of the header files to see what changes there are.

    You don't tell what GPIO works and what GPIO doesn't work, so it's hard to tell what potential register accesses that may be involved.

Reply
  • Check if the addresses for the GPIO registers are correct in the header file for the processor. Same for all registers used to control if pins are GPIO or mapped to peripherial devices like I2C, SPI, ...

    2.3V is a possible value if the GPIO is set as input and with internal pull-up/pull-down deactivated.

    Since you do have a working setup and a non-working setup, it should be possible to compare the contents of the header files to see what changes there are.

    You don't tell what GPIO works and what GPIO doesn't work, so it's hard to tell what potential register accesses that may be involved.

Children