Help required with Update firmware to 4.1.1
#1
Posted 31 January 2011 - 04:48 PM
#2
Posted 31 January 2011 - 06:28 PM
#3
Posted 31 January 2011 - 08:02 PM
Attached Files
#4
Posted 31 January 2011 - 08:33 PM
#5
Posted 01 February 2011 - 12:50 AM
To add to above. I just reflashed 4.1.0.5 onto N+ and that works ok, no hang ups
Hi Alan,
Are you running inside a virtual machine? If not, what version of Windows are you using (and is it 32-bit or 64-bit)?
Chris
#6
Posted 01 February 2011 - 05:16 PM
Hi Alan,
Are you running inside a virtual machine? If not, what version of Windows are you using (and is it 32-bit or 64-bit)?
Chris
Chris,
I am running a 32bit version of XP with service pack 3 on an Esprimo with Intel core2 CPU 6300 @ 1.86 GHz showing 2.99 GB of ram although there is 5GB on board. I usually run Ubuntu but installed the only version of XP I own which is the 32 bit version from a previous machine. Not running on a virtual machine.
Alan
#7
Posted 01 February 2011 - 06:48 PM
#8
Posted 01 February 2011 - 07:34 PM
Attached Files
#9
Posted 01 February 2011 - 08:10 PM
Attached Files
#10
Posted 01 February 2011 - 08:47 PM
#11
Posted 01 February 2011 - 11:41 PM
#12
Posted 02 February 2011 - 08:14 PM
#13
Posted 02 February 2011 - 09:07 PM
Chris,
I have received the builds. All contain config and flash. Which version of TintbootDecompressor do you wish me to try them with from 4.1.0.5 or from 4.1.0.6 ?
Alan
Hi Alan,
If you haven't flashed a TinyBooter before then the one you have right now is fine. Otherwise, use the one from the v4.1.1 alpha 6 build or the v4.1.0.6 RC1 build. ["64KB" bootloader]
Chris
#14
Posted 02 February 2011 - 11:02 PM
Attached Files
#15
Posted 08 February 2011 - 12:33 PM
while (true) { Debug.Print("Loop " + i.ToString() + "\n"); string[] dirs = Directory.GetDirectories(@"\"); foreach (string s in dirs) Debug.Print(s); i++; try { Directory.SetCurrentDirectory("\\SD"); } catch (Exception) { Debug.Print("Exception occurred while calling SetCurrentDirectory"); } Debug.Print("Current directory (after): " + Directory.GetCurrentDirectory()); Thread.Sleep(8000); }See attached file for output. I removed/re-inserted the SD card between iterations of the loop but it seems to make no difference. So can you tell if my SD card reader working or not or is it a software issue?
Attached Files
#16
Posted 08 February 2011 - 04:03 PM
I always get this also.when using MFDEploy used to flash chip it still hangs up after finishing with Application executing message so I have to unplu/plug there but beginning to think that is an MFDeploy bug.
Jim
#17
Posted 08 February 2011 - 05:37 PM
#18
Posted 08 February 2011 - 08:25 PM
On my system I get dirs set to an array of size one containing the string \SDI also get this.
SetCurrentDirectory appears to the set the directory correctly as the call to GetCurrentDirectory returns \SD.
Regards,
Mark
To be or not to be = 0xFF
Blogging about Netduino, .NET, STM8S and STM32 and generally waffling on about life
Follow @nevynuk on Twitter
#19
Posted 08 February 2011 - 10:49 PM
#20
Posted 09 February 2011 - 11:01 AM
alanb,
It's really weird that you're getting "\ROOT" and "\WINFS" at all. Which firmware build are you using? The special "build #3" that I sent you?
Also, is the card formatted as FAT16 or FAT32?
Chris
Yes I am using the special build you sent. I will reflash the old 4.1.0.5 today and try that. The SD card was formatted on my PC as FAT so I take that to be FAT16. I do know that when mounted on a USB carrier my pc reports the SD disk as healthy.
At present I do not know if it is the firmware or my N+ hardware that is at fault (if it is the hardware I will want to return my N+ to the supplier to be swapped under warranty for a fully working board).
I am under the opinion that perhaps secret labs should think about makeing some short test programs available (not necessarily in c#) that will enable users to establish definitively, if at all possible, whether a problem is hardware or software related. I think this could apply to the SD card, the Network interface etc.
For example is my short bit of code that doesnt report \SD a definitive test for the SD reader/firmware? If not what code would be?
Alan
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users