Microcontroller thread

File: images.duckduckgo.com.jpg (283KB, 1200x800px) Image search: [Google]

283KB, 1200x800px

>>61034478

>>61034511
DON'T YOU DARE FLIP THAT SWITCH

File: AT89C2051-24PU-500x500.jpg (21KB, 500x500px) Image search: [Google]

21KB, 500x500px

>>61034478
I actually wrote my own programmer for this one. Remember when programming protocols weren't proprietary bs?

>>61034804
In a proper circuit you would just trip a breaker.

>>>/g/

>>61034478
Ah man, I remember working with the 16C84 and then upgrading to the '16F84', writing my shit all in assembly was annoying but the code was real small... it has been years since the last time I programmed one of those. I even recall when you could request free samples from Microchip, even for the higher end uC

Good shit

>>61034478
Are there any good paying jobs for this shit?
I have a job programming MCUs but the pay is shit, and every time I read about another firmware dev on the internet, they are also making a shit wage.

>>61035042
Depends. If you program coffee machines then it's probably shit. I had some good offers in the IoT land (MCU + complementary python stuff: interfacing, webservices, etc) I guess that security/military sector also pays well.

>>61035042
I think it is because if you are working on embedded you are at a hardware company. Software is just seen as a necessary tool rather than what makes them competitive.

>>61034988
are you me?
Did some pic 16f stuff some years ago, all assembly madness. I built a binary clock. I recently discovered RasPis for me, these things are so much greater than uCs, especially the 5$ PiZero. For any uC task, I'd just throw a 5$ pi in there.

>>61034982
Well, I guess I can't blame you, /g/ is looking more and more like /v/ every day.

>>61035042
there are plenty in silicon valley

File: 1497029243304.jpg (181KB, 1920x1079px) Image search: [Google]

181KB, 1920x1079px

>>61034478
Who else programs their mcus in forth?

It's like the teensiest unix there is

File: Viagra.jpg (40KB, 500x364px) Image search: [Google]

40KB, 500x364px

>>61034478

File: DSCN4515.jpg (535KB, 1600x1200px) Image search: [Google]

535KB, 1600x1200px

I've done a lot of projects using 8bit ~20MHz MCUs, but now I've got to use something powerful enough to implement an HD USB webcam with. I'm estimating that will require at least 100MHz 32bit, USB 2.0 transceiver, a Mb of RAM, and preferably a few ADCs. Any recommendations?

Anyone tried RetroBSD or LiteBSD?

>>61034478
was into these things when i was in jr high (pic16f628). i remember plugging them into breadboards. found this 5 digit led display on an old computer, looked up the datasheet, and made it display some scrolling messages. i also remember ordering a free sample of one of those pic32 with like 100 pins and etching a pcb to interface it to my breadboard with wirewrap. this must have been in like 2002

>>61035042
All companies working close to the bare metal pays shit. Probably something to do with that they've been in business for a long time and knows what they can get away with. In my area the companies kind of formed a price cartel and decided how much they were willing to pay a developer. Web on the other hand pays like 4 times as much minimum despite being easy. Can't wait for the next IT crash when the web devs are out of luck.

>>61036412
ARM m0 chip or an M4

>>61036305
Kek'd mein Freund

>>61034478
I'm having a sumo robot competition with PIC microcontrollers this tuesday. Wish me luck.

>>61035042
i work in embedded systems i.e. bretty much this
not in us but 2 years experience and make just over $4k a month which is more than $1k over average in my country
if you like low-level programming its really nice
i work with drivers and rtos implementations, most of which are written in C and Assembly

>>61036412
why not an fpga?
they're really good for implementing image and signal processing stuff on

>>61041120
I'm trying to make a digitiser that can convert an obscure old analog format to a webcam feed. The signal processing is very low; it's mostly just the speed needed to push all the pixels into an HD feed and enough memory to buffer a frame. USB stacks are a lot easier to work with on microcontrollers too.

>>61036305
KEK <--- this one
KEK
KEK

>>61034862
I know where you're coming from.
I cant be bothered to spend 50$ for a proprietary usb flasher that i can only use on specific model chips all the meanwhile newer chips might not even support the protocol in the future.

>>61036412
Samiliar problem, exept that i need 2 cameras for stereo vision and other computer vision stuff.
Linux SBC's dont seem to have necessary protocols for that amount of data, ignoring the fact that they have the perfect price/performance/memory ratio that i need.

I was thinking about using a small 32 logicblock CPLD for glue logic to funnel the 24bits per pixel data stream from 2 cameras in to a megabyte tier DRAM chip and then use the same CPLD as a serial interface to the ram chip for a ~50 MHz microcontroller to do some processing on.
However i havent ran any real numbers on it and dont know if it will give me an acceptable latency. since i want that as a realtime system.
The fact that the cheapest CMOS sensors are 30fps max this already pulls me down.

>>61034478
> 2017
> not STM32