Main Site Documentation

Project - G120HDR Gadgeteer Mainboard


#1

I just posted G120HDR Gadgeteer Mainboard on Codeshare. Feel free to discuss and make suggestions here.


#2

This is great one, thanks. We should add it to the developer’s guide :slight_smile:

For the custom socket, a user can follow the code and create their own.


#3

Just add the pins to the socket…

https://www.ghielectronics.com/community/forum/topic?id=12508&page=8#msg127457


#4

Thanks Justin.
I didn’t know you were doing this or else i would have just waited for yours.


#5

@ MikeCormier - No drama, yours is probably better tested than mine :wink:


#6

Thanks!


#7

Using the latest Gadgeteer Core released on August 27 (“4.2 R2”). I am getting the following error/warning in the output window:

Warning: socket 5 is not compliant with Gadgeteer : Cpu pin 3 must be specified for socket of type D
Warning: socket 5 is not compliant with Gadgeteer : Cpu pin 6 must be specified for socket of type D
Warning: socket 5 is not compliant with Gadgeteer : Cpu pin 7 must be specified for socket of type D.

Your Code in the Mainboard Drive needs to be changed:

{
‘D’
};
numberedSocket5.CpuPins[3] =[em] Cpu.Pin.GPIO_NONE[/em];
numberedSocket5.CpuPins[4] = Cpu.Pin.GPIO_Pin14;
numberedSocket5.CpuPins[5] = (Cpu.Pin) 31;
numberedSocket5.CpuPins[6] = [em]Cpu.Pin.GPIO_NONE[/em];
numberedSocket5.CpuPins[7] = [em]Cpu.Pin.GPIO_NONE[/em];
numberedSocket5.CpuPins[8] = Cpu.Pin.GPIO_NONE;
numberedSocket5.CpuPins[9] = Cpu.Pin.GPIO_NONE;
Socket.SocketInterfaces.RegisterSocket(numberedSocket5);
Socket numberedSocket6 = Socket.SocketInterfaces.CreateNumberedSocket(6);
numberedSocket6.SupportedTypes = new char[2]


#8

That is the error message that i specified as happening in the code share page.
It is due to the fact that there is no cpu pins wired to those pins on the socket.
You can safely ignore those warnings.


#9

I use G120 to connect TE35 , but in the Program.gadgeteer it appears to be that R of TE35 is connected to B of G120, and B of TE35 connected to R of G120. Anyone could answer me please?


#10

it appears like this.


#11

And my TE35 screen is always all white, I need help!!!


#12

@ a31415926 -
i’ll check it out
can you post your code so i can test it


#13

Haa, sorry, I am a beginner. I have no codes, I just use the original debug codes

using System;
using System.Collections;
using System.Threading;
using Microsoft.SPOT;
using GHI.Premium.Hardware;
using GHI.Premium.IO;
using GHI.Premium.System;
using 

using Gadgeteer.Networking;
using GT = Gadgeteer;
using GTM = Gadgeteer.Modules;
using Gadgeteer.Modules.GHIElectronics;

namespace GadgeteerApp9
{
    public partial class Program
    {
        // This method is run when the mainboard is powered up or reset.   
        void ProgramStarted()
        {
            /*******************************************************************************************
            Modules added in the Program.gadgeteer designer view are used by typing 
            their name followed by a period, e.g.  button.  or  camera.
            
            Many modules generate useful events. Type +=<tab><tab> to add a handler to an event, e.g.:
                button.ButtonPressed +=<tab><tab>
            
            If you want to do something periodically, use a GT.Timer and handle its Tick event, e.g.:
                GT.Timer timer = new GT.Timer(1000); // every second (1000ms)
                timer.Tick +=<tab><tab>
                timer.Start();
            *******************************************************************************************/


            // Use Debug.Print to show messages in Visual Studio's "Output" window during debugging.
            Debug.Print("Program Started");
        }
    }
}

and my output window appears like that:
could you help me, thanks a lot lot lot, I am almost crazzzzzy.

Found debugger!

Create TS.

Loading start at a0e85838, end a0e9cf94

Assembly: mscorlib (4.2.0.0) Assembly: Microsoft.SPOT.Native (4.2.0.0) Assembly: Microsoft.SPOT.Hardware (4.2.0.0)
Assembly: Microsoft.SPOT.Hardware.PWM (4.2.0.1) Assembly: Microsoft.SPOT.Security.PKCS11 (4.2.0.0)
Assembly: System.Security (4.2.0.0) Loading Deployment Assemblies.

Attaching deployed file.

Assembly: GHI.Premium.IO (4.2.11.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Graphics (4.2.0.0) Attaching deployed file.

Assembly: GHI.Premium.System (4.2.11.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Touch (4.2.0.0) Attaching deployed file.

Assembly: GTM.GHIElectronics.UsbClientDP (4.2.100.0) Attaching deployed file.

Assembly: Microsoft.SPOT.TinyCore (4.2.0.0) Attaching deployed file.

Assembly: IngenuityMicro.Gadgeteer.G120Hdr (1.0.2.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Net (4.2.0.0) Attaching deployed file.

Assembly: System.IO (4.2.0.0) Attaching deployed file.

Assembly: GTM.GHIElectronics.Display_TE35 (4.2.100.0) Attaching deployed file.

Assembly: Gadgeteer (2.42.0.0) Attaching deployed file.

Assembly: GHI.Premium.Hardware (4.2.11.0) Attaching deployed file.

Assembly: Microsoft.SPOT.IO (4.2.0.0) Attaching deployed file.

Assembly: GadgeteerApp9 (1.0.0.0) Resolving.

Link failure: some assembly references cannot be resolved!!

Assembly: IngenuityMicro.Gadgeteer.G120Hdr (1.0.2.0) needs assembly ‘GHI.Premium.IO’ (4.2.10.0)

Assembly: IngenuityMicro.Gadgeteer.G120Hdr (1.0.2.0) needs assembly ‘GHI.Premium.Hardware’ (4.2.10.0)

Assembly: IngenuityMicro.Gadgeteer.G120Hdr (1.0.2.0) needs assembly ‘GHI.Premium.System’ (4.2.10.0)

Assembly: GadgeteerApp9 (1.0.0.0) needs assembly ‘IngenuityMicro.Gadgeteer.G120Hdr’ (1.0.2.0)

Error: a3000000

Waiting for debug commands…

程序[13] Micro Framework application: 托管已退出,返回值为 0 (0x0)。


#14

the references that added as follow


#15

you are using a different driver than mine. it is targeting a different assembly.
uninstall the g120hdr driver you have and install the one i wrote.
https://www.ghielectronics.com/community/codeshare/entry/755

it is working fine


#16

@ MikeCormier -
I should say thank you very very much!!!
It is cool and works well!!
my display shows something now~~ and debug is OK, but in the out put window it shows some warning. I dont know what that means (do these not matter?)

Warning: socket 5 is not compliant with Gadgeteer : Cpu pin 3 must be specified for socket of type D
Warning: socket 5 is not compliant with Gadgeteer : Cpu pin 6 must be specified for socket of type D
Warning: socket 5 is not compliant with Gadgeteer : Cpu pin 7 must be specified for socket of type D
Using mainboard GHI Electronics G120HDR version 2.0
Program Started


#17

@ a31415926 - you can safely ignore those messages.

As this was not officially a Gadgeteer board GHI did not not wire up those pins so it is not compliant to the D socket spec. it is just notifying the programmer as such and will not effect your program in any way. just remember that those pins are not connected to anything.

Glad it’s working for you


#18

@ MikeCormier -
Thank you very much!
But I come across with another problem, when I connect the G120 with CAN DW module, it is said like follow. Is it because of that 4 and 6 are not specified?


#19

@ MikeCormier -
and my G120 version is G120HDR 1.1 not 2.0
does it matter?


#20

@ andre.m -
how can I do that? You mean I should define the socket with pins by myself? Is that very complex, I don’t know what to do!