|
Post by drgarymorgan on May 26, 2018 11:58:54 GMT
Hi everyone, I bought an Aurduino a few months ago and it works fine.
I've just bought a further 10 from RS for some university lab work. However, I've tried the first two and am unable to program them.
The jumpers, software, connection to PC, etc. are all the same as the board that works.
Also, I can see (using the DAS device scanner) the board that works.
However, the non-working boards fail to report anything in the DAS device scanner.
Putting the working and non-working boards next to each other I notice that the layout is not the same.
The working board has an id (on the underside at the far end from the power and USB connectors) of 4269.03.06210_B1 whereas the non-working boards have an ID of 4269.03.06210_A.
I don't know what the difference is between a "B1" and and "A" board.
Can anyone help?
Thanks... gary
|
|
|
Post by Admin on May 26, 2018 12:12:44 GMT
Please check the TC275 step marking. It will be either CA or DC. Make sure you choose the correct board type in the Arduino board setup. If this is wrong the Memtool will fail to connect.
|
|
|
Post by drgarymorgan on May 26, 2018 17:18:42 GMT
Hello, many thanks for replying on a Saturday. Everything works now. I think that there were several problems, and your reply fixed one problem before I'd encountered it.
I'm using Mac OSX and VirtualBox for development. 1) Sometimes the Mac fails to recognise the Shieldbuddy boards. This was my original problem. I don't know why this is. Unplugging and replugging the shieldbuddy often fixes this. 2) Virtualbox needs to be told to forward the Shieldbuddy USB device to the VM. But! By default also uses the serial number of the shieldbuddy in the USB filter. This meant I needed to add each shieldbuddy to the filter until I discovered that a blank serial number matches all. 3) I was using the DAS device scanner to make sure that the Shieldbuddy was recognised by Windows. Unfortunately, if I scan the device and then use the memory programmer, programming fails - every time. Unplugging and replugging the shieldbuddy allows the programmer to work, as does programming first and then using the scanner.
Thanks for your help.
Cheers... gary
|
|
|
Post by Admin on May 26, 2018 19:03:58 GMT
We seem to have a number of people trying to use MacOs. This is something we potentially could support.
|
|