Author Topic: Which microcontroller should I learn?  (Read 73248 times)

0 Members and 3 Guests are viewing this topic.

Offline dannyf

  • Super Contributor
  • ***
  • Posts: 8221
  • Country: 00
Re: Which microcontroller should I learn?
« Reply #125 on: February 22, 2016, 11:56:11 am »
"msp432"

I would like to see anyone taking a stock download of ccs, a stock example downloaded from ti and a stock msp432 and show that they work out of the box.

That project was basically pushed out before it is ready. Shame on ti.
================================
https://dannyelectronics.wordpress.com/
 

Offline dannyf

  • Super Contributor
  • ***
  • Posts: 8221
  • Country: 00
Re: Which microcontroller should I learn?
« Reply #126 on: February 22, 2016, 12:02:00 pm »
"register level ="

Like a vortex m chip of your choice, set up the clock, set up uart transmission via the interrupt. All with registers.

And then do the same with the library and you will understand why libraries are used.

This no-library non sense is the same as the no-C nonsense of yesteryear: they never understood that the world have changed and chips are getting so complex that to maintain productivity, you have to rely on libraries, OEM, your own, or a 3rd party.
================================
https://dannyelectronics.wordpress.com/
 

Online tggzzz

  • Super Contributor
  • ***
  • Posts: 23122
  • Country: gb
  • Numbers, not adjectives
    • Having fun doing more, with less
Re: Which microcontroller should I learn?
« Reply #127 on: February 22, 2016, 03:29:10 pm »
This no-library non sense is the same as the no-C nonsense of yesteryear: they never understood that the world have changed and chips are getting so complex that to maintain productivity, you have to rely on libraries, OEM, your own, or a 3rd party.

The buy-vs-build debate is, with good reason, never ending. Decisions must be continually re-evaluated without dogma.

Many many people have been burnt by trying to use a library that had subtle incompatibilites with the way their system was designed. Classic problems areas include re-entrancy, low power, multiple threads/processes, incompatible C compiler flags, and changes/incompatibilities between various vintages of C/C++ compiler standards and implementations.
There are lies, damned lies, statistics - and ADC/DAC specs.
Glider pilot's aphorism: "there is no substitute for span". Retort: "There is a substitute: skill+imagination. But you can buy span".
Having fun doing more, with less
 

Online nctnico

  • Super Contributor
  • ***
  • Posts: 30421
  • Country: nl
    • NCT Developments
Re: Which microcontroller should I learn?
« Reply #128 on: February 22, 2016, 05:28:55 pm »
Libraries usually don;t behave as expected/documented so when using a library it must solve a difficult problem. OTOH investing time into learning how to use a library can be beneficial because you'll have an off-the-shelve solution for a particular problem. IOW don't throw a library out at the first sign of trouble but do careful research with the help fora and other online resources about the particular library to find it's strengths and weaknesses.
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline Sal Ammoniac

  • Super Contributor
  • ***
  • Posts: 1813
  • Country: us
Re: Which microcontroller should I learn?
« Reply #129 on: February 22, 2016, 06:37:44 pm »
MIPS add more complexity by sever orders of magnitude  :D

MIPS is orders of magnitude more complex than what? ARM Cortex?

Nonsense. MIPS is a very simple architecture, even compared to ARM Cortex.
"That's not even wrong" -- Wolfgang Pauli
 

Offline legacy

  • Super Contributor
  • ***
  • !
  • Posts: 4415
  • Country: ch
Re: Which microcontroller should I learn?
« Reply #130 on: February 22, 2016, 06:51:30 pm »
MIPS add more complexity by sever orders of magnitude  :D

MIPS is orders of magnitude more complex than what? ARM Cortex?

Nonsense. MIPS is a very simple architecture, even compared to ARM Cortex.

we are talking about two different things: the HDL complexity, the programming assembly complexity
in my experience yes, if you want to implement a MIPS machine in VHDL (I did), it's the simplest in the RISC family
while if you want to program MIPS in assembly (I have written a lot of assembly code, including a monitor), it adds more complexity in your code
as you have to deal with a lot of troubles which are handled by hardware in ARM
 

Online nctnico

  • Super Contributor
  • ***
  • Posts: 30421
  • Country: nl
    • NCT Developments
Re: Which microcontroller should I learn?
« Reply #131 on: February 22, 2016, 08:15:06 pm »
MIPS add more complexity by sever orders of magnitude  :D
MIPS is orders of magnitude more complex than what? ARM Cortex?

Nonsense. MIPS is a very simple architecture, even compared to ARM Cortex.
Having written assembly for both they are both equally complicated with MIPS having the one-delay-slot disadvantage because the instruction after each jump gets executed as well. The biggest disadvantage of using MIPS is that when you have cross-platform sourcecode you'll often find an x86 and ARM assembly optimised version but no MIPS assembly optimised version. It gets worse if software depends on pieces of assembly code to work on a certain platform and there is -again- no MIPS support (the older firefox versions for example).

So from a micro perspective there is not much difference but looking at the big picture the difference is huge and MIPS is definitely the lesser choice.
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline Sal Ammoniac

  • Super Contributor
  • ***
  • Posts: 1813
  • Country: us
Re: Which microcontroller should I learn?
« Reply #132 on: February 22, 2016, 09:01:14 pm »
while if you want to program MIPS in assembly (I have written a lot of assembly code, including a monitor), it adds more complexity in your code
as you have to deal with a lot of troubles which are handled by hardware in ARM

That I agree with. You pretty much have to do everything explicitly in MIPS assembly code versus an ARM. A good example is an interrupt: a MIPS CPU just saves the PC and vectors to the handler, nothing more. An ARM will save some of the registers as well, minimising what you need to do in the handler. This extends to other operations as well.
"That's not even wrong" -- Wolfgang Pauli
 

Offline legacy

  • Super Contributor
  • ***
  • !
  • Posts: 4415
  • Country: ch
Re: Which microcontroller should I learn?
« Reply #133 on: February 22, 2016, 11:22:50 pm »
Having written assembly for both they are both equally complicated

mmm, on the linux platform I find more complexity due to the cache and due to all the mips variants, and there are too many variants in the MIPS family (including IDP, Toshiba, NEC, …. and SONY). Attempting to port linux 4.* to SGI Octane (for SMP purpose, Toshiba R14K/MIPS4, now it works) was not so easy due to the cache, which must done in assembly.

When I programmed the playstation2 I had a lot of troubles with the TLB, which was just different from what I was expecting.
 

Offline legacy

  • Super Contributor
  • ***
  • !
  • Posts: 4415
  • Country: ch
Re: Which microcontroller should I learn?
« Reply #134 on: February 22, 2016, 11:28:42 pm »
I am afraid the PowerPC is the worst: the EIEIO nightmare

EIEIO stands for Enforce In-order Execution of I/O, it's a machine code instruction used on the PowerPC computer processor which prevents one memory or I/O operation from starting until the previous memory or I/O operation completed. This instruction is needed as I/O controllers on the system bus require that accesses follow a particular order, while the CPU reorders accesses to optimize memory bandwidth usage.

It usually causes a lot of headaches in avionics (BSP, BPUM, PUM, AUTOMA, … low level behind the hood)
 

Offline dannyf

  • Super Contributor
  • ***
  • Posts: 8221
  • Country: 00
Re: Which microcontroller should I learn?
« Reply #135 on: February 22, 2016, 11:46:19 pm »
To the OP,

This key is not get paralyzed by the fear of picking up the wrong mcu to learn. If you are going to be a great embedded programmer, you are going to find that out on an avr just as well as you will find that out on a cortex m or pic24, etc.

People have long been great embedded programmers in the 1bit mcu days. So just start the journey learning.
================================
https://dannyelectronics.wordpress.com/
 

Offline ez24

  • Super Contributor
  • ***
  • Posts: 3082
  • Country: us
  • L.D.A.
Re: Witch microcontroller should I learn?
« Reply #136 on: February 23, 2016, 12:28:27 am »
If you're interested in ARM, there is an online course from University of Texas that started this January 20:

https://www.eevblog.com/forum/beginners/free-course-ut-6-03x-embedded-systems-on-edx-starting-now/msg846982/#msg846982

Although it already started, I guess you can still enroll. The course is based around the TI implementation of ARM (TM4C123), and you can get the evaluation board directly from TI: https://store.ti.com/Tiva-C-LaunchPad.aspx. I got mine delivered in 4 days, to Sao Paulo.


FYI  As of Feb 22 2016 this course is still open.  I just enrolled and ordered the kit with the wi-fi from Digit Key.  Price about the same as Element 14 (Newark)  With Newark I could see the complete price and with Digit Key I could not see the exact shipping costs.  Digit Key might have cheaper shipping if I knew the shipping weight.

Now to try and get caught up.  Thanks 1xrtt
YouTube and Website Electronic Resources ------>  https://www.eevblog.com/forum/other-blog-specific/a/msg1341166/#msg1341166
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf

 

- - -
-->