Messages

16

TinyDuino Processors & TinyShields / Re: TinyArcade and memory usage

« on: January 05, 2016, 02:28:09 AM »

Another question regarding memory on the TinyArcade. Out of the 256KB flash memory, how much will be available to the app? Is any flash memory (or SRAM) reserved for your game loading code or any other kind of boot loader?

17

TinyDuino Processors & TinyShields / Re: TinyArcade and the SD card reader

« on: January 05, 2016, 02:26:13 AM »

Cool! And I guess writing to the SD is fine too, for save files like a high score table?

How is new code loaded into memory? Is the executable linked with all addresses PC relative, so it can be loaded anywhere into memory or does it have a reserved address space? I'm just wondering how feasible it would be to split my code up into different parts that is loaded at different times, to save Flash Memory.

18

TinyDuino Processors & TinyShields / TinyArcade and the SD card reader

« on: January 03, 2016, 10:29:52 AM »

Will it be possible to read from the SD card in a TinyArcade app?

Both into SRAM and Flash Memory would be interesting, but I assume the Flash Memory have a limited number of writes to it?

19

TinyDuino Processors & TinyShields / Re: TinyArcade and memory usage

« on: January 03, 2016, 10:27:05 AM »

Cool, thanks for clearing that up!

Looking through the source for Arduino has been very useful. I've been curious how functions like millis and micros was implemented.

20

TinyDuino Processors & TinyShields / Re: TinyArcade and memory usage

« on: December 29, 2015, 05:05:18 PM »

Oh ok, so I can use everything that comes with standard C/C++ like malloc/free and new/delete? Are the libraries pre built as library files for each platform or do they come as c/cpp files that are compiled for the proper platform at build time?

I've been programming c and c++ for 15+ years but I'm new to Arduino and still a bit confused as to what the Arduino app can and cannot do.

It seems like my .ino file is basically renamed to .cpp and built with a template program that contain a C entry point with a main loop that call the loop function in my ino file, but I don't have my computer around so I can't verify that.

21

TinyDuino Processors & TinyShields / TinyArcade and memory usage

« on: December 26, 2015, 09:45:11 AM »

Hi everyone!

First of all, I'm super excited about the TinyArcade! I ordered the 3 DIY kits and is eagerly awaiting their arrival.

I'm preparing some games for it and have a few questions, but I figured I should start one thread per question to keep it simply, I hope that is ok!

So first of, memory on the TinyArcade.

If TinyArcade is based on Arduino Zero, and the Arduino Zero have 256 KB FLASH and 32 KB SRAM, will the TinyArcade also have 256 KB flash and 32 KB SRAM? Will the code execute from FLASH or does the executable AND runtime data need to exist in the 32 KB SRAM?

Also, is there a memory handler for the 32 KB SRAM?

Cheers!

22

TinyDuino Processors & TinyShields / Re: Combining different shields

« on: November 25, 2015, 10:07:12 AM »

Excellent, thank you both for the help!

That compatibility matrix is exactly what I was looking for. The signals that goes through the connector, how do they not conflict with each other? Is each shield on its own pin, with some form of serial protocol to transfer data? I've read through the TinyScreen library code ( https://github.com/TinyCircuits/TinyCircuits-TinyScreen_Lib ) and found that the screen can be on GPIO address 0x20 or 0x21. Are those addresses what makes sure that the shields doesn't conflict?

How many shields can the battery power? Is there a limit or is it simply a matter of how quickly the battery will drain?

As you can probably tell I'm still learning a lot about the hardware.

I am super close to getting a Tiny Game kit just to get cracking on the basics, but the big difference in clock speed and SRAM makes me wonder if I should get an Arduino Zero instead, and .. uhm .. yeah, I don't really know what display to get instead. But if I have a 16 bit display buffer in SRAM then I could write an abstraction layer to blit it to any kind of display. As I would want to do for the joystick.

23

TinyDuino Processors & TinyShields / Combining different shields

« on: November 23, 2015, 04:04:59 PM »

Hi everyone,

First time poster here.

I have just found out about Tinyduino and Tiny Arcade and I must say, I'm super excited! I'm not sure I can hold off until the Tiny Arcade is funded and shipping so I figured I should just order the parts so I can get cracking on making games for it.

I have two questions and I've searched these forums without finding the answer. I hope I'm not asking rookie questions and you can all still accept me.

1) What are the limitations for combining different shields? Can I simply attach any combination of shields and build what ever monster I'd like? For example, can I have audio, screen, micro sd, real-time clock and gps? How can I know which shields I can combine?

2) For the Tiny Arcade, is there a new joystick and audio shield developed, or can I get the game kit and audio shield and expect to run my code on the Tiny Arcade?

Cheers,
Magnus