1. Boss Ac Script And Boss Ac For Machine

First off, I'm a moron. I designed a custom board, derived from. However, instead of the ATSAMD21E17 that the Tau uses, I used an ATSAMD21E16. (The difference is 64 KB of program space, instead of 128.) I've tried recompiling the bootloader with all the references to the E17 changed to E16. I'm able to compile that successfully, and the Atmel-ICE reports that it programmed successfully, but the board doesn't enumerate as a USB device at all, not even a malformed one. Now, I am able to get USB enumeration with Atmel's precompiled SAM-BA bootloaders, as described in The board shows up in the Device Manager and everything. However, I haven't been able to use this bootloader to actually accomplish anything.

I'm on a bit of a deadline here, since I'm using a borrowed Atmel-ICE, and I need to have it back by next Monday. Since the device isn't even showing up, I'm guessing that I've missed some configuration on the chip, but I can't figure out what that would be. Does anyone who actually knows what they're doing have any ideas? Does anyone who actually knows what they're doing have any ideas? Aww darn, I was all set to offer you some advice and then I see that!;) Rabid Prototypes here!

Boss Ac Script And Boss Ac For Machine

WARNING: I wasn't kidding about the whole I don't know what I'm doing thing! I've only needed to create a new bootloader once for the Tau and my other boards which use the SAMD21E17A, and it was a huge pain in the ass!

But I did take some notes as I was figuring it out. They may be of help to you in finding something you missed. I'll post them below. Regarding the board not showing up, which VID did you use? I'm not super familiar with how the USB drivers work, but it might be that in order to be discoverable the VID has to be that of Arduino.cc with your own unique PID.

The Atmel driver probably was compiled with their VID and I'm guessing a driver was installed to talk to them that recognizes that VID. If you're wondering where the VID and PID need to be entered, you have to compile them into the bootloader.

And you need to create a board definition with JSON file which has the VID and PID in there and the chipset and such. It's a very convoluted process. Also before you delve into my notes, Mattairtech has a bunch of pre-compiled bootloaders for various chips.

I had tried these myself when attempting to get the Tau working, but I wasn't having any luck. I think possibly because at the time I didn't know about the VID and PID being compiled into the bootloader, and I'm guessing these have one specific to Mattairtech. But you may find it useful to look at how he configured his boards.

Also, you will need the version of BOSSA he has compiled which has support for all the SAM chipsets, or else it will not recognize the chipset when the Arduino IDE passes it to it when you go to compile and upload your sketch. Btw I was having the same issue as you were when I was trying to get my boards working. The SAM-BA stuff worked, but I wasn't able to upload from the Arduino IDE with it even though they seemed to claim it was compatible. I'm doing some experimentation with the mattairtech code right now, essentially trying to address my board as one of their E16 boards. For some reason, they don't have a compiled bootloader for E16 (though they do for most other variants), but SAM-BA is compatible with their board definitions. Right now my main problem is that they configured SERCOM differently than the Tau, so their I2C device is unconnected on my board, and my SPI is on their UART.

Whenever I try to reassign these, I manage to bork the serial port, and I have to reflash SAM-BA. I used the same VID and PID as you - what was already in the makefile. And to clarify, my problem isn't that I'm not showing up in the Arduino IDE.

I'm not showing up at all. When I plug in, Windows doesn't go 'boo-doop', the Windows device manager doesn't show any new hardware, nothing. It's like the board isn't even trying to USB. Since I leaned pretty heavily on the Tau schematics during design, I suspect that my best bet will be to simply tweak the Tau files, if only I could find the places to do so. Well if you use the Tau board definition, you will need to recompile the bootloader. And you will need to change a few references to the processor here and there.

And set up the new JSON repository on your own server so you can download it, but there is a way to fool it into not deleting it on you if you put it locally but I don't remember how you are supposed to name it.test or something on the end maybe? But even if you get all that right, with no crystal on there you're dead in the water. I'm pretty sure the bootloader requires it. But even if I am mistaken, the sketch certainly does. You also need to make sure to set your fuses correctly. If you have the WDT enabled for example the board will just reset over and over.

Here are the fuse settings you need to worry about. For some reason even though some of them are supposed to default to certain values, I have been getting chips that appear to have them set incorrectly. And they're being bought from Digikey and Mouser, so they're legit chips. I can't explain it, and Atmel insists they should always default to certain values.

So check them all when you program the board. Flash firmware, then set the following fuses: NVMCTRLNVMLOCK = 0x00 NVMCTRLBOOTPROT = 0x02 NVMCTRLEEPROMSIZE = 0x00 BOD33USERLEVEL = 0x07 BOD33EN = X BOD33ACTION = 0x01 WDTENABLE = WDTALWAYSON = BOD33HYST = NVMCTRLREGIONLOCKS = 0xFFFF.

C: Tempbossac.exe -port=COM12 -U false -e -w -v -b PWMPWMLEDEXAMPLE1.bin -R No device found on COM12 bossac.exe -port=COM12 -U false -e -w -v -b PWMPWMLEDEXAMPLE1.bin -R No device found on COM12 bossac.exe -port=COM12 -U false -e -w -v -b PWMPWMLEDEXAMPLE1.bin -R Erase flash Write 12772 bytes to flash 100% (50/50 pages) Verify 12772 bytes of flash 100% (50/50 pages) Verify successful Set boot flash true CPU reset. C: Temp So we need to Erase the device to be able to connect to the Bootloader in the Arduino Due. Next step is to integrate this into the Atmel Studio enviroment. I have not tested this yet. More to follow.