Created Wed, 03 Oct 2012 20:25:39 +0000 by ricklon
Wed, 03 Oct 2012 20:25:39 +0000
The FubarinoSD is out in the wild. I just wanted to start a thread for people in case they needed to discuss it or needed some support. The main info is: http://fubarino.org It got a plug on Adafruit: http://www.adafruit.com/blog/2012/10/02/fubarino-a-breadboardable-open-source-pic32-board/
Thu, 04 Oct 2012 14:22:59 +0000
Feel free to run RetroBSD on it ;)
Fri, 05 Oct 2012 14:31:24 +0000
I got mine today from Seeedstudio, and it is the 795 version.
It runs OK on Windows 7 and Mac OSX 10.8.2, but it fails on Ubuntu Linux 12.04, all using the 20120811 MPIDE. This has nothing to do with the Fubarino, and is an MPIDE problem.
A driver loads OK in linux (ttyACM0), but on starting MPIDE, I immediately get asked which directory to store my sketches in, and then, after either making a selection, or creating a new folder, the program just disappears. It's the same without the Fubarino attached.
Arduino IDE 1.0.1 works OK on Ubuntu 12.04
When running MPIDE in terminal mode, in Ubuntu, I see some java errors, such as "no rxtxSerial in java.library.path"
I am current with all linux updates for 12.04, though sometimes things like Java have to be downloaded externally, to get the latest version, rather than through software update.
In Windows 7, when starting the 20120811 MPIDE, there is a temporary java file created, jna1515996498641544886.tmp, that triggers an alert from Microsoft Security Essentials (MSE). Hoping for the best, I told MSE to always ignore this file.
Fri, 05 Oct 2012 23:04:51 +0000
Yeah, I had that when I copied my mplab installation over from one computer to another. There's stuff in the lib directory that needs removing / replacing (I think it should create those files at first run).
You might also want to trash your .mpide/preferences.txt file - I had that go screwy at one point too.
Wed, 31 Oct 2012 21:27:38 +0000
Can the PIC32MX440F256H bootloader for the Fubarino be used for the PIC32MX440F512H? Does anything other than boards.txt need to be changed for use in MPIDE? I may have a couple projects where 512kB flash would be nice, but don't need the extra power (read $expense$) of the 795F512H.
Wed, 31 Oct 2012 21:32:36 +0000
That's a good question. I think that if you put the 440F256H bootloader onto a 440F512H part, the bootloader will generate an error if you ever try to use a sketch larger than would normally fit on a 256K part. So while I don't think it will crash or do anything bad, I don't think it will work for what you want to do.
The good news is that it's super simple to create new bootloader images using the new bootloader project. Would you like me to create a new FubarinoSD bootloader for a 440F512K part?
Wed, 31 Oct 2012 22:32:38 +0000
That would be nothing short of fantastic!
As a side note, did you ever get the SD card library running faster than 100kB/s using the enhanced buffering mode? It appears that the 440 has that mode but the 320 does not (sorry Uno32).
Thu, 01 Nov 2012 01:02:54 +0000
OK, I'll try to build one tonight for you and get it posted to Github.
So far, MPIDE can only go up to about 100KB/s to the SD. However, if you run RetroBSD on it, you can get far faster speeds than that. So we know the hardware is able to do it.
There may be an improved SD library for MPIDE in the future - although I'm not sure how specific it is to the MX440. We shall see. At this point, there is huge potential for improvements on the software front, but just a few people working on it and posting their results.
Thu, 01 Nov 2012 03:44:45 +0000
OK, here's a HEX file for a 512K FubarinoSD. I don't actually have one of these, so I can't test it out. But I'm pretty confident it will work.
Thu, 01 Nov 2012 19:32:32 +0000
Thank you. I will report back when I get it up and running (may be a little while with the other things on my plate).
Mon, 03 Dec 2012 16:19:20 +0000
I have built up a board with the 512kB MX440. There are some minor differences between it and the standard board. Programming using PICKit2 works fine with both the bootloader given by EmbeddedMan and the Seeed Studio hex.
The bootloader from EmbeddedMan seems to boot up into programming mode, I am guessing since there is no actual program to run. The production test hex from Seeed studio boots into the test routine and flashes out an error since I do not have it connected to the proper test jig. It can be put into programming mode the normal way.
My issue is that it will not be recognized by the computer regardless of the bootloader used. Windows says that it malfunctioned and puts it in the device manager as an "Unknown Device" When I direct it to use the proper .inf, it says it is the wrong type of device to use that file. Ubuntu also does not recognize it since it does not appear in the "lsusb" list.
Any ideas what would cause this? I am using a usb connector and crystal from a different manufacturer (same footprint), different diodes, NCP1117 regulator, and a different SD adapter. All the voltages are good so I doubt it is the regulator or diodes. The SD adapter should not affect the USB. If the crystal was bad, then I should not get proper flashing rates on the LED, but I do. To me, that leaves only the connector, PCB, PIC, and while unlikely, the bootloaders.
I have another blank board so I may build it up using the 256kB MX440 to see if the 512 version is the problem.
Mon, 03 Dec 2012 17:53:05 +0000
I had an issue once whereby I used some code I compiled for a 128KB pic24 on a 256KB pic24 (same model, different flash size). It didn't work right, and I couldn't work out why.
In the end I found that the config bits were at a different memory location, and it was running on defaults.
As soon as I recompiled specifically for the 256KB version it all worked fine.
If the config bits location differs between the two flash sizes of the MX440, and your bootloader isn't specifically compiled for the 512K version, it may well be that you are actually running on the internal oscillator at the same frequency as you would be on the crystal (so you get the right flashing speeds) but not the right USB frequency, as the PLL settings will be wrong (if they will even work right off the internal oscillator).
Mon, 03 Dec 2012 20:19:12 +0000
Thanks for the suggestion. It looks like the config words are at the same memory location on both devices according to DS61143H.
I will do some more continuity checks and hopefully tomorrow I can inspect the board on the microscope for any possible soldering anomalies.
Wed, 05 Dec 2012 00:40:43 +0000
The microscope revealed a miniscule thread of solder bridging the D+ and D- pins. Looks like I need to get some new flux since the solder is not balling up as well as it should.
Mon, 17 Dec 2012 01:30:57 +0000
I got some new flux and fixed the microscopic solder bridge. Now everything is working great! For more info and continuing progress, check out:
Sat, 26 Jan 2013 20:08:00 +0000
Any news as to when the Fubarino Mini will be released? I would like to port the MultiWii software to PIC32 and use the Mini for my next quadcopter.
Sat, 26 Jan 2013 23:16:56 +0000
Sorry about that. I kept telling people it would be ready by the end of 2012, and that didn't happen. The design is actually completely done, and Seeed is ready to build it. However, I need to provide them with a testing jig for final functional test, and I just haven't had the time yet.
If you just need one or two Minis, I have a small number of hand-built prototypes. Send me an e-mail and we can work something out.
Tue, 16 Jul 2013 21:37:15 +0000
I would like to use MultiWII on ChipKit Do you have some news regarding the re-write of the arduino lib ?
Tue, 16 Jul 2013 21:49:11 +0000
What does that have to do with the release of teh FubarinoSD?
Try starting a new topic, and asking a proper question.
Tue, 16 Jul 2013 22:04:20 +0000
the same question was already asked in this topic FubarinoSD But I will open a new topic
Tue, 16 Jul 2013 23:05:57 +0000
Oh, sorry I didn't see that one then. It's not your fault then - I'll blame the other person ;)