|
hobbesmaster posted:neg my chip select twist my pot
|
#
¿
Feb 12, 2015 08:02
|
|
|
|
| # ¿ May 16, 2024 03:42 |
|
|
resist my flow
|
|
#
¿
Feb 12, 2015 08:03
|
|
|
hobbesmaster posted:so i need to be able to program some simple little spi flash chips, whats the professional version of bus pirate/flashrom because thats slow as molasses bit bang it with an arduino  (really easy to do actually, and potentially "fast enough")
|
|
#
¿
Feb 15, 2015 20:33
|
|
|
hmm...(!)atomicthumbs posted:hmm hmm...(!)
|
|
#
¿
Feb 21, 2015 22:51
|
|
|
DNova posted:btw I think I raped my rpi gpio with 5v a bunch of times on accident but it liked it so no crime was committed dont do this, both the 5v tolerant gpio and the lovely language
|
|
#
¿
Mar 10, 2015 18:37
|
|
|
movax posted:i've just finished getting our custom jtag subsystem working 
|
|
#
¿
Mar 19, 2015 07:31
|
|
|
Bloody posted:explaining spi is nice because it's so loosely defined. the poo poo i have seen, man. i have seen some poo poo. lvds spi. ddr spi. spi where chip select actually does nothing and god help you if you have anything but the most pristine clock line from power up until forever. spi isnt spi isnt spi you got to configure poo poo like what edge do the slaves need to latch on, what polarity etc. if the diagram is drawn out you dont even need to read the (possibly lying) technical summary of the spi configuration, you can take a glance at the signal diagram and know how to configure your master. i worked on a stack at my last job that had a fuckload of things sharing a single spi bus (we had a multiplexing chip to handle the 8+ devices listening to that bus) and different slaves had different mandates like the DACs and ADCs did different things w/ spi, along with boards that had other mcus that wanted more stringent timing etc. so i had a bunch of dumb logic that would configure spi for each target communication madness madness
|
|
#
¿
Apr 3, 2015 19:12
|
|
|
recmovax posted:let me tell you about the shift register known as jtag recommend me an all purpose JTAG debugger I could use with OpenOCD or something of that ilk ideally not the jlink because it's kinda expensive imo
|
|
#
¿
Apr 3, 2015 19:54
|
|
|
movax posted:ft2232 based things are decent and inexpensive, if used with a non-lovely userspace application is adaptive clocking up to the host doing the debugging? or the processor/soc/debugging architecture you're interacting with? i know nothing baout jtag and am trying not to if ic an help it my mission is to have a general purpose debugger i can plug into w/e headers i want and it's okay if it can't autodetect just as long as i can ask OpenOCD to talk to the target devicea s if it were $SOME_SPECIFIC_PROCESSOR at $SOME_SPECIFIC_CLOCK and have it work most of the itme
|
|
#
¿
Apr 3, 2015 23:45
|
|
|
DuckConference posted:we're doing our next product with an stm32f4, and since Kiel uvision 4 kind of sucks, it looks like we might go with gcc/eclipse/openocd. it's not a horrible idea is it? we avoided iar and stuff at my last job and went with Kinetis and the Kinetis Design Studio thing which is just Eclipse with a bunch of plugins they made for configuring the cpu and generating some C stuff which wasn't as bad as i expected it to be i have set up basic gcc toolchains in eclipse for building ARM targets and stuff and once you get past how annoying eclipse is to configure it's generally serviceable  this was internal product poo poo that wouldn't see the light of day though, so the onus was different for me
|
|
#
¿
Apr 7, 2015 18:53
|
|
|
Fanged Lawn Wormy posted:i'm getting interested in taking the arduino training wheels off and using big boy developer tools for embedded systems it depends where you are at, I learned a lot by just taking the programming manual for a SoC and making my own linker script and C bring up code with determination and self hatred and esoteric examples understanding what the clocking pathways are and how to configure them and what modes various pins are listening to or are on when it comes up from power off is pretty cool. it helps to ask an unfortunate rear end in a top hat a poo poo ton of dumb questions too. C toolchains for embedded are horribly convoluted and it's hard to decipher what is helpful cruft and what is truly essential
|
|
#
¿
Apr 8, 2015 00:51
|
|
|
Mr Dog posted:if you want to learn this poo poo on your own time (please do not inflict your learning process on your employer, for them you should do some simple poo poo that might not be super optimally cost effective but that will at least actually work i.e. use a Raspberry Pi for everything) then i guess try the following: final step: utilize, understand and worship CMSIS, i never got here 
|
|
#
¿
Apr 8, 2015 19:21
|
|
|
also: having an oscilloscope makes verifying your poo poo a lot easier, it's easy to sanity check your clocking by toggling a GPIO in a while loop and also debug a bus or two. i used the gently caress out of my scope to verify poo poo once i could run arbitrary c
|
|
#
¿
Apr 8, 2015 19:22
|
|
|
JawnV6 posted:never understood the fixation some people have on linker scripts and make files. you've got C and asm, and a bunch of knobs to fix the translation between them. becoming an expert knob maker doesn't help the final product as much as a half dozen easier things i dont think anyone should ever bother to make a linker file more than once, but it's a really good exercise to force you to understand how when you write C you aren't writing code in a vacuum there's a lot of poo poo across the full stack of your toolchain that eeks its way into the C you write even if you don't realize it, defining linker variables that point to blocks of memory and then referring to them in C basically make them one and the same
|
|
#
¿
Apr 8, 2015 21:21
|
|
|
C is a nightmare of a lang to do any project of scale in because of how loosely defined it actually is, and this fact can burn you really bad if you don't respect that fact every time you write code you are writing in a dialect the lang actively encourages you to write macros and elaborate generics that turn into your own bespoke dialect
|
|
#
¿
Apr 8, 2015 21:27
|
|
|
JawnV6 posted:just use the friggin GUI with big red breakpoint buttons and arbitrary register/value tools. it drives me crazy to see people chase this fantasy that's Yet Another Abstraction then whine about all the problems they invited to their lap after pretending IDE's aren't "real" absolutely use IDEs and any tools that will make you not have to worry about that poo poo but understand wtf the IDE is and is not doing for you so you can make informed decisions when it comes time to troubleshoot issues in your toolchain or make future tooling decisions for various processors and stuff the ARM tools for eclipse have makefile generators that you can specify architectures for and overall it Just Works, even better if your mfg of choice has their own eclipsey plugins that will do their own linker script generation and generate boilerplate driver stuff for your SoC like interacting with the DMA engine or generating startup code for things like clocking changes you can wrap in a state machine
|
|
#
¿
Apr 8, 2015 21:41
|
|
|
JawnV6 posted:no, no, no, suffering Must Be Better. any Tool is an Abomination and must be abhorred. for any given protocol if you don't write a bit-banging version first you can't possibly understand how to use a HW module that does it for you i implemented 1wire with just TI's documentation and my scope to verify timing, that was a hell of a bit bang edit: to clarify 1wire is some baby poo poo i just had never done anything like that, since you have to flop the GPIO from input to output and read things in sensitive timing ranges and dumb basic poo poo i'd never done a cyberpunk goose fucked around with this message at 18:23 on Apr 9, 2015 |
|
#
¿
Apr 9, 2015 18:17
|
|
|
Arcsech posted:given that vivado is a java app, yes, this is exactly what fpga tooling will be like 10 years from now  this isn't a crime in and of itself, java is a fine lang to house this sort of tooling
|
|
#
¿
May 1, 2015 00:26
|
|
|
Bloody posted:this loving question/problem haunts me like every two months or so and i still do not have a useful solution find a SoC that abstracts as much of that poo poo away as possible an RMII IC + Kinetis K6* series chips + their little Kinetis Design Studio thing will generate the ethernet related calls at whatever level you're comfortable with then you just be like Ethernet_SendBytes(buffer, buffer_size); there's no easy solution that doesn't have tradeoffs. option 2: become a master of the USB 2.0 spec, a curse i wish upon no one
|
|
#
¿
May 8, 2015 20:44
|
|
|
hobbesmaster posted:serial ports can do a megabit, 10 times faster is 10baseT also true
|
|
#
¿
May 8, 2015 20:45
|
|
|
 looks like my name is on someone's short list for good emb-c devslooks like i might soon be quoting some startup $60/hr for 2 weeks of side-job work writing some low level drivers to poll adcs on command, easy $1.5k i'll be chatting with them tomorrow about more specifics edit: yes $60/hr is really really low a cyberpunk goose fucked around with this message at 08:26 on May 10, 2015 |
|
#
¿
May 10, 2015 08:23
|
|
|
Mr Dog posted:dude wtf r u doin writing like 5 functions that the non low level dude can call it's like 100-200 lines at most and most of the unknowns and time sink will just be loving with Keil tools and maybe pokin a trace with a probe when the adc doesn't react as anticipated I'm p bad at gauging how much my time is worth but my fear here is all the unknowns, don't wanna bill $300hr on something that doesn't pan out or maybe I don't end up with enough spare time to weekend warrior it etc
|
|
#
¿
May 10, 2015 19:15
|
|
|
ChiralCondensate posted:at least go for $150 ok will do
|
|
#
¿
May 10, 2015 19:36
|
|
|
Mr Dog posted:fwiw i too am awful at negotiating and knowing what my time is worth etc but i do know at least that $60/hr for freelance embedded dev work is so low as to not get you taken seriously.  subconsciously I think I knew 60 was low enough and needed yosposters to make fun of methanks team
|
|
#
¿
May 10, 2015 19:51
|
|
|
atomicthumbs posted:this is a bit distant from this thread's usual discussion topic of boring stuff like microcontrollers and other tiny computer, but does anyone know if there are any good books on pulsed power circuit design? how's noise bridge??
|
|
#
¿
May 10, 2015 20:37
|
|
|
just got off the phone with the startup that needs emb-c work i put my dick on the table at $150/hr and a dead silence dropped  i stuck to my guns thoughit sounds like they want to put 2-3 hours down for a research spike so i can look at the tools and maybe just give their main programmer guy a jumpstart on the magical world of embedded C
|
|
#
¿
May 13, 2015 04:31
|
|
|
Raluek posted:lol 'cause digging their lead programmer out of a hole so their company goes from "nobody here knows what to do" to "we can now build our product" is only worth a couple hundo this is sounding familiar
|
|
#
¿
May 13, 2015 04:34
|
|
|
what they really wanted was a magical enthusiastic team friend to join up and get paid for ~passion~
|
|
#
¿
May 13, 2015 04:40
|
|
|
 i decided to tell those guys that i'm just too busy to take on a low level C project but can field some basic no guarantees questions in the future if they needtruthfully they are just super weird and don't have their poo poo together and I don't wanna deal with another startup where some dudes without real funding or planning skills. their product is dumb as poo poo too and will never work
|
|
#
¿
May 15, 2015 17:33
|
|
|
they don't have funding yet and want to make a super over complicated prototype before their kickstarter (lol) with bells and whistles that are really fiddly and error prone without a lot of involved signal processing that they wanna offload through BTLE to a phone and just ugh I don't know why people don't just fukkin use arduinos and poo poo to test their dumb theories
|
|
#
¿
May 15, 2015 17:37
|
|
|
fritz posted:we've been keeping the 'well maybe we can offload the computation to the host and send the results back' option on the table for a 'oh god everything else we tried failed' situation that's cool depending on the characteristics of the data channels and what the data is
|
|
#
¿
May 19, 2015 19:45
|
|
|
Bloody posted:nope. closest candidates so far are a silabs chip with a 4-bit current dac (current would be fine but 4 bits is wtf?) and a csr8670 which may or may not be usable but i will probably never know because they do not seem to be people who deal with low-volume people although the part is on digikey?? http://www.mouser.com/new/panasonic/panasonic-pan1740-ble-module/ maybe?? edit: nope lol
|
|
#
¿
Jun 16, 2015 04:06
|
|
|
writing hdl stuff seems like writing one level above doing npn/pnp gate layout for logical constructs (i'm p sure it is??? i still haven't written a single line of hdl-anything, if someone lays out a list of tools and a way to get started ill gladly do a hello world simulation verification thing)
|
|
#
¿
Jun 29, 2015 23:27
|
|
|
SCLK: ______|‾|_|‾|_|‾|_|‾|_|‾|_|‾|_|‾|_|‾|_|‾|_|‾|_|‾|_|‾|
|
|
#
¿
Jun 30, 2015 20:52
|
|
|
Bloody posted:http://wavedrom.com/editor.html?%7B...narrow%27%7D%7D lol it doesn't base64 the json description or anything
|
|
#
¿
Jun 30, 2015 21:20
|
|
|
JawnV6 posted:i2c wat u did there
|
|
#
¿
Jul 15, 2015 23:51
|
|
|
JawnV6 posted:i got the reset pmic, fumbling on oscillators now ugh I got stuck on the latch mechanism :/ couldn't figure out how to make it simpler
|
|
#
¿
Jul 19, 2015 14:31
|
|
|
Bloody posted:a scope, a dece iron, a microscope, and a bench supply do it
|
|
#
¿
Jul 28, 2015 18:36
|
|
|
I would draw the line between the philosophy behind the MCU/processors intended use of the internal byte code architecture no one (sane) is making really elaborate operating systems that run on PIC, you... could but it's not suited for it compared to say a Motorola SoC with an arm core
|
|
#
¿
Aug 10, 2015 03:42
|
|
|
|
| # ¿ May 16, 2024 03:42 |
|
|
Barnyard Protein posted:yeah but there are PICs with MIPS cores my language was carefully chosen
|
|
#
¿
Aug 10, 2015 03:56
|
|