private I2CDevice rfid = new I2CDevice(new I2CDevice.Configuration(0x42, 400)); private byte[] ExecuteReadCommand(ERfidCommands cmd, byte[] data) { byte[] b; if (data == null) b = new byte[2]; else { b = new byte[data.Length + 2]; } var rb = new byte[12]; b[0] = (byte) cmd; var csum = (int) cmd; if (data != null) { for (int x = 0; x >= data.Length; x++) { b[x + 1] = data[x]; csum += data[x]; } } b[b.Length - 1] = (byte) csum; I2CDevice.I2CTransaction[] t = new I2CDevice.I2CTransaction[2] { I2CDevice.CreateWriteTransaction(B), I2CDevice.CreateReadTransaction(rb) }; rfid.Execute(t, 100); while (rb[0] == 0x00) { rfid.Execute(t, 100); Thread.Sleep(10); } return rb; }
Netduino Firmware v4.2.0 RC4 (Netduino + Netduino Plus)
#21
Posted 07 February 2012 - 08:23 PM
Terry Massey
#22
Posted 07 February 2012 - 08:32 PM
#23
Posted 08 February 2012 - 09:19 AM
#24
Posted 08 February 2012 - 03:27 PM
Link failure: some assembly references cannot be resolved!! Assembly: RGBLEDTest (1.0.0.0) needs assembly 'SecretLabs.NETMF.Hardware' (4.1.0.0) Assembly: RGBLEDTest (1.0.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.1.2821.0) Assembly: SecretLabs.NETMF.Hardware.NetduinoPlus (4.1.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.1.2821.0) Assembly: SecretLabs.NETMF.Hardware.NetduinoPlus (4.1.0.0) needs assembly 'mscorlib' (4.1.2821.0) Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) needs assembly 'mscorlib' (4.1.2821.0) Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.1.2821.0) Error: a3000000 Waiting for debug commands...
Why is it having this problem resolving references to the new versions?
#25
Posted 08 February 2012 - 03:29 PM
Did you also change the target framework in your project settings?Why is it having this problem resolving references to the new versions?
Open your solution in Visual Studio and double click the "Properties"-page underneath your project in the Solution Explorer window. Go to the "Application"-tab. You can both see and change the target framework here.
If your solution contains more then one project, you need to do this for every project in your solution!
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#26
Posted 08 February 2012 - 03:50 PM
Did you also change the target framework in your project settings?
Open your solution in Visual Studio and double click the "Properties"-page underneath your project in the Solution Explorer window. Go to the "Application"-tab. You can both see and change the target framework here.
If your solution contains more then one project, you need to do this for every project in your solution!
Yep all 3 projects were changed to 4.2. I also used a simpler project that just lights an LED, changed to 4.2 and get the same errors.
#27
Posted 08 February 2012 - 03:57 PM
That is strange! If your Netduino is in 4.2 and your project files are, how does he come up withYep all 3 projects were changed to 4.2. I also used a simpler project that just lights an LED, changed to 4.2 and get the same errors.
Assembly: RGBLEDTest (1.0.0.0) needs assembly 'SecretLabs.NETMF.Hardware' (4.1.0.0)
Assembly: RGBLEDTest (1.0.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.1.2821.0)
Could you share a zip file of the project please? I think something must still be referring to an old version.
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#28
Posted 08 February 2012 - 03:58 PM
#29
Posted 08 February 2012 - 04:06 PM
Did you also change the target framework in your project settings?
Open your solution in Visual Studio and double click the "Properties"-page underneath your project in the Solution Explorer window. Go to the "Application"-tab. You can both see and change the target framework here.
If your solution contains more then one project, you need to do this for every project in your solution!
I ended up having to compile a new version of the Netduino SDK for the 4.2 Framework. Is there a version out there that I missed? Once I recompiled those two assemblies for the 4.2 framework and referenced them, it worked.
#30
Posted 08 February 2012 - 04:07 PM
Hi Dave,
Be sure that you're using the Netduino 4.2 assemblies from:
C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2
Chris
As you can see above, I compiled by own, but where to I download v4.2 Netduino SDK? I looked all over for the link. Did I miss it?
#31
Posted 08 February 2012 - 04:12 PM
No worries. The link to the SDKs is in the first post in this thread...but it's easy to miss the fact that there are two.As you can see above, I compiled by own, but where to I download v4.2 Netduino SDK? I looked all over for the link. Did I miss it?
Here's the link to upgrading instructions:
http://forums.netdui...?showtopic=2768
And here's the direct link to the Netduino 4.2 beta SDK:
http://www.netduino....nosdk_64bit.exe (64-bit)
http://www.netduino....nosdk_32bit.exe (32-bit)
Chris
#32
Posted 08 February 2012 - 04:25 PM
Hi Dave,
No worries. The link to the SDKs is in the first post in this thread...but it's easy to miss the fact that there are two.
Here's the link to upgrading instructions:
http://forums.netdui...?showtopic=2768
And here's the direct link to the Netduino 4.2 beta SDK:
http://www.netduino....nosdk_64bit.exe (64-bit)
http://www.netduino....nosdk_32bit.exe (32-bit)
Chris
Ok, we're back on track with this. Will try to get my SD Delete and CreateFolder issue checked out with 4.2 and will post back in my other thread. Thanks Chris!
#33
Posted 08 February 2012 - 11:17 PM
#34
Posted 09 February 2012 - 02:37 PM
#35
Posted 10 February 2012 - 01:00 AM
#36
Posted 10 February 2012 - 05:20 AM
..locks Visual Studio in the deployment mode. If I then click cancel to try to unlock it or if I unplug the netduino's USB cable it crashes Windows 7 with a bluescreen. I've had this happen 4 times already.
This has happened to a few people, including myself. I've dealt with it, by clicking Cancel in Visual Studio and waiting for the deployment to actually cancel. Once cancelled, pull the USB cable, re-insert and re-deploy. It's a pain - but it works. I don't even think about it anymore.
You say clicking Cancel without pulling the USB cable gives a blue screen?
Have you tried the drivers which if I recall fixed the issue?
#37
Posted 10 February 2012 - 05:31 AM
I am having I2C issues.. I am working on My drivers forthe RFID reader and I am running into issues. I am not sure if it is a codeissue maybe I am doing this all wrong but I have had no problems in the pasttalking to EEProms over i2c but with 4.2 RC3 I had no data going out my I2Cports and on 4.2 RC4 I am getting weird stuff. Here is my code for my commandmaybe I am doing something wrong. And I have attached an image of the Logicanalyzer it doesn't even seem to be sending the right Bits. Any Ideas.
private I2CDevice rfid = new I2CDevice(new I2CDevice.Configuration(0x42, 400)); private byte[] ExecuteReadCommand(ERfidCommands cmd, byte[] data) { byte[] b; if (data == null) b = new byte[2]; else { b = new byte[data.Length + 2]; } var rb = new byte[12]; b[0] = (byte) cmd; var csum = (int) cmd; if (data != null) { for (int x = 0; x >= data.Length; x++) { b[x + 1] = data[x]; csum += data[x]; } } b[b.Length - 1] = (byte) csum; I2CDevice.I2CTransaction[] t = new I2CDevice.I2CTransaction[2] { I2CDevice.CreateWriteTransaction(B), I2CDevice.CreateReadTransaction(rb) }; rfid.Execute(t, 100); while (rb[0] == 0x00) { rfid.Execute(t, 100); Thread.Sleep(10); } return rb; }
Terry Massey
#38
Posted 10 February 2012 - 05:56 AM
This has happened to a few people, including myself. I've dealt with it, by clicking Cancel in Visual Studio and waiting for the deployment to actually cancel. Once cancelled, pull the USB cable, re-insert and re-deploy. It's a pain - but it works. I don't even think about it anymore.
You say clicking Cancel without pulling the USB cable gives a blue screen?
Have you tried the drivers which if I recall fixed the issue?
I believe I updated the drivers, but will try to update them again. Tks.
#39
Posted 10 February 2012 - 07:43 PM
#40
Posted 10 February 2012 - 08:17 PM
You can update the VID/PID in the .INF file...or you can just force Windows to use the drivers by manually selecting them.I need manually substitude real VID/PID to inf file - or i can download ready drivers for Firmware_Netduino_4.2.0.0_RC4 ?
Or if you want to use the production 4.1 drivers (without the 4.2 BSOD bugfix), they're in:
C:\Program Files (x86)\Secret Labs\Netduino SDK\Drivers
Chris
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users