Activity for Least Significant Bit
-
Least Significant Bit modified a comment on discussion Help
Cool, that's a really useful example - thank you! Was looking at some "blink without delay" examples but this is cleaner and clearer. 10kHz is plenty fast. The gifs are made with Byzanz; a command line GIF screen recorder that does a really good job with optimisation. I usually grab whole screen and crop in Gimp, but you can specify a region too. Edit: What is this GCBasic - looks like C?
-
Cool, that's a really useful example - thank you! Was looking at some "blink without delay" examples but this is cleaner and clearer. 10kHz is plenty fast. The gifs are made with Byzanz; a command line GIF screen recorder that does a really good job with optimisation. I usually grab whole screen and crop in Gimp, but you can specify a region too.
-
No worries; I do not need to model the complete circuit, only the logic. I'm kinda new to Atmel C and trying to design a bi-colour LED matrix display, which to me is quite a challenge! I started by building a "proof of concept" in Python (with which I'm more famliar) and now need to port it to the AVR. I'm hoping SimulIDE will speed up the countless trial & error cycles which will be required. I have opted for a common row anode configuration, and row by row multiplexing; the low-side shift registers...
-
No worries; I do not need to model the complete circuit, only the logic. I'm kinda new to Atmel C and trying to design a bi-colour LED matrix display, which to me is quite a challenge! I started by building a "proof of concept" in Python (whith which I'm more famliar) and now need to port it to the AVR. I'm hoping SimulIDE will speed up the countless trial & error cycles which will be required. I have opted for a common row anode configuration, and row by row multiplexing; the low-side shift registers...
-
No worries; I do not need to model the complete circuit, only the logic. I'm kinda new to Atmel C and trying to design a bi-colour LED matrix display, which to me is quite a challenge! I started by building a "proof of concept" in Python (whith which I'm more famliar) and now need to port it to the AVR. I'm hoping SimulIDE will speed up the countless trial & error cycles which will be required. I have opted for a common row anode configuration, and row by row multiplexing; the low-side shift registers...
-
It's been a bit of a struggle, but seeing this makes me excited: I know the LED matrix needs drivers, but it's too fiddly to build these in SimulIDE; I tried adding a bunch of transistor driven mosfets but it slowed the simulation down to just 4% and with pull-ups etc it took up 5x as much screen space as the logic alone. Saying that, it's the AVR code I want to test, and SimulIDE is the only tool I know that will let me do this WYSIWYG and in "real time", so it's still quite useful!
-
Doh! I knew that (reset must be high), just getting a bit tired. Example works now. Going back to my own test now to see if I can make it go - useuful to have a working example to compare behvaiour!
-
Thanks Santiago - I found the 74HC595 example, but whatever I do I cannot get any output! Maybe broken in trunk somehow? Also, I thought OE was inverted? In the example the switch feeds it 5V - does that mean it's tied to GND when "off"? I've tried with OE both on and off and still nothing...
-
I'm sorry, I just cannot get this to work :( Spent an hour with the 74HC595 and I'll be damned if I can get any of the outputs to go high. The datasheet suggests that in this configuration all outputs should be high: Edit: Scratch that; I misread. Check instead the more elaborate example in my next post. I have also tried tying "DS" (or "SER" in the datasheet) high, while putting a 5V pulse on "SHC" (or "SRCLK" in the datasheet), and tying "MR" (or "SRCLR") high and low, and tying also "STC" ("RCLK")...
-
Here's a more elaborate example, with a 0.5s 5V pulse applied to the "SHC" pin. With "DS" and "MR" tied high, I would expect this to clock in another "one" with every rising edge of the pulse, and with "OE" tied low these should appear on the outputs.
-
I'm sorry, I just cannot get this to work :( Spent an hour with the 74HC595 and I'll be damned if I can get any of the outputs to go high. The datasheet suggests that in this configuration all outputs should be high: I have also tried tying "DS" (or "SER" in the datasheet) high, while putting a 5V pulse on "SHC" (or "SRCLK" in the datasheet), and tying "MR" (or "SRCLR") high and low, and tying also "STC" ("RCLK") high and low, and any combination of the above. I have never seen the tiniest blip of...
-
I'm sorry, I just cannot get this to work :( Spent an hour with the 74HC595 and I'll be damned if I can get any of the outputs to go high. The datasheet is quite clear that in this configuration all outputs should be high: I have also tried tying "DS" (or "SER" in the datasheet) high, while putting a 5V pulse on "SHC" (or "SRCLK" in the datasheet), and tying "MR" (or "SRCLR") high and low, and tying also "STC" ("RCLK") high and low, and any combination of the above. I have never seen the tiniest...
-
What do the pin names on the generic logic components signify? Where is DCC and GND? Is ">" the latch clock or the shift clock (assuming shift clock since it wouldn't work without one). Is "m" "output enable"? I've tried a few ways of wiring it up but cannot get it to work!
-
What do the pin names on the generic logic components signify? Where is DCC and GND? Is "m" "output enable"? I've tried a few ways of wiring it up but cannot get it to work!
-
What do the pin names on the generic logic components signify? Is "DI" or ">" data in on this shift register? Where is DCC and GND? Is "m" "output enable"? I've tried a few ways of wiring it up but cannot get it to work!
-
Hi Santiago! Thanks for your help - it works! But I found that I have to name it "Makefile", and not "makefile", or I get "File type not supported" ("make" itself does not care about this). But the built-in compilation function is not that useful; you still have to manually load the resulting .hex file, and you can't trigger a compilation from the .c file itself. It would be cool if the app knew what source code was running on the MCU, so you could do single click deployment directly from the .c...
-
Hi Santiago! Thanks for your help - it works! But I found that I have to name it "Makefile", and not "makefile", or I get "File type not supported" ("make" itself does not care about this). But the built-in compilation function is not that useful; you still have to manually load the resulting .hex file, and you can't trigger a compilation from the .c file itself. It would be cool if the app knew what source code was running on the MCU, so you could do single click deployment directly from the .c...
-
Hi Santiago! Thanks for your help - it works! But I found that I have to name it "Makefile", and not "makefile", or I get "File type not supported" ("make" itself does not care about this). But the built-in compilation function is not that useful; you still have to manually load the resulting .hex file, and you can't trigger a compilation from the .c file itself. It would be cool if the app knew what source code was running on the MCU, so you could do single click deployment directly from the .c...
-
Hi Santiago! Thanks for your help - it works! But I found that I have to name it "Makefile", and not "makefile", or I get "File type not supported" ("make" itself does not care about this). But the built-in compilation function is not that useful; you still have to manually load the resulting .hex file, and you can't trigger a compilation from the .c file itself. It would be cool if the app knew what source code was running on the MCU, so you could do single click deployment directly from the .c...
-
Hi Santiago! Thanks for your help - it works! But I found that I have to name it "Makefile", and not "makefile", or I get "File type not supported" ("make" itself does not care about this). But the built-in compilation function is not that useful; you still have to manually load the resulting .hex file, and you can't trigger a compilation from the .c file itself. It would be cool if the app knew what source code was running on the MCU, so you could do single click deployment directly from the .c...
-
Hi Santiago! Thanks for your help - it works! But I found that I have to name it "Makefile", and not "makefile", or I get "File type not supported" ("make" itself does not care about this). But the built-in compilation function is not that useful; you still have to manually load the resulting .hex file, and you can't trigger a compilation from the .c file itself. It would be cool if the app knew what source code was running on the MCU, so you could do single click deployment directly from the .c...
-
First of all: thanks to everyone involved in this project! I've been struggling with SimulAVR and SimAVR on the command line (SimulAVR seems to be abandoned), and Atmel Studio 6 in a Windows XP(!) virtual machine, but it's clunky and can only simulate standalone MCUs. I've been dreaming about an "IDE" that would allow me to build and test simple AVR projects including external components such as buttons, LEDs and serial comms, and to be able to watch and graph pins and registers in realtime. There...
-
First of all: thanks to everyone involved in this project! I've been struggling with SimulAVR and SimAVR on the command line (SimulAVR seems to be abandoned), and Atmel Studio 6 in a Windows XP(!) virtual machine, but it's clunky and can only simulate standalone MCUs. I've been dreaming about an "IDE" that would allow me to build and test simple AVR projects including external components such as buttons, LEDs and serial comms, and to be able to watch and graph pins and registers in realtime. There...
1