SteveS

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

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