This post replaced by Netduino v4.2 RC3 firmware
Netduino Firmware v4.2.0 RC1
Started by
Chris Walker
, Aug 07 2011 06:18 AM
9 replies to this topic
#1
Chris Walker
-
- Moderators
-
- 7767 posts
Secret Labs Staff
- LocationNew York, NY
Posted 07 August 2011 - 06:18 AM
#2
Valkyrie-MT
-
- Members
-
- 315 posts
Advanced Member
- LocationIndiana, USA
Posted 07 August 2011 - 06:36 AM
Woo hoo! I got the first download of RC1 ! But what did I just download? Is this for the regular, Mini, or Plus?
I'm flashing it now onto my plus...
-Valkyrie-MT
#3
ColinR
-
- Members
-
- 142 posts
Advanced Member
- LocationCape Town, South Africa
Posted 07 August 2011 - 06:52 AM
Woo hoo! I got the first download of RC1 !
I'm only second
#4
Valkyrie-MT
-
- Members
-
- 315 posts
Advanced Member
- LocationIndiana, USA
Posted 07 August 2011 - 06:54 AM
Doh! That is definitely not for the NetduinoPlus. Ethernet link lights are off and it says Netduino (sans Plus) in MFDeploy... I'll continue impatiently waiting. 
-Valkyrie-MT
-Valkyrie-MT
#5
Chris Walker
-
- Moderators
-
- 7767 posts
Secret Labs Staff
- LocationNew York, NY
Posted 07 August 2011 - 06:57 AM
I appreciate the enthusiasm!
We've built firmware for all three boards, but we are going through a "quick test" procedure to help ensure there were no glitches in the code merge.
We'll post the Netduino Plus and Netduino Mini firmware within the next 24 hours. Netduino Plus will come first...
Chris
We've built firmware for all three boards, but we are going through a "quick test" procedure to help ensure there were no glitches in the code merge.
We'll post the Netduino Plus and Netduino Mini firmware within the next 24 hours. Netduino Plus will come first...
Chris
#6
Valkyrie-MT
-
- Members
-
- 315 posts
Advanced Member
- LocationIndiana, USA
Posted 07 August 2011 - 07:00 AM
We'll post the Netduino Plus and Netduino Mini firmware within the next 24 hours. Netduino Plus will come first...
Excellent!
And for the N+, don't forget to set the NETIF_FLAG_BROADCAST in the Porting Kit to enable UDP Broadcast. (Paraphrased from ZachLibby)
Thanks,
-Valkyrie-MT
#7
Chris Walker
-
- Moderators
-
- 7767 posts
Secret Labs Staff
- LocationNew York, NY
Posted 07 August 2011 - 05:40 PM
Ask and ye shall receiveAnd for the N+, don't forget to set the NETIF_FLAG_BROADCAST in the Porting Kit to enable UDP Broadcast. (Paraphrased from ZachLibby)
Netduino Plus Firmware v4.2.0 RC1
Includes "extra RAM" and broadcast support, along with lots of bugfixes.
Chris
#8
ajcg1973
-
- Members
-
- 71 posts
Advanced Member
Posted 08 August 2011 - 08:16 PM
I'm getting a blue screen of death with the 64bit USB drivers for the Netduino 4.2 RC1. I'm running Windows 7 64bit. I have kept the 4.2 SDK files installed but I backed down to the 4.1.0.6 firmware and it seems to work fine now.
Have you guys seen any 64bit USB driver issues on your side? Is there any information that I could provide to help diagnose? Thanks.
*Edited to include contents of Dump FIle*
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03066000 PsLoadedModuleList = 0xfffff800`032ab650
Debug session time: Mon Aug 8 13:13:26.283 2011 (UTC - 6:00)
System Uptime: 0 days 7:52:58.814
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003315100
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
+3332313336383065
00000000`00000000 ?? ???
PROCESS_NAME: System
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff800044f6bf0 -- (.trap 0xfffff800044f6bf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000187000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff800044f6d80 rbp=fffffa80049d01d8
r8=fffffa800391c0c8 r9=0000000000000000 r10=fffffffffffffffe
r11=fffff80003258e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
00000000`00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030e52a9 to fffff800030e5d00
FAILED_INSTRUCTION_ADDRESS:
+3332313336383065
00000000`00000000 ?? ???
STACK_TEXT:
fffff800`044f6aa8 fffff800`030e52a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff800`044f6ab0 fffff800`030e3f20 : fffffa80`049d0030 00000000`00000004 fffffa80`04eba1b0 fffff800`03258e80 : nt!KiBugCheckDispatch+0x69
fffff800`044f6bf0 00000000`00000000 : fffffa80`041fa430 fffffa80`049d01d8 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`030e3f20 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
Followup: MachineOwner
---------
Have you guys seen any 64bit USB driver issues on your side? Is there any information that I could provide to help diagnose? Thanks.
*Edited to include contents of Dump FIle*
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03066000 PsLoadedModuleList = 0xfffff800`032ab650
Debug session time: Mon Aug 8 13:13:26.283 2011 (UTC - 6:00)
System Uptime: 0 days 7:52:58.814
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003315100
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
+3332313336383065
00000000`00000000 ?? ???
PROCESS_NAME: System
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff800044f6bf0 -- (.trap 0xfffff800044f6bf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000187000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff800044f6d80 rbp=fffffa80049d01d8
r8=fffffa800391c0c8 r9=0000000000000000 r10=fffffffffffffffe
r11=fffff80003258e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
00000000`00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030e52a9 to fffff800030e5d00
FAILED_INSTRUCTION_ADDRESS:
+3332313336383065
00000000`00000000 ?? ???
STACK_TEXT:
fffff800`044f6aa8 fffff800`030e52a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff800`044f6ab0 fffff800`030e3f20 : fffffa80`049d0030 00000000`00000004 fffffa80`04eba1b0 fffff800`03258e80 : nt!KiBugCheckDispatch+0x69
fffff800`044f6bf0 00000000`00000000 : fffffa80`041fa430 fffffa80`049d01d8 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`030e3f20 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
Followup: MachineOwner
---------
#9
Chris Walker
-
- Moderators
-
- 7767 posts
Secret Labs Staff
- LocationNew York, NY
Posted 08 August 2011 - 09:22 PM
Hi ajcg1973,
Can you add your data to the BSOD driver codeplex issue over at netmf.codeplex.com?
I know that they're looking at this today...your additional input would be very valuable.
We can't reproduce the issue here at Secret Labs on any OS or any computer, unfortunately.
Chris
#10
ajcg1973
-
- Members
-
- 71 posts
Advanced Member
Posted 09 August 2011 - 02:01 AM
Hi ajcg1973,
Can you add your data to the BSOD driver codeplex issue over at netmf.codeplex.com?
I know that they're looking at this today...your additional input would be very valuable.
We can't reproduce the issue here at Secret Labs on any OS or any computer, unfortunately.
Chris
Done. Let me know if you need any more information about this. I'm going to see if I can get it working though serial deployment.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
