New GHI installers package for hydra/gadgeteer users

Archive
21

Resolved.

22

Please only wrap c# code with the code tags for now.

23

Yeah, that last dump is useless. I think removing it will help.

24

What is this? I haven’t seen it before installing this last update. I’ve seen it a few times now and it seems to just appear randomly in the Output window.

[quote]Updating display configuration. THE MAINBOARD WILL NOW REBOOT.
If you are deploying/debugging using Visual Studio, you will need to stop (Shift-F5) and start debugging again (F5). [/quote]

25

This is needed to disable the display sockets so they can b used as GPIO but what is crazy about this is that this is not supported on hydra!

We will investigate. Thanks for the feedback.

Of course if you can give us steps to repro that will be fantastic.

26

Yea, that is odd. Especially since I don’t have a display connected. Here’s what I’ve done tonight to produce it and at least right now I seem to be able to reproduce it almost every time. Although it seems to be somewhat random.

  1. New Gadgeteer project.
  2. Add Extender module to socket #7.
  3. Add Button module to socket #14.

Add the following to bottom of ProgramStarted()


            //var pwm = extender.SetupPWMOutput(Socket.Pin.Nine);
            // Trying it this way creates the weird warning/error.
            var pwm = extender.SetupPWMOutput((Socket.Pin) 9);
            pwm.Set(25000, 0);
            Debug.Print("0%");
            Thread.Sleep(5000);
            pwm.Set(25000, 30);
            Debug.Print("30%");
            Thread.Sleep(5000);
            pwm.Set(25000, 50);
            Debug.Print("50%");
            Thread.Sleep(5000);
            pwm.Set(25000, 80);
            Debug.Print("80%");
            Thread.Sleep(5000);
            pwm.Set(25000, 100);
            Debug.Print("100%");

The output I get is…

[quote]Program Started
0%
30%
50%
80%
100%
Updating display configuration. THE MAINBOARD WILL NOW REBOOT.
If you are deploying/debugging using Visual Studio, you will need to stop (Shift-F5) and start debugging again (F5).
[/quote]

27

[quote]Updating display configuration. THE MAINBOARD WILL NOW REBOOT.
If you are deploying/debugging using Visual Studio, you will need to stop (Shift-F5) and start debugging again (F5).[/quote]

This will happen any time you either add or remove a display, or deploy firmware to the device. It should only occur the first time any of those happen. It is set up to do this in the Gadgeteer Core.

Special note: At this time, even through the display sockets (RGB or 10, 11, 12) may not be in use by a display and are marked with the Y socket type, they are not available to use as GPIO.

28

There’s definitely an issue then. I’m not using a display or any of the display sockets and the above setup will produce that error/reboot almost every time right after PWM is set to 100%.

29

Maybe the frequency at 100% is too much for the board, and it resets? I solved this two ways: either by lowering the frequency or by adding external power to the board. Which ever fits best with your application.

30

I’ll try stopping it at 99% tonight and see if that makes a difference. If the board can’t handle 100% duty cycle then there’s definitely a problem that needs to be fixed. Other FEZ boards handle this fine.

31

How would setting pwm to max would effect this! I would love to see this happening with my own eyes.

32

Did you try my steps above? If you can’t reproduce, I’ll create a video tonight.

33

Any news on an update? I see Joe & Steven have been hard at work :wink:

34

All fixes are done but we are adding more modules drivers to it. Should be this week.

35

Sweeeeeet :smiley: