Netduino home hardware projects downloads community

Jump to content

  2. → SteveS's 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.

SteveS's Content

There have been 20 items by SteveS (Search limited from 26-April 23)


By content type

See this member's

Sort by                Order  

#36773 PCF8574 and some LEDs

Posted by SteveS on 08 October 2012 - 02:14 PM in Project Showcase

Ok, after reading about the i2cdevice, it seems like it takes 7bit adresses, it's masking away the r/w bit, so I guess it's shifted down one bit. That means you should try 38hex instead if you put a0-a2 low and you have the A chip.
If you have the non-A chip,it would mean 20hex as adress, and then I understand the above example, and the linked example..


That's right. The Wire library used in Arduino does exactly that too. On a couple of boards I built where I had I2C slaves that supported A0..An pins, I put either jumpers or a DIL switch to allow me to set the address, but where you will only have a single device, hardwiring is usually easier. Some devices, like the RTC (DS1307?) don't support it anyway, although I'm not sure why you'd want more than RTC

SteveS


#36188 We interrupt this program

Posted by SteveS on 28 September 2012 - 03:34 PM in Netduino Go

And since I live in the UK, it doesn't help me much either. My day job doesn't let me pop over to the U.S. for the weekend. Mind you, since 29th just happens to be my 50th birthday, it would have been a good weekend to go....


#35862 Mini Upgrade Woes

Posted by SteveS on 23 September 2012 - 05:09 PM in Netduino Mini

Great! After a somewhat tiresome day at the office yesterday (and Saturday isn't a good day for that anyway), I have had a fun 20 minutes reflashing my mini devices. I am very pleased to report that it all went smoothly, and I'm now planning on doing the same with my N/N+ boards to bring them up to the latest firmware. Many thanks, Chris. SteveS


#34641 Mini Upgrade Woes

Posted by SteveS on 04 September 2012 - 07:59 AM in Netduino Mini

Hi SteveS,

Thanks for testing this. It might be seeing the same core issue. We'll pull it in and try to fix both at the same time.

You're welcome. I've been a software developer for 30+ years, so I know how it is. Stuff happens.


Can you use TTL for deployment for the moment?

Chris

As it happens, yes - I'll be doing some work on an N, rather than a mini for the next phase of my project.


SteveS


#34634 Mini Upgrade Woes

Posted by SteveS on 03 September 2012 - 09:12 PM in Netduino Mini

Hi Chris

Not exactly good news. I was able to build and deploy it, but it doesn't seem to run. I have Putty running on both a USB/TTL adaptor connected to Tx0/Rx0 and on COM1 connected to DTX0/DRX0, and nothing seems to be coming out of either port.

I am going to try 'hard-setting' the transport port using the code in the selector as a guide, to see if that works.
Unfortunately it's been a busy weekend, so I wasn't able to do this yet.

SteveS


I tried setting the interface to Com1 and Com2, neither of which seem to make the RS232 port work as the transport, so I guess I will need to wait for the new firmware. :(

SteveS


#34590 Mini Upgrade Woes

Posted by SteveS on 03 September 2012 - 08:11 AM in Netduino Mini

Please let us know how this works for you.
Chris


Hi Chris

Not exactly good news. I was able to build and deploy it, but it doesn't seem to run. I have Putty running on both a USB/TTL adaptor connected to Tx0/Rx0 and on COM1 connected to DTX0/DRX0, and nothing seems to be coming out of either port.

I am going to try 'hard-setting' the transport port using the code in the selector as a guide, to see if that works.
Unfortunately it's been a busy weekend, so I wasn't able to do this yet.

SteveS


#34441 Mini Upgrade Woes

Posted by SteveS on 30 August 2012 - 04:42 PM in Netduino Mini

OK. I have upgraded the firmware to TTL successfully. However, I cannot deploy the transport selector, nor can I build it for 4.2 and deploy it. However, it reassures me somewhat that I haven't done anything with the mini to permanently destroy it. Also, I have deployed an app to it that uses the 12v serial connection successfully, so I'm almost there... Is there a prebuilt 4.2 transport selector anywhere I can download and deploy? SteveS


#34060 COM1, COM2 - which is which (USB/TTL, RS232)

Posted by SteveS on 22 August 2012 - 01:10 PM in Netduino 2 (and Netduino 1)

Doh! I have the pinout PDFs printed out and on a cork-board! Shame I didn't look more closely. (I do have an excuse - my advanced years mean I wear varifocals, and unless I squint and sit very close, I can't read them... Only the Mini has direct connection support for RS232 levels, so that just leaves my last query, every thing else is sorted. Thanks. SteveS


#34054 COM1, COM2 - which is which (USB/TTL, RS232)

Posted by SteveS on 22 August 2012 - 08:48 AM in Netduino 2 (and Netduino 1)

Hi. I'm pretty sure this isn't a new question, but I couldn't see a suitable answer, so I'm asking anew. I have a number of different Netduino models (vanilla, Plus, Mini). Since there are both TTL level and RS232 level Tx/Rx pairs, I assume these map TX0/RX0 = COM1, DTx/DRx = COM2. Firstly, do I have these the right way around or not? Secondly, does the transport selection change the port assignments? Thirdly, am I right in thinking that when debugging, the transport selected means the relevant port is not available? Finally, can the transport be identified from within the CLR in some way (in other words, can an app determine which the debugging port is)? I'm wanting to interface to some serial hardware which, like the Netduino, has both 232 and TTL levels (although there's only one UART, there's a MAX232, solder-pad selectable). Since I have spare digital I/O, it occurred to me to hack the solder pads so I can software switch the mode. Power-cycling the device isn't an issue, since I'm using another pin to do just that :) SteveS


#34052 Mini Upgrade Woes

Posted by SteveS on 22 August 2012 - 08:23 AM in Netduino Mini

I'm told that the TTL firmware is working properly. You might be able to flash that and then change the transport to RS232 (using TTL). We're investigating, and hope to have a resolution soon...

Chris

That's reassuring to hear.
I'll try the TTL firmware. Luckily for me, the dev board has a USB connection on it as well, so I don't even have to dig out a TTL cable.

I'll get the instructions for the TTL install, try that, and post the results here. Since I'm only upgrading a few Mini devices, that extra step won't be too much hassle, providing I can change the transport successfully.

SteveS


#34033 Mini Upgrade Woes

Posted by SteveS on 21 August 2012 - 09:56 PM in Netduino Mini

OK, I haven't confused them. Are there alternative f/w 4.2 files I can try, or can I connect via PuTTY and see what's being spat out of the serial port (if anything)? If so, what baud rate will I need?


#34032 Mini Upgrade Woes

Posted by SteveS on 21 August 2012 - 09:42 PM in Netduino Mini

Doh! Where's an embarassed smiley when you need one? Of course there isn't.


Don't worry, I have quite a collection of them...

OK. More progress of a sort. I can force the device into TinyBooter mode, not surpisingly.
I can also reflash the 4.1 tinybooter, and 4.1 RS232 firmware, and it all works perfectly.

So, my original question stands, what am I doing wrong?
I notice that in the 4.1 f/w download, there are .sig files, but not in 4.2

Also, is it significant that when flashing the 232 image for 4.2, I don't get the 'Chk signature' message?
To me it looks as though something is either eating the output, or supressing it from the device.

I'm _pretty_ sure I haven't confused the TTL and RS232 f/w, but if I had, would I see this kind of behaviour?

SteveS


#34017 Mini Upgrade Woes

Posted by SteveS on 21 August 2012 - 03:21 PM in Netduino Mini

Hi SteveS,

The DTR pin is useful for kicking the Netduino Mini into TinyBooter during powerup...but you'll want to drive the RESET pin low instead to reset the Netduino Mini.

Chris

[fx: slaps forehead]
Yes, I will, won't I?

On the other hand, if I put it into TinyBooter mode, I can then make sure that MFDeploy can then see it, which currently, it can't. If it does, and I click 'Erase', does that actually wipe ER_CONFIG and ER_FLASH from the device, or just the application (if any)?

When I write ER_FLASH, it (MFDeploy) does tell me at the end, via a dialog box, that it's starting the application. This is news to me, since I haven't deployed one yet...

Steve


#34009 Mini Upgrade Woes

Posted by SteveS on 21 August 2012 - 01:09 PM in Netduino Mini

Oh, and on the subject of the SK Pang dev board, I now have an elevated ZIF socket adaptor which uses heatshrink wrapped long pinned sockets. Now I don't need to worry about damaging my Minis. Steve


#34008 Mini Upgrade Woes

Posted by SteveS on 21 August 2012 - 01:07 PM in Netduino Mini

Try the "push the button when connecting to MFDeploy" trick. That worked for my very similar Netduino Plus flashing problems.


My problem with that is that on a Mini, there is no button (on a DIP package, no one can hear me scream...)

Looking at the N/N+ schematics, it looks like that would be wired to PA29.
From the mini schematics, this looks like the DTR line is connected there, so maybe I can do something with that. I do know that the dev board I have doesn't have DTR wired from the serial port (as it's only a 3-wire serial connect).

If anyone has already done this, it would be useful to know. I'll see if I can work something out, and post my results here to share.

Steve


#33992 Mini Upgrade Woes

Posted by SteveS on 21 August 2012 - 09:16 AM in Netduino Mini

The SK Pang one is the one I'm using. I like it, because you can choose USB vs EXT power, a simple female-female null modem cable works for the serial port, and there's a handy connector for TX0/RX0 as well as the pinouts. The only thing about it I'd change would be a ZIF socket for the mini itself. And to get back to my original issue, I am going to try and reflash a mini to 4.1 and see if that works. If it doesn't, I obviously have a problem with my mini setup, although a 2,3,5 connection on the serial port is difficult to get wrong if SAM-BA works (which it does). If that does fail, I have an XP machine which I can install 4.2 onto, and see if it's a Win7x86 issue. I deliberably chose to do this on a 32 bit machine in case there were 64-bit issues. So much for that cunning plan... Steve


#33951 Mini Upgrade Woes

Posted by SteveS on 20 August 2012 - 04:30 PM in Netduino Mini

Hi Steve,


Just to confirm...did you flash both TinyBooter and TinyCLR from the "RS232" firmware zip file?

Chris



Of course. I've been married twice, so I'm used to following instructions now :)


#33936 Mini Upgrade Woes

Posted by SteveS on 20 August 2012 - 01:08 PM in Netduino Mini

OK. I have five or six Mini devices I want to upgrade to 4.2.0.0 I have the correct SDK, MicroFramework etc installed. I have downloaded the firmware for all the models (except the Go) and extracted then to separate folders. I have a mini232 and a miniTTL folder. I have successfully updated the firmware on my netduino boards and plus boards. I place the mini into a dev board (from SKPang) since that gives me easy connection to serial port and power. My machine is Win7 32 bit. I clear the flash by connecting the gold pad to 5v. Power cycle board. Run samba 2.12, tell it there is a 7x512 on COM1. Exec the two scripts (boot from flash, enable flash access. Select 232 version of tiny booter bin file, and send file to device. Select "No" whan asked about locking device. Verify image against device. Exit SAM-BA. Power cycle board. Run MFDeploy from 4.2 MF tools Ping COM1 which shows as 4.2.0.0 tinybooter select ER_CONFIG and deploy it. Power cycle device Ping COM1 which shows as 4.2.0.0 tinybooter select ER_FLASH and deploy it. After flashing, MF display displays C (which is first part of Checking signature). Board then fails to respond. Power-cycling the board and pinging it results in Pinging... Error: No response from device and device is 'bricked'. I can recover it by repeating the erase/flash, but I can never get it to ping after updating the firmware. Now, this applies to more than one mini, so not a faulty device.. Any suggestions as to what is going wrong? I don't undertsnad why the booter and the config go across OK, but not the flash, which would to me imply the cable etc is OK. I will try flashing with an older (4.1) FW, and see what I get, but hopefully someone can point me in the right direction. I realise that the ER_FLASH files for TTL and 232 are different. Presumably if I flash the TTL ones, I should be able to see the device from USB ? Any help on this would be gratefully received. It was all going so well.... Steve


#33816 Netduino Mini Dev Board by SK Pang Electronics

Posted by SteveS on 17 August 2012 - 10:23 AM in Netduino Mini

Yes, they are a great idea. Only improvement I'd make would be to change the way the Mini is dropped into the board by using ZIF socket. Other than that, it's just what you need to work with the Mini. I undestand what soshimo is saying, but Chris is right; I use the mini in some stuff where I wouldn't want to use a prefab-ed board like the Plus or regular Netduino for form factor reasons. As I've said in another thread, though, I'd love to see a 40-pin Mini with a SPI1 and ethernet brought out :) Steve


#33756 Mini Overclock

Posted by SteveS on 16 August 2012 - 10:21 AM in Netduino Mini


We've been playing with the idea of a larger Netduino Mini, but once we go beyond DIP24 the form factor starts getting quite a bit bigger...

Chris


I have used larger DIP packages. The 40 pin ATMega 644 (yup, Arduino...) is manageable, you just need bigger breadboards.
Of course, you'd lose STAMP pin compatibility, but the extra pin count would be worth it (access to SPI1 for SD support, maybe even breaking out for Ethernet as well). A Netduino Mini+, just add the extra hardware (SD holder and a magjack...)

I'm about to spend a happy few hours updating my motley assortment of N,N+ and NM to 4.2....

Steve



  1. Netduino Forums
  2. → SteveS's Content
  3. Privacy Policy
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.