@ steenis
I guess he’s off drinking coffee, so I’ll offer my two cents:
He doesn’t know what you’re doing - he is acting like the manufacturer of a mainboard and defining the sockets. When you use the gadgeteer plug-n-play view to attach modules, they use the information he supplied in his definition to see what module can be plugged into which socket.
Include the source to the module driver (BeamBreaker)
You just tell it what pins you have wired up.
Then instantiate from code:
using System;
using Gadgeteer.Modules.IngenuityMicro;
using Microsoft.SPOT;
using GT = Gadgeteer;
using GTM = Gadgeteer.Modules;
using GHI.Hardware.G120;
namespace GadgeteerApp37
{
public partial class Program
{
void ProgramStarted()
{
GT.Socket socket = GT.Socket.GetSocket(3, false, null, "");
socket.CpuPins[3] = Pin.P0_0;
BeamBreaker beamBreaker = new BeamBreaker(3);
beamBreaker.BeamBroken += new BeamBreaker.BeamEventHandler(beamBreaker_BeamBroken);
}
void beamBreaker_BeamBroken(BeamBreaker sender)
{
Debug.Print(DateTime.Now.ToString());
}
}
}
The discussion in post #33 is purely there to help you take drivers for modules and move them back to pure netmf code. Some will be easy, some will not - how easy they are is relative to how experiences you are, as well as how complex the driver is and what it relies on.
Edit:
I just got caught up on the thread and i see Justin was already doing this.
Sorry Justin I did this over the weekend and i din’t read through this thread before i posted.
Good work
I tried the MulticolorLed again. I could only connect it to 1.SPI, 4.Red, and 6.Blue, nut not to the user socket. I connected it to Blue, because that is also an X-socket. The solution compiled without errors, after uploading it stopped so quickly that I could not see error messages.
Thread.Sleep(20000);
and
Thread.Sleep(Timeout.Infinite);
did not work.
I tried to connect several other modules, but a lot could not be connected at all.
Because the G120HDR did not show in VS2010 (prof) I uninstalled everything and reinstalled everything in the the correct order. The installation was different, for instance GHI.Premium.Hardware.G120 has disappeard, also Display_HD44780 has disappeared from the Toolbox.
Can anybody give me a more comprehensive explanation on how to update the tinybooter. The G120 Developer manual is very unclear about that. From that manual I understand that I have to do something with the buttons LDR0 and LDR1 and then go to the EMX manual. There it becomes blurry: pressing Up and Down and Select and using TeraTerm. Can somebody help me ?
From the section “TinyBooter Update through GHI Boot Loader”, you need to make sure you have Tera Term installed (link in point 2 if you need it).
At this point I always open Device Manager so you can see what COM ports are visible, and what new one appears.
Then connect the device to your PC via USB cable.
Then you should see the new COM port appear in Device Manager - you might be prompted for a driver as mentioned in point 9. The device is then in GHI bootloader mode
edit: If no COM port appears, your LDR0/1 pins haven’t been successful in going into BL mode.
At this point it’s best to remove the LDR0/1 to GND jumpers/wires/switches/whatever you’ve done, so that when the device reboots it’ll come back into normal device mode.
Then start at step 10 - connect Tera Term to the new COM port shown in device manager.
Press b, then B, then V, and see it’s response each time (step 11)
Press E then Y to erase (step 13). Press X, and transfer the tinybooter (the long step 14)
So then you need to re-load the full netmf with mfdeploy.
