I no longer have to worry about plugging in a 3.3v wall wart *anywhere* anymore. Next, on the point of issue with 5V, I haven't run into those issues on the USB, because most experienced ARM programmers know to not plug into the native port with power on the board, so I'm unsure what you are referring to, but I *CAN* tell you about the issues and limitations of having to step down to 3.3v stuff when you have all 5v parts on EVERYTHING ELSE I use, so this is a welcome addition to the ecosystem in my opinion. (Makers program by USB real hackers program by JTAG ) Just to make this even more awesomer, They added a native JTAG. to add the fact that it POWERS the pi from that same connection.well, you get the idea. On that point, looking further at the design, having native Raspberry pi integration is a positive example of that kind of expandability. In my opinion, that is what I think intended expand the platform, Enhance the platform, but don't cripple it. That is hard for me to accept if I'm looking for a board that is nearing "industry standard" quality, especially if I'm in support of Īlso, I love the potential for USB OTG control of another downstream device that just simply shows foresight and adherence to the standard. That was the one of the original scenarios with the Arduino due, (and 32-bit proc) but the point is it was there for a reason.and for me the Duet didn't honor that principle. It is simpler, no argument, to flash through the native port, but to do so, Duet changed the Arduino due model design to enable native programming and control, they blocked the otg power output for the native MCU, which limits any ability to use it for USB OTG.
reduces the risk of sending resetting baud rates, hitting reset buttons, etc. flip, reset, flip, flash using the programming port. On the alligator, they honored this with a DIP switch that makes erasing and flashing pretty easy. "Either of the USB ports can be used for programming the board, though it is recommended to use the Programming port due to the way the erasing of the chip is handled"
but given that themselves, and just about anybody who has had to deal with a crashed or half-flashed ARM can tell you, you really need a separate programming port just sayin. Nobody said you could not program it through the native port, because you can, and I have, and haven't had a problem.
the fact 3D artists designed it closer to the original Arduino Due design bodes well for repurposing this board for future scenarios. I don't want this to turn into a flame war, but as a customer and a backer, I am actually quite glad and very pleased they enabled the Alligator board like they did compared to other ARM based boards out there. Maybe they will fix that in a future revision of the board. it provides higher speed with flow control, which means you can get much better data rates.īut I understand there are issues with the 5V supply on the Alligator native USB port. it means that it doesn't matter what you set the baud rate to, because there is no async comms involved Using the native USB port instead of the USB-over-serial port solves two problems: It's a shame the Alligator team didn't learn from the Duet (which is also based around the Arduino Due but came out a year earlier) and design the board to use the native USB port as standard.
0 kommentar(er)
