Welcome to the forum!
We are waiting for new SDK that will support GameO. Any moment now.
@ Rahul Karnik - does your program do anything other than
Debug.Print(...)
?
Are you using the example in the Developersā Guide: http://www.ghielectronics.com/docs/207/fez-game-o
Everything in the Developersā Guide up to, but not including, Example 3 should work. Example 3 and on, require the new SDK (due out in days).
Yes, the first example, itself didnāt seem to go anywhere beyond:
The debugging target runtime is loading the application assemblies and starting execution.
I just noticed a strange thing. I got as far as above using VS 2012. And then I quit and started up VS 2010. I am using different solutions for each version of VS (and neither are Express versions, if that could be a factor), and have used appropriately different strings in the Debug.Print statement for each project to avoid (further) confusion
and got the deployment timeout as about, but I clicked Yes when asked if I wanted to continue. And it eventually got to āAn error has occurred, please check your hardwareā
And now, when I hit the button to stop debugging, it quits and in the Debug window, I actually see
Ready.
VS2012
Whew. So I havenāt bricked it after all!
[line]
So it seems as if VS2012 manages to deploy successfully, but got stuck upon attempting to execute, whereas VS2010 manages to execute, and get the debug streams, but is unable to deploy!
I guess I could go on to the next examples, sans debugging, and at some point use runtime visual (lcd) debugging artifacts instead of Debug statements ā¦
Even if it fails once, try deploying again, with some USB connections it can be intermittent ā on one of my laptops, it is very common for me to have one deploy fail & then re-try it in the same session and it works fine. Be patient, sometimes it can be pretty slow (may depend on what else windows is doing ??)
take a look at the trouble shooting guide: http://www.ghielectronics.com/docs/165/netmf-and-gadgeteer-troubleshooting ā couple of sections on USB and also a section on checking communication with a Ping method.
also of potential help, directions for trying different USB drivers: http://www.ghielectronics.com/docs/109/usb-drivers-choices-including-winusb
I donāt know if you noticed but there is an āAdd a imageā link available when making a post. Screen shots of the output window after failed deployment can aid us in our diagnosis
@ Jeff - How is the new SDK coming out? 
@ Architect - weāre polishing up final testing, want to get it right the first time
Now I really seem to have nicely botched things up.
Pinging... TinyCLR
I ElHalSystemInfo.halVersion:
ectronics, LLCHalSystemInfo.halVendorInfo:
t GHI Electronics, LLCHalSystemInfo.oemCode: 0
HalSystemInfo.modelCode: 0
HalSystemInfo.skuCode: 0
HalSystemInfo.moduleSerialNumber:
HalSystemInfo.systemSerialNumber:
ClrInfo.clrVersion:
ClrInfo.clrVendorInfo:
ClrInfo.targetFrameworkVersion:
SolutionReleaseInfo.solutionVersion: 4.2.5.0
SolutionReleaseInfo.solutionVendorInfo: Copyright (C) GHI Electronics, LLC
SoftwareVersion.BuildDate: Apr 25 2013
SoftwareVersion.CompilerVersion: 410713
FloatingPoint: True
SourceLevelDebugging: True
ThreadCreateEx: True
LCD.Width: 0
LCD.Height: 0
LCD.BitsPerPixel: 0
AppDomains: True
ExceptionFilters: True
IncrementalDeployment: True
SoftReboot: True
Profiling: False
ProfilingAllocations: False
ProfilingCalls: False
IsUnknown: False
Ping works (mostly returns tynclr, but also an occasionally tinybooter), so does the above (device capabilities), and firmware deployment ( of course, firmware.hex hangs on āchecking signatureā even though it says āpassā in the console, but config.hex does pass.
At this point either VS version doesnāt get far in deploying anything.
Currently using the winusb driver but that doesnāt appear to make any difference.
Unfortunately I only have USB 3.0 ports and I donāt have a powered hub handy so am wondering if AAA batteries would do the trick, and of course, where I would find a pre-built image and how Iād strap it in to restore to a working point ā¦
@ Rahul Karnik -
[ol]go to GHI web sites supportās page for .NET Micro Framework: http://www.ghielectronics.com/support/.net-micro-framework
use step 4 to download FEZ Config (Beta), unzip it
plug your Gameo into the computer
run the FEZ Config .exe
make sure Device is USB and you should see "Cerb-Family_Gadgeteer
click on Firmware Updater
click on FEZ Cerebus (leave all check boxes in the panel unchecked)
after the firmware files list appears, click Next
click on OK for dialog that pops-up
click on Next when you get the TinyBooter info Dialog
click Yes in the All Data will be Deleted Dialog
be patient while the application works
if a dialog pops-up, there is no device connected, cllick OK and unplug and plug gameo
close the FEZ Config Utility[/ol]
Do NOT try to update TinyBooter.
@ Rahul Karnik - After consulting with other people, there is still an opinion that the device firmware may not be the problem; rather, problems with USB. In which case the procedure I outline (1) may not be necessary, and (2) may not work. So if you read this message at the same time as my previous, try switching USB drivers first: http://www.ghielectronics.com/docs/109/usb-drivers-choices-including-winusb
Wunderbar.
I swapped back to the GHI_NETMF_Interface driver
Fez_Config_013 still didnāt do any better so I used MFDeploy, same story.
Then I followed a thread that suggested trying āDeploy with PortBooter Commandā, after which MFDeploy still hung during the signature check stage but then some of the other diagnostics such as Show Device Info began working
Then I used Fez_Config_013 and it did do something when I click on Device Version, which wasnāt working earlier. However it showed nothing no version for Loader (TinyBooter), but did show 4.2.5.0 for Firmware (TinyCLR)
So next I went ahead with the Firmware Updater, which did things differently this time, first warning me that TinyBooter would not get updated bla bla. I simply clicked next etc., and voila, success.
Now VS2010 actually works and deploys nicely. Still on Example 1 so far. Probably should go through all the examples before posting this ā¦
Thanks!
Update: I think what really worked was my trying one of the other USB ports (the ones on the right are awkwardly located for my couch arm comfort access).
Note to self. Never forget to remember original note to self. Make only one change at a time!!
Update update: Example 2 works, buttons detected
However, no luck getting the LCD to do anything. One combination of I forget which sample program from Codeshare got it all completely lit up white completely. But nothing more than that, and now itās blacked out again.
Hereās what Iām running:
using System;
using Microsoft.SPOT;
using Microsoft.SPOT.Hardware;
using System.Threading;
using Microsoft.SPOT.Presentation.Media;
// using TestGameoEmulator;
namespace GameoText2LCD
{
public class Program
{
public static void Main()
{
Bitmap bmap = new Bitmap(160, 120);
bmap.DrawText("hello", Resources.GetFont(Resources.FontResources.small), Color.White, 0, 0);
bmap.Flush();
Debug.Print("height: " + bmap.Height.ToString() + ", width: " + bmap.Width.ToString());
for (int i = 0; i < bmap.Height; i++)
{
for (int j = 0; j < bmap.Width; j++)
{
if (!bmap.GetPixel(i, j).ToString().Equals("0"))
{
Debug.Print(i.ToString() + ", " + j.ToString() + ": " + bmap.GetPixel(i, j).ToString());
}
}
}
Debug.Print("---");
Thread.Sleep(-1);
}
}
}
And hereās the output:
Found debugger!
Create TS.
Loading start at 8051ff4, end 807c374
Assembly: Microsoft.SPOT.Hardware.SerialPort (4.2.0.0) Assembly: Microsoft.SPOT.IO (4.2.0.0)
Assembly: System.IO (4.2.0.0) Assembly: Microsoft.SPOT.Hardware.OneWire (4.2.0.0)
Assembly: Microsoft.SPOT.Hardware.Usb (4.2.0.0) Assembly: System.Xml (4.2.0.0)
Assembly: Microsoft.SPOT.Hardware.PWM (4.2.0.1) Assembly: Microsoft.SPOT.Net (4.2.0.0)
Assembly: System (4.2.0.0) Loading Deployment Assemblies.
Attaching deployed file.
Assembly: GameoText2LCD (1.0.0.0) Resolving.
The debugging target runtime is loading the application assemblies and starting execution.
height: 120, width: 160
0, 3: 16777215
0, 4: 16777215
0, 5: 16777215
0, 6: 16777215
0, 7: 16777215
...
...
...
18, 6: 16777215
18, 7: 16777215
18, 8: 16777215
19, 5: 16777215
19, 9: 16777215
20, 5: 16777215
20, 9: 16777215
21, 5: 16777215
21, 9: 16777215
22, 6: 16777215
22, 7: 16777215
22, 8: 16777215
---
Nothing on the LCD yet though
Hi,
I seem to have a USB Driver issue for the Game-O. I have the FEZ_Config_v013 utility running and when I plug the device in to the USB slot, I get the installing driver (Cerb Family) and then the USB device is not recognised. If I unplug it again and plug it back in. The driver shows Cerb family - Gadeteer appears for a second in the Device section of the Config tool then disappears and the windows Unregcognised USB device message appears again.
Itās connecting to a USB 3 port on a Sony Vaio laptop running windows 8 Pro (64 bit)
Any ideas?
Cheers,
Jas
@ Rahul Karnik - Check your font color versus screen color.
@ Jeff - on the emulator, things will show by default but donāt we need to initialize the display on gameo first?
@ Rahul Karnik - per Gus[quote] @ Jeff - on the emulator, things will show by default but donāt we need to initialize the display on gameo first?[/quote]
I apologize for wasting your time, the program can be run in emulator, but not on your device until the SDK is released. So in post #186, I should have said the first 2 examples only.
Sdk should be ready on Monday, fingers crossed.
Wouldnāt you be able to code quicker with fingers ā¦ uncrossed?
1 Like
@ jasuk70 - I tried it on a VAIO Series S laptop, running Win 8; on all 3 of its USB ports with no problems. You probably know the material, but just in case, I suggest reading the the sections on USB and Unexplained Failures in the trouble shooting guide http://www.ghielectronics.com/docs/165/netmf-and-gadgeteer-troubleshooting
also our document on USB drivers: http://www.ghielectronics.com/docs/109/usb-drivers-choices-including-winusb
No time wasted at all.
Is there any way to flash the pre-loaded binary from somewhere (without recompiling or anything) to play Pong again?
@ Rahul Karnik - not currently, but the SDK really will be out VERY soon.