From: Corey T. <cmt...@hr...> - 2013-04-16 05:10:16
|
Hello, I'm having problems getting a terminal on an AirSTORM COM using the Alcatraz board. Hopefully someone here can help me. Originally, the FTDI processor was not showing up on dmesg. After inspecting the board the 4.7K pull-up resistor, R2 on the schematic, was actually soldered along side the 10K resistor R3. Both resistors occupied the R3 pads and as would be expected resulted in a parallel resistance of 3.2k. This resulted in #reset being pulled low and the chip was stuck in reset. I separated the resistors and placed the pull-up in the location that matched the schematic and board layout. After this the chip showed up on dmesg and /dev/ttyUSB0 was present. My first question is was this in fact a manufacturing defect or were the resistors placed like this on purpose and the schematic has just not been updated? After this I could configure minicom and it would connect through the USB connection. I added the jumpers to use 5V and 3.3V power as well as the jumpers to connect TX and RX. However, when I plug in the 5V supply the status in minicom changes to "Offline" and obviously I don't get any output on the comm port. The middle LED of the Overo board is the only one illuminated at this point. Is there something fundamental that I'm missing? Is it likely that there are more problems with the Alcatraz board? I would have expected the board to be tested before it was shipped so I can't help but think that I was premature in moving the resistors. Any help or suggestions would be appreciated. -- Corey |
From: Neil M. <ne...@gu...> - 2013-04-16 17:30:19
|
Hi Corey, Two resistors populating the same pads is definitely not right. You can check the schematic for other obvious problems or contact sales for an RMA. http://pubs.gumstix.com/boards/ALCATRAZ/R3751/B30022.pdf Sorry about the trouble. - Neil On Mon, Apr 15, 2013 at 9:57 PM, Corey Thibeault <cmt...@hr...>wrote: > Hello, > > I'm having problems getting a terminal on an AirSTORM COM using the > Alcatraz board. Hopefully someone here can help me. > > Originally, the FTDI processor was not showing up on dmesg. After > inspecting the board the 4.7K pull-up resistor, R2 on the schematic, was > actually soldered along side the 10K resistor R3. Both resistors > occupied the R3 pads and as would be expected resulted in a parallel > resistance of 3.2k. This resulted in #reset being pulled low and the > chip was stuck in reset. I separated the resistors and placed the > pull-up in the location that matched the schematic and board layout. > After this the chip showed up on dmesg and /dev/ttyUSB0 was present. > > My first question is was this in fact a manufacturing defect or were the > resistors placed like this on purpose and the schematic has just not > been updated? > > After this I could configure minicom and it would connect through the > USB connection. I added the jumpers to use 5V and 3.3V power as well as > the jumpers to connect TX and RX. However, when I plug in the 5V supply > the status in minicom changes to "Offline" and obviously I don't get any > output on the comm port. The middle LED of the Overo board is the only > one illuminated at this point. > > Is there something fundamental that I'm missing? Is it likely that > there are more problems with the Alcatraz board? I would have expected > the board to be tested before it was shipped so I can't help but think > that I was premature in moving the resistors. > > Any help or suggestions would be appreciated. > > -- Corey > > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |