Learned the hardway - never be too lazy to put in pulldown resistors when you are doing blue wire changes
"pull down" with a short to ground a repurposed pin without verifying that the firmware brings it up high, pop pop pop, like a killswitch for carefuly curated prototypes
speaking of prototypes -- apparently Atmel hadn't figured out yet that shipping a micro with its fuse bits set for an external crystal by default makes it bloody hard to program :/
so you want to put into you vhdl "drive pin 67 on breadboard high" and it should magically figure out how the pins on your fpga are externally wired to find that pin on the breadboard?
I have this other device that contains 6 pins, and I have to connect it to my fpga somehow. I thought the way to do this was by plugging in the 6 pins into my breadboard and reading the pins the way I just described, but it seems to be impossible
from within vhdl you access the pins, and then you connect to the pins in whatever way you like whatever things you want, chickens, hamburgers, oysters, opamps, thermonuclear fuses.
The wiring between the breadboard & FPGA is already done on the FPGA board I'm given. How can I figure out which pin is connected to GPIO0 for example? It doesnt say this in the FPGA board manual :/
hm, intresting feature, if you upload a video to youtube containing music from some registered song, they will place ads on your video and revenues from that ad go to whoever registered that song...
@user1534664 I usually do so within the VHDL itself, but you're probably using the GUI. I have no experience with the Spartan GUI so you'll have to read the manual yourself.
it is quite hard to find any particular information about how much control you have on the type and placement of ads in your videos when you activate monetarization...
Thanks for pointing me in the right direction. I'll do some research on that. My only problem now is that the datasheets/manuals don't say which pin on the FPGA connects to the breadboard e.g. GPIO0. Or at least, I haven't been able to find these real_pin references.
@PlasmaHH Know an online service that lets me blab get and post to it from one side and look on another PC what parameters get received?
they say the messages don't get to the server, while on my internal network it works fine, so I want to test it "across the real world" to show whether they should be looking at their own server
@Asmyldof nope, never heard of any, but since I have my own server out there I never had the need to look for something like that
does there need to be anything behind it? you could just get and post something nonexistant on my server and if you have a fixed IP I can tcpdump it for you
I was thinking of making a PHP page that shows the previously gotten parameters (history of 3 or something)
So that I can post to it with the script, and then refresh on PC and see my own empty one and then the last 2 device ones
@PlasmaHH will do
It's possible I'll see if simply a php that writes a txt file and reads it back works in my host's sandbox anyway, but I think maybe it doesn't allow locally written files and then it becomes a pita to figure out where to leave crap or install a database
Or to put it differently, you haven't seen anything of this system yet, so you don't know, but it's already pretty much gone from 7th layer to 2nd layer of hell
How about just have one half of the peninsula bull-dozer the other half into the ocean, rinse, repeat till there's 10% smartest/most resourceful left and have them run our labs?
When making an edit to an answer I have given, sometimes I would like to use the "strike-through" rather than delete the text. What is the command to cause text to show with strike through, when editing answer ?
@BrandenBoucher Be aware of there being an ARM element and an "Chip Vendor" element
ARM is just the core and all peripherals are made by Atmel, so there may be a devide in the documentation and examples of ways things are done. This can be confusing at first
Core-related interrupts and clocks and blah-blah may look and feel different than the same kinds of subjects related to everything not-core
Other than that, it's mostly just read the docs and examples and you'll be fine. Don't stick all your learning effort onto the ASF based examples, as many of them, like most other systems also do, use stupid non-interrupted ways for things that could be easily done by interrupt
@Asmyldof, on the ASF note: I know they put a lot of hard work into that and it helps you for doing some rapid dev work, but it really is bloated and I prefer writing my own, more design-specific code anyways. So I think we agree there.
But it's good to keep your first point in mind. The way the core works may feel different than the way the peripherals work.
@BrandenBoucher In that case the gotcha is to not forget to enable the peripheral, enable the clock to the peripheral and unlock the peripheral. Not necessarily in that order. Not mentioning to program the equivalent of DDR and PORT registers, that is pretty similar to AVR
My experience is with TI parts, but I've seen similar registers on serveral controllers. Just be aware. Read the datasheet carefully when trying to use a peripheral.
BTW, am I the only one that thinks these dev board with tons of peripherals (LCD screen, buttons, LEDs, speakers, USB, ect...) are really awesome when you want to learn about an MCU our test something, but REALLY impede the design process when trying to create something specific, especially where you will need to implement all the support hardware?
@BrandenBoucher You use the dev boqard to get to know the features. Costs β¬30, which is peanuts in the professional world. Then you throw everything out and purposely design for your intent and board design
@BrandenBoucher You're missing a step. You start with the dev-board and afterwards you make a rough-prototype for at least that much which is more specialised to your needs.
@BrandenBoucher Some of the "better" boards have postage stamps that house the actual MCU/device and the dev board is just the "breakout", the protype process then proceeds to you spinning or otherwise wiring up your own breakout plane for the stamp, and eventually migrating to an integrated design.
@crasic, that's why I usually go from big dev board to simple breakout board. I think you understand where I am coming from.
@Asmyldof, some are not so cheap. But still pocket change in the professional world, true. However, compared to a one-off project by a hobbiest, that can be quite a significant cost.
@Mast, I guess that's kinda what I mean, essentially. The big dev board is nice for learning, but once you know that part, it seems easier (or maybe more useful for PoCs) to have a very simple breakout board.
@BrandenBoucher I've never bought a sample/test board above β¬70,- Once it crosses the β¬50 line it's easier to spin the first test design and dev on that
@Mast if you have some kind of video output peripheral or ic it's not that hard to get an as Gui. The complexity of the os Gui comes from multiplexing multiple applications and not because it's particularly difficult to make graphical input and output on a low level