Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.
Photo

Shield Base Firmware v4.2.0.1 (beta 1)


  • Please log in to reply
36 replies to this topic

#21 Kristoffer

Kristoffer

    Advanced Member

  • Members
  • PipPipPip
  • 37 posts

Posted 17 July 2012 - 08:55 PM

.....
Could you try flashing your Netduino Go with the attached (unofficial) firmware? Just flash all three files using ST's "DfuSe demonstrator" program.
....


Doing this solved my problem:

Running the ShieldBase firmware update stalled at line 180 in STM32Bootloader.cs

_bootloaderPort.Write(true);
And nothing happened until I forced the execution to stop.

I flashed the Netduino Go with the unoffical software and ran the ShieldBase firmware update again without any problems

#22 rcflyair

rcflyair

    New Member

  • Members
  • Pip
  • 7 posts

Posted 19 July 2012 - 03:54 AM

Evening!

I'm experiencing the same type of problem....

A first chance exception of type 'System.Exception' occurred in NetduinoGo.ShieldBase.dll
An unhandled exception of type 'System.Exception' occurred in NetduinoGo.ShieldBase.dll

It occurs on creating either an OutputPort or InputPort object targeted for the ShieldBase.

using System;
using System.Threading;
using Microsoft.SPOT;
using Microsoft.SPOT.Hardware;
using SecretLabs.NETMF.Hardware.NetduinoGo;
//using SecretLabs.NETMF.Hardware;
//using SecretLabs.NETMF.Diagnostics;

namespace NetduinoGo_v01
{
    public class Program
    {
        // Create ShieldBase Object
        public static NetduinoGo.ShieldBase sb = new NetduinoGo.ShieldBase(GoSockets.Socket5);

        public static void Main()
        {
            Debug.Print("Main");
            OutputPort D13 = new OutputPort(sb.Pins.GPIO_PIN_D13, false);
            //InputPort D13 = new InputPort(sb.Pins.GPIO_PIN_D13, true, Port.ResistorMode.Disabled);
            //bool state = false;

            while (true)
            {
               D13.Write(true);
               //state = D13.Read();
               //Debug.Print(state.ToString());
               Thread.Sleep(500);
               //D13.Write(false);
               //Thread.Sleep(500);
            }
            //sb.Dispose();


        }

    }
}

I've flashed the shieldbase a few times, then flashed the unofficial netduinogo firmware and re-flashed the shieldbase a few times.

At a loss.....

#23 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 20 July 2012 - 09:23 PM

Hi rcflyair, Just following up to make sure you're up and running... Did the solution in the other thread solve this issue for you? http://forums.netdui...dpost__p__32366 Chris

#24 rcflyair

rcflyair

    New Member

  • Members
  • Pip
  • 7 posts

Posted 21 July 2012 - 02:09 PM

Morning! Yup, I've got my little program working great, and I've even managed to bring in the other three modules included in the starter kit and have them functioning as well (at the same time!). Thanks heaps!

#25 NXTwoThou

NXTwoThou

    Advanced Member

  • Members
  • PipPipPip
  • 68 posts
  • LocationTulsa, OK

Posted 06 August 2012 - 07:57 PM

How does one revert back to the previous firmware? I tested my app, then reflashed the firmware hoping to improve some of the other nagging random lockups, now I get exceptions when trying to init the shieldbase unless I unplug everything from the digital I/o ports. I thankfully have 2 other shieldbases here that I could plug in to continue my other testing. So sick of this. When is this thing going to be ready?

#26 Hugh Hoover

Hugh Hoover

    New Member

  • Members
  • Pip
  • 8 posts
  • LocationEnumclaw

Posted 09 August 2012 - 08:06 PM

Hi - I am trying to update my shield firmware with the 4.2.0.1 update - but I'm running into issues right away. The flashing app fails on the very first call to GetAck - where it receives back 0x00 instead of the required 0x79. I had to reflash the 4.2.0 firmware on my Go! a couple of days ago - so it's got fresh firmware on it. Any suggestions?

#27 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 09 August 2012 - 08:37 PM

Hi hhoover,

Hi - I am trying to update my shield firmware with the 4.2.0.1 update - but I'm running into issues right away.
The flashing app fails on the very first call to GetAck - where it receives back 0x00 instead of the required 0x79.

I had to reflash the 4.2.0 firmware on my Go! a couple of days ago - so it's got fresh firmware on it.

What socket do you have the Shield Base connected to?

Have you tried reseating the IDC cable to ensure that it's connected on both ends?

Do you have any other modules connected to your Netduino Go mainboard?

Do you have anything plugged into your Shield Base?

Chris

#28 Hugh Hoover

Hugh Hoover

    New Member

  • Members
  • Pip
  • 8 posts
  • LocationEnumclaw

Posted 09 August 2012 - 09:25 PM

Hi hhoover,


What socket do you have the Shield Base connected to?

Have you tried reseating the IDC cable to ensure that it's connected on both ends?

Do you have any other modules connected to your Netduino Go mainboard?

Do you have anything plugged into your Shield Base?

Chris


A few more details? ;^)
plugged into socket 5, which is the default socket for the app. No other modules plugged in, nothing plugged into Shield Base.
cables... hmmm. Hadn't try fiddling with them -
now:
damn! it's working now. where did I put that cable down...

hardware 101... you'd think I'd learn - of course, it's been almost 30 years since I last played seriously with actual hardware... :)
The funny thing is that I'd tried this last night, and was getting back 0x80, instead of 0x00... I DID unplug / replug the shield base between at least once.

Ok - now I take it I have to remove the shield base and load a different program if I don't want to reflash every time I plug the Go! into USB...

Thank you!

#29 kenNET

kenNET

    Advanced Member

  • Members
  • PipPipPip
  • 69 posts
  • LocationSweden

Posted 30 August 2012 - 08:04 PM

Hi, Is I2C working on the Shield ? (pin A4, A5 like old Netduino) I have updated my Shield to Version: 4.2.0.1 beta 1, but don't get I2C working. /Ken

#30 GregR

GregR

    Advanced Member

  • Members
  • PipPipPip
  • 32 posts
  • LocationKeller, Tx

Posted 30 August 2012 - 08:08 PM

Hi,

Is I2C working on the Shield ? (pin A4, A5 like old Netduino) I have updated my Shield to Version: 4.2.0.1 beta 1, but don't get I2C working.

/Ken



From what I remember reading I2C will be the last thing to be supported on the Shieldbase...

#31 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 30 August 2012 - 08:15 PM

Hi Ken, I2C will be the last feature implemented. We're wrapping up SPI right now, and UART will be next. Chris

#32 kenNET

kenNET

    Advanced Member

  • Members
  • PipPipPip
  • 69 posts
  • LocationSweden

Posted 30 August 2012 - 08:55 PM

Hi Ken,

I2C will be the last feature implemented. We're wrapping up SPI right now, and UART will be next.

Chris


Ok, when do you think I2C will work Chris?

Now it feels like I got me a GO, Nwazet Go Tinker Kit and two sheilds that I can not use as I thought ;-)

/Ken

#33 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 31 August 2012 - 04:27 PM

Hi Ken,

Ok, when do you think I2C will work Chris?

Now it feels like I got me a GO, Nwazet Go Tinker Kit and two sheilds that I can not use as I thought ;-)

/Ken

We're planning on enabling both SerialPort and SPI this coming month (September). I2C support is scheduled about a month out right now.

BTW, there's been a lot of work behind the scenes for Shield Base recently. We'll have lots to share very soon.

Chris

#34 GregR

GregR

    Advanced Member

  • Members
  • PipPipPip
  • 32 posts
  • LocationKeller, Tx

Posted 31 August 2012 - 04:46 PM

Ok, when do you think I2C will work Chris?

Now it feels like I got me a GO, Nwazet Go Tinker Kit and two sheilds that I can not use as I thought ;-)

/Ken



I'm right here with Ken on this one. Got a table top full of toys...with alot of $$$ invested...but cannot use them the way I thought I could. I was thinking that the Go! would be backwards compatible at a minimum in that I could use the Shield Base connected to the Go! and have it act just like a Netduino/Netduino+. That is not the case..and to be honest I am starting to lose interest. I understand this is a new product...just expected it to be able to do what the previous Netduinos can do from the start.

Just my $.02 worth... :)

#35 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 31 August 2012 - 08:54 PM

Hi Greg, With the Shield Base, we listed it as beta with a list of supported features at launch. But I also know that we normally only ship products which are feature-complete, so I understand the expectation. We'll have an update for the Shield Base which enables additional features soon. I2C is still probably coming in October...but we can get SerialPort and SPI support out in September. Thank you for your enthusiasm, patience, and feedback. Especially the feedback. Chris P.S. There are some features coming to Netduino Go which we didn't talk about at launch. We will have some surprises in a few weeks which should make your investment in Netduino Go even more worthwhile. Both with Shield Base and without...

#36 Fabien Royer

Fabien Royer

    Advanced Member

  • Members
  • PipPipPip
  • 406 posts
  • LocationRedmond, WA

Posted 20 September 2012 - 01:47 AM

Greg, Ken,

I wanted to let you know that the Nwazet DAQ module provides an I2C interface and it works with sensors anywhere from 10kHz to 400kHz.
This module only takes a single socket on the Go! main board and uses a 16 MHz SPI interface.

Cheers,
-Fabien.

#37 GregR

GregR

    Advanced Member

  • Members
  • PipPipPip
  • 32 posts
  • LocationKeller, Tx

Posted 20 September 2012 - 05:03 AM

Greg, Ken,

I wanted to let you know that the Nwazet DAQ module provides an I2C interface and it works with sensors anywhere from 10kHz to 400kHz.
This module only takes a single socket on the Go! main board and uses a 16 MHz SPI interface.

Cheers,
-Fabien.



Fabien,

Looks like a very nice module! But I cannot justify spending another $80 just for I2C when I have 2 ShieldBases just sitting here waiting to be used and collecting dust. :(

Greg




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.