Shield Base Firmware (beta 5)
#1
Posted 13 January 2013 - 10:32 AM
- Gutworks likes this
#2
Posted 13 January 2013 - 10:34 AM
Attached Files
#3
Posted 13 January 2013 - 01:09 PM
This update requires a Netduino Go running v4.2.2.0+ firmware.
The link text states version 4.2.2.0 but following the link takes you to the 4.2.0.2 topic.
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
#4
Posted 13 January 2013 - 02:06 PM
P.S. To update your current project using Shield Base: 1. Remove the NetduinoGo.ShieldBase.dll assembly reference from your current project. 2. Add the attached NetduinoGo.ShieldBase.dll assembly as a reference to your project. This update should be fully backwards compatible with your existing code. Chris P.S. NetduinoGo.ShieldBase.dll will also included in the upcoming Netduino 4.2.2 SDK.
Thanks! Work great for 74HC595 for SPI. No Error
#5
Posted 13 January 2013 - 02:37 PM
Thank again.
#6
Posted 13 January 2013 - 02:42 PM
The link text states version 4.2.2.0 but following the link takes you to the 4.2.0.2 topic.Good catch Fixed. Thanks for letting me know. Chris
#7
Posted 14 January 2013 - 01:23 PM
I was wanting to see if I could flash my nwazet DAQ with the changes made. I'm a little confused on the code in the FlashFile section. The size numbers don't seem to make any sense to me. ER_BOOT on disk is 308 bytes, but it says 52 in new FlashFile. ER_CONFIG 2,572 != 2,316 ER_FLASH 266,676 != 266,420 ER_PROXYAPP 23,016 != 22,760. What on earth would I put for NwazetDAQLVModule.bin at 55,808?
#8
Posted 14 January 2013 - 01:27 PM
#9
Posted 14 January 2013 - 05:36 PM
As an update, I padded it out and ran the reflasher, it said it completed. I'm awaiting an answer from Fabien if there's a way of checking to see if the DAQ is truly flashed or not.
#10
Posted 14 January 2013 - 05:41 PM
Hi everyone,
If interested I have updated the Shield Base pinout to reflect the changes found in this Beta 5 update. You can find the post here: http://forums.netdui...ld-base-pinout/
Cheers,
Steve
- NXTwoThou likes this
Twiiter: https://twitter.com/Gutworks
#11
Posted 14 January 2013 - 06:24 PM
As an update, I padded it out and ran the reflasher, it said it completed. I'm awaiting an answer from Fabien if there's a way of checking to see if the DAQ is truly flashed or not.As long as the file and size settings are correct, you should be good to go. The reflash sample app verifies that the data was written automatically. Chris
#12
Posted 14 January 2013 - 09:35 PM
Happy dance! Reflasher worked with the Nwazet DAQ!
#13
Posted 17 January 2013 - 03:49 AM
FLASHING WAS SUCCESSFUL. !!!
#14
Posted 20 January 2013 - 03:33 PM
Chris,
After I download the zipped file it is downloaded as one file, STM32ReflashApp.sln and one directory STM32ReflashApp. When I click on the sln, I get an this in the output window.
"C:UsersDeniseAppDataLocalTempTemp2_ShieldBase_ManualUpdate_beta5.zipSTM32ReflashAppSTM32ReflashApp.csproj : error : Unable to read the project file 'STM32ReflashApp.csproj'.
#15
Posted 20 January 2013 - 03:48 PM
"C:UsersDeniseAppDataLocalTempTemp2_ShieldBase_ManualUpdate_beta5.zipSTM32ReflashAppSTM32ReflashApp.csproj : error : Unable to read the project file 'STM32ReflashApp.csproj'.
Looking at the path I'd guess that you are trying to run the project from the ZIP file. If I'm right then have you tried to extract the zip into a directory and then open the solution in the extracted directory.
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
#16
Posted 20 January 2013 - 04:25 PM
Looking at the path I'd guess that you are trying to run the project from the ZIP file. If I'm right then have you tried to extract the zip into a directory and then open the solution in the extracted directory.
Regards,
Mark
Thank you so much Mark. That worked. I am back to hacking happily.
#17
Posted 20 January 2013 - 05:10 PM
When deploying this flash application I do not get to this step:
3. When prompted, press the Netduino Go's onboard button to start the flashing process.
After starting to debug, F5, I get this, "The debugging target is not in an initialized state; rebooting..."
About five minutes later I get the following in the output window:
#18
Posted 20 January 2013 - 05:54 PM
Denisetoo,
When you first start the debugger by pressing F5, it is normal to see the message "The debugging target is not in an initialized state; rebooting..." Assuming you have your Shield Base plugged into GoPort 5, you should see in a couples seconds later this message in your Output window just after some other debugging statements:
Module: Shield BaseFirmware: v0.4.0.0 beta 5GoPort: 5Press BTN to start.
At this point you press the button on the Netduino Go the app will flash your Shield Base. Then just continue following the steps listed at the beginning of the post.
Regards,
Steve
Twiiter: https://twitter.com/Gutworks
#19
Posted 20 January 2013 - 06:10 PM
Incrementally deploying assemblies to device Deploying assemblies for a total size of 304080 bytes Assemblies successfully deployed to device. The debugging target and the debugger engine failed to initialize because of unspecified device errors. The debugger engine thread has terminated unexpectedly with error 'Could not reconnect to the debugging target after rebooting it.'.Please try again. If the app hasn't restarted after about 60 seconds, quickly unplug and re-attach the Netduino Go via USB. That should help Visual Studio re-connect. Chris
#20
Posted 20 January 2013 - 06:17 PM
Thanks Chris. It worked!
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users