I ask this since assembly language is really close to the micro-controller hardware, and what micro-controller would you reccomend.
The bot has to search for object that I show it before and then I 'lose' the object. Note, I do not know anything about micro-controllers.
This is one of those "open-ended" questions that the moderator doesn't like. So I'm going to leave you with some short, general answers. These are based on over 20 years in industry designing various bits of hardware and software for embedded systems:
In general you don't need to learn assembly to be able to program a microcontroller. As long as you know C, it's enough for you.
Knowledge of assembly of course would help. Specifically, it would help in writing optimized code (or rather, not writing stupid code) as well as having a good estimate of how fast or slow a piece of code could be. Sometimes in very performance critical sections manipulating the assembly may also be needed, but again, in general you wouldn't be needing any of this.
Specially if you are a beginner.
Regarding microcontrollers, there is a wide variety of them, almost all of which are good and useful. Choosing a microcontroller really depends on what you want to attach to it and how complicated its software is going to be. With similar microcontrollers among different brands, I would personally pay attention to how well the microcontroller is documented and how good its compiler/IDE is. Little-explained data-sheet is a headache and a bad IDE an annoyance you don't want to deal with.
The major disadvantage of assembly language is that it is different for each processor that you use. Therefore there is a big learning curve whenever you change processor.
Clearly, if you only ever plan on using a single processor (or family of processors) then this is less of an issue; however, life is rarely that simple.
Equally, assembler allows you to really get things wrong, unless you are very careful. I speak as someone with lots of years commercial experience writing flight-critical assembly code!!
On the other hand, pretty much every processor comes with a suitable C compiler (as @Shahbaz suggests) and porting C from one processor to another is a lot more straightforward than porting assembler.
Unless you already have good assembler experience, I'd be minded to learn C, and leave assembly language for those (very rare) occurrences when C just isn't up for it.
As for which processor... how long is your piece of string?
I think the answer here is "that's the wrong question". (It's a bit like asking "what spoken language should I learn if I want to write detective novels?") But it does have an answer: it depends.
I can't speak for everyone, but when I was just starting out in programming it seemed to me that learning assembly language would help my programs run faster. This is not necessarily true, because it was based on a faulty assumption: that my writing assembly code (at a beginner level) would produce more efficient code than today's sophisticated compilers. Furthermore, I assumed that I could pull off complicated algorithms in assembly in the first place -- look at how a simple algorithm like bubble sort becomes very intimidating in assembly.
You should have a good command of the algorithms themselves that are required for robotics. With that knowledge, the specific language is irrelevant; you will use the language most appropriate to the platform, even if you have to learn a new language to do so. In some cases this will be assembly, in other cases it will be a variant of C/C++ (like in Arduino), and in still other cases it could be a high-level language.
But learn the theory first, before you get bogged down in the implementation. In other words, before you choose a language you should think about what you're going to say.
push ax ; push ax onto the stack and mov bx, cx ; set bx=cx :-). loop is an expensive instruction, you're better off with dec bx followed by jnz loop_start - and it saves you from push/pop cx.
$\endgroup$
What kind of problems are you interested in? Mechanical design? Electronics? Low-level control and algorithms? High-level planning and state estimation?
Pick your battles. Assembly is good to know for some projects, but use bigger/easier building blocks depending on what your interest is.
It's nice, but for the most part, unnecessary if you're just dealing with robotics. Maybe if you need some high-end optimization, it may be helpful. But most compilers can optimize better than average humans these days anyway. Unless you really know what you're doing and understand the architecture enough to optimize further, I'd say it's not necessary. Plus, different manufactures have their own instruction sets, many of which behave differently on different MCU's. Another thing to cosider is that syntax varies between different MCU's. For instance, AVR MCU's have a different syntax than MIPS architectures and TI DSP's. It all depends on what you're doing.
