I purchase a Arm Cortex M3 stamp module ([linky) and I’m just getting around to the point that I want to start fooling around a bit
I’m an absolute beginner to electronics, so I’m starting simple; just gonna start with the blinking LED routine. After that, I’m planning on getting a couple of LCD screens; most likely a 16x2 screen, and a small graphical screen. First question is, what voltage does this use? I see that the 16x2’s come in both 3.3v and 5v.
Next on the list, I have salvaged a screen from an old PSP, and am wanting to build a breakout board to utilize it with various projects. I’m going to order the connector ([link). Besides the main… ribbon? I don’t even know the proper term for that… Anywho, there’s another smaller one, but there is no connector available for it it would appear. What is it for? Also, how would I go about replicating the screen connector in Eagle? The pitch is fairly small (0.5mm I think?), so I’m just kinda stumped.
This isn’t actually a Cortex-M3 question. These “Stamp” modules run interpreters on them that distance you from the hardware, so unfortunately nobody here can help you with specific coding issues unless they have experience with this specific module (unlikely) since this isn’t Cortex-M3 coding, it’s ET-ARM Stamp coding.
The power requirements are listed right on the technical page:
You will not be able to use your PSP screen with this. To run the PSP screen it takes a lot of horsepower and i/o lines as it does not have it’s own controller. You would be much better off getting an LCD screen with a controller, which simplifies the interface a lot. Even then, with something with a resolution like that it takes a lot of memory for images and graphics.
That module appears to run standard code produced by a compiler or an assembler; I can’t see anything about an interpreter, although one could be ported to it.
That ETT device comes with TONS of sample code and a couple of Compilers, the best of which is a complete copy of RIDE7.
I have that device working. Its much like diving into the deep end of the pool!
You need a 3.3v supply. I use a ‘XBee Explorer USB’,sku: WRL-08687 breakout card, it has 5v and 3.3v output pins. But also FTDI Basic Breakout - 3.3V, sku: DEV-08772 would work also.
I suggest, you get a breadboard, a pack of jumpers that Sparkfun sells, a 3.3v lcd(not serial backpack). I love the jumpers, Jumper Wires Premium 6" Mixed Pack of 100, sku: PRT-09194
Then you can use the Ride7 kit to get started. After that think about the Rowley Crossworks (because they support the OpenOCD, Ride7 does not).
Back to that PSP screen. I would like to get something running off that, even if it has to be a more powerful rig (which I’ve been told it does). What kind of power are we looking at here?
Uh - pardon - as a beginner your task is like becoming starting shortstop for NY Yankees. Can it be done - can you do it - well possibly - but quite likely with little efficiency and satisfaction.
Suggest instead that you proceed more systematically - learn basics, I/O, timers, software (loops, decisions etc). Working with a 24 bit color TFT is “not” a wise “first” project.
Believe you’ll learn better/faster by:
a) using a simpler MCU as a learning vehicle
b) blink several Leds tied to GPIO
c) experiment with timers
d) graduate to 2x16 text Lcd - be sure to read/comply w/contrast voltage
e) graduate to small mono graphic - 122x32 or 128x64
After the above - many, many questions will have been answered. You will have a much deeper/broader “technical base” and will be able to form your “natural” questions in a more compelling form - raising the likelihood of forum response.
imho - “deep end” entry too often yields frustration, expensive mistakes and destroys morale. Wish you well…
SeniorEE:
Uh - pardon - as a beginner your task is like becoming starting shortstop for NY Yankees. Can it be done - can you do it - well possibly - but quite likely with little efficiency and satisfaction.
Suggest instead that you proceed more systematically - learn basics, I/O, timers, software (loops, decisions etc). Working with a 24 bit color TFT is “not” a wise “first” project.
Believe you’ll learn better/faster by:
a) using a simpler MCU as a learning vehicle
b) blink several Leds tied to GPIO
c) experiment with timers
d) graduate to 2x16 text Lcd - be sure to read/comply w/contrast voltage
e) graduate to small mono graphic - 122x32 or 128x64
After the above - many, many questions will have been answered. You will have a much deeper/broader “technical base” and will be able to form your “natural” questions in a more compelling form - raising the likelihood of forum response.
imho - “deep end” entry too often yields frustration, expensive mistakes and destroys morale. Wish you well…
Thank you for all of your advice. I did plan on starting with smaller things, but I just felt like asking these questions just so I had some answers. That list you posted is almost identical to what I was planning on doing; I’m gonna start with an Arduino most likely, just due to the support that’s out there. The only thing you mentioned that I was not thinking is Timers, but I’ll be sure to include that in there as well! Thank you very much again for all your advice, and sorry for not being more clear!
stevech:
Agree fully with prior poster.
Wanna run Linux? Do so on a PC!
I already do run Linux on my PC (well, one of them)
I did look at the PSP screen a while ago. It was just a quick look, since you can get refurbs for $20. From what I could see you could implement it with an ARM7, so you might be able to implement with the M3. You wouldn’t be doing much else with the chip, though. There’s an LPC 2xxx with a LCD driver built in that looked like it would work.
That’s just based on a quick look, though. Don’t quote me on anything there.
To be quite honest, I was just rifling through a box of junk the other night, and found this old broken PSP that my friend gave me. I saw how much the screens were going for, and shortly thereafter realized they’re some pretty nice screens, so I yanked it out of there I would just like to implement it sometime for one thing or another, as I don’t want it to go to waste!
a) Proceed by Refinement - start “basic” change/add only ONE thing at a time - continue only after you clearly understand each issue. Keep a list of: where you want to go, how you’re progressing - commit to writing - the “fog of battle” will surely make you forget after short time
b) Do not allow “Maximum Randomness!” New, untested HW (hardware), first time use SW and multiple new peripherals. Now “why” doesn’t this work? (have seen/been hired by big co.s caught in this trap) Not Good!
Your time is worth something - suggest that you buy “known good” HW - at least till you’ve got first few working. Recall - “only” one “unknown” at a time - promise that this will SAVE you time/money/effort…
Completely off topic now, but no point in making another thread.
Is there any reason not to build my own ‘Arduino’? I found this [Instructable, and it seems like what I’m looking for. It’s simple, inexpensive, and has only the features I really need. Is there any reason not to use something like this?
Signing off this topic now - however, “What is your goal?” Time, life is finite - I’ve observed that the most successful “focus” their efforts.
If your goal is to “learn to build” - make your own. If your goal is to build understanding of MCU, programming, measurement, control etc. then you risk “maximum randomness” by building your own. You will not be sure if it’s your work, your IDE, your SW which is causing problems. (and I’ve seen cases where it’s been, “all of the above.”)
By starting with at least ONE thing, “known good” you greatly increase your chances of success. I don’t feel your time/confidence is worth the 20-30 USD you’ll save by building…
Once you’ve got the basics mastered you’ll likely have developed new interests/applications - which are NOT likely to be included on the board you seek to “build.” So building “later” rather than “sooner” will best enable you to design/build something more suited to your needs - and which may be of interest to others too…
Jesse B:
Completely off topic now, but no point in making another thread.
Is there any reason not to build my own ‘Arduino’? I found this [Instructable, and it seems like what I’m looking for. It’s simple, inexpensive, and has only the features I really need. Is there any reason not to use something like this?
Thanks :)[/quote]
I have no experience with the Arduino, but I believe it has a boot loader. That instructable is a guide for putting together a premade kit and I assume the AVR has already been loaded with the boat loader. If you want to build yourself from parts that you buy seperately, I believe you’ll need an actual AVR programmer to get the Arduino bootloader on the chip.
I like that idea of the paper cut out template for the breadboard.
Since this thread started I got my ‘teensy’ in the mail. These are prettyslick Arduino-like avr processors. I have been using the Arduino IDE and only had to change the SPI bus pins. I2C worked out of the box. I have LCD, real time clock, and sd mem card working in very short order.
