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

need help:newbie

I am new to this microcontroller;actually to microcontrollers in general.I am a student.I need help for my final yr project.How do I interface philips lpc2148 with my battery charger circuit?can anyone help me?

Parents
  • the project description says arm controller and the supervisor had suggested the controller lpc2148.the battery charger should draw power from the usb.

    i understand its "my" project sir but i am not very familiar with the microcontroller.I am struggling to understand the architechture and have been reading the datasheets for more than 3-4 weeks..with not much results.

    we have only studied 8051 micrcontroller in our coursework.

Reply
  • the project description says arm controller and the supervisor had suggested the controller lpc2148.the battery charger should draw power from the usb.

    i understand its "my" project sir but i am not very familiar with the microcontroller.I am struggling to understand the architechture and have been reading the datasheets for more than 3-4 weeks..with not much results.

    we have only studied 8051 micrcontroller in our coursework.

Children
  • "the project description says arm controller"

    That is not a project description - that is just the name of a component!

    You need to start with a proper definition of your project Requirements - you cannot possibly solve a problem before you know what the problem is!

  • "the supervisor had suggested the controller lpc2148"

    If he suggested it, then he must think that, by the final year of this course, you should be able to do it.

    "I am struggling to understand the architechture and have been reading the datasheets for more than 3-4 weeks"

    A final year project shouldn't be a walk in the park - you should expect a challenge!
    If you are really struggling that much, then you need to discuss it urgently with your supervisor!

    "we have only studied 8051 micrcontroller in our coursework."

    So why not use one?
    Part of your project report will need to discuss how you decided on the processor to use - "my supervisor told me" will probably not gain many marks...

  • "the supervisor had suggested the controller lpc2148" [but] "we have only studied 8051 micrcontroller in our coursework"

    seems like your supervisor is offering you bit of real world taste here. If you really want to get to the market and be a embedded developer, you will face new processors / system platforms quite often.

    There is a daunting pile of datasheets to read about the ARM. You are probably not reading the right ones.

    The chip datasheet will give you a description of each peripheral and detailed configuration information, but it assumes you are familiar with the ARM7 architecture. You should read the ARM ARM (architectural reference manual). Read at least chapters A1 and A2 (Introduction and Programmers Model) to get the grand picture on the ARM architecture, then proceed to reading the chip datasheet. That will give you the required hardware knowledge to make decisions like interfacing methods with your circuit.

    All these manuals treat the processor at the lowest level. Unless your 'project description' requires you to write the firmware in assembly, you will use a C compiler. Both NXP and ARM have examples on how to do a lot of simple things and setup each peripheral in C, and you can program and simulate them in uVision.

    Even with the very scant information you gave us, there are several issues on your project that you need to address. For example, the USB port has limits on Vdroop and on max. current that can be drawn. If you are allowed to use a charger IC, there are ready-to-use chargers that can be powered from the USB.

    I suggest you to set up very small programs and test them in the simulator to get a feel of programming for the ARM. You can simulate almost all peripherals without any real hardware, so you can use this controlled framework to learn how the peripherals are configured. Restricting the scope of each step makes incremental implementation easier.