Actions
Forum Thread Details
  • State Not Answered
  • Replies 37 replies
  • Subscribers 484 subscribers
  • Views 3621 views
  • Users 0 members are here
Related

Where do I start  in embedded?

majorkuso

I would like to get better at building embedded devices but can't decide between avr or pic. I have the pickit 3 for pics and avr usbasp  and arduino. the arduino is ok, but I want to get closer to the metal. I would like some structured projects that I can build and familiarize myself with both the hardware and more importantly the c coding i would like to get better at my c. What would you guys recommend?

Parents
  • 0

    I'm late to the game as always, but nonetheless I'll throw in my $0.02.

     

    I started with AVRs mostly because I transitioned from Arduinos. After diving in, I realized AVR programming and Arduino programming are two different beasts. I keep my old Uno around as a test platform (like when I get a new LCD display and quickly want to see if it works, I'll grab an Arduino library for the component and give it a quick whirl) but other than that I rarely touch the thing.

     

    The Make book that you have is pretty good, but after about 100 pages the author forgets he's writing for non-engineers. Get ready to search here, Google, elsewhere for answers unless you have a hardware background.

     

    That said...if I had to start over again, I wouldn't base my choice (PIC or AVR) on which is "better," but instead which has decent development boards. Other than Arduinos and Atmel's XPlained boards, I can't think of any for AVRs. Boards for PICs are plentiful, though (Digilent is one company that makes them).

     

    The reason I prefer learning with these is that development boards typically have a debugger built in (along with lots of GPIO pins/headers and some peripherals to play with). These debuggers are often separable by jumpers and can be used to debug external circuits. Once you taste hardware debugging, you may not want to go back. Yeah, printf() statements work, but without a console and serial adapter and USART code and...etc...I don't know. I think hardware debuggers are quicker and easier. I haven't done much with my PICKIT3 so I don't know what kind of hardware debugging it offers. If it offers that, though, my vote will lean more toward PICs. Debugging AVRs requires special hardware starting at around $60 (AVR Dragon) and getting more expensive from there. That, or an XPlained board.

     

    Anyway, there you go. I like AVRs, but PICs get my vote if you want hardware debugging.

     

    Now if Microchip would standardize on their pin assignments...holy wowza, try building a programming board that'll support a number of different PICs, it'll drive you nuts. AVRs seem to be semi-consistent with their pinouts. I digress.

  • 0 in reply to modalpdx

    I am leaning more towards the pic right now I am paying with the pic 12f683 now if I could find some pin assignment syntax that makes some sense instead of gpiobits.gp1 etc. Also I noticed that my led wouldn't blink if didn't end the coffee with a delay function. For example led is off then wait then led on wouldn't work I would have to put a delay after led on.compiler is xc8.

Reply
  • 0 in reply to modalpdx

    I am leaning more towards the pic right now I am paying with the pic 12f683 now if I could find some pin assignment syntax that makes some sense instead of gpiobits.gp1 etc. Also I noticed that my led wouldn't blink if didn't end the coffee with a delay function. For example led is off then wait then led on wouldn't work I would have to put a delay after led on.compiler is xc8.

Children
No Data