I did a search and found other topics on TinyCore where the use of it balloons the size of the deployed application by 60+K. Looked like all the other threads were discussing the use on pre-N+2 boards which were smaller and therefore could not handle that much code.
I just finished testing an app that I am trying to port from Gadgeteer over to the N+2. It should be able to handle the app because of the increased memory and speed. However, TinyCore is giving it problems.
If you create a blank app and add a reference to TinyCore you should see the size jump to around 64K (even with no application code added) and when you try to deploy and run you'll see the error:
Resolve: unknown type: Microsoft.SPOT.Touch.TouchGestureEventArgs
Error: ff000000
It should also be around 64K - again, without adding any application code.
Adding the Touch assembly to try to resolve the type only adds to the deployment size. I can't seem to find a way to get around the type resolution error. BTW, I'm not trying to use any of the touch or wpf features - just DispatcherTimer. I'm going to create a work around since this is a stopping point AND adding that much size to the app just for a timer doesn't make sense. It took me a while to figure out that the unknown type issue was simply the use of TinyCore so thought I would post here just in case someone else runs into a similar situation.
Thanks,
MarkNic
N+2 and (not so) TinyCore
Started by MarkNic, Dec 07 2012 02:27 PM
3 replies to this topic
#1
Posted 07 December 2012 - 02:27 PM
#2
Posted 07 December 2012 - 04:17 PM
Hi MarkNic,
Good info; thanks for sharing this.
Have you thought about changing to a System.Threading.Thread-based or System.Threading.Timer-based model?
Chris
#3
Posted 07 December 2012 - 09:33 PM
Hi MarkNic,
Good info; thanks for sharing this.
Have you thought about changing to a System.Threading.Thread-based or System.Threading.Timer-based model?
Chris
That part of the code was originally part of a component that I didn't build and over time I've replaced all almost all of the functionality through different means. The timer was something I hadn't messed with because it was working. Unfortunately, until now I hadn't taken the time to review the impact of that one single "feature".
I had the same thought as you and created a new timer today by extending a Threading.Timer and it works great and Drops the code size by ~60K. Because of that, I think my app may even fit on a N+1. I'll try that later.
I wonder who's bright idea it was to name that assembly "TinyCore"? Whoever it was, I'm sure they're still giggling.
Mark
- Arron Chapman likes this
#4
Posted 08 December 2012 - 02:14 AM
...
I wonder who's bright idea it was to name that assembly "TinyCore"? Whoever it was, I'm sure they're still giggling.
Mark
George Orwell's. Right after he wrote http://en.wikipedia....een_Eighty-Four where the "Ministry of Truth" wrote propaganda and changed records to match the current Party line, and the "Ministry of Love" tortured and brainwashed you ;-)
Have a good weekend!
Howie
- Arron Chapman likes this
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users