thanks P. will keep 120R on. jumpers will be tough - no space - so will have a trace one would have to cut (restoration would be possible by wire-jumping two small vias)
ETH PHY as shield is a good idea. Don't want to burden the landing board too much as it's likely going to be shipped with every MicroDue board and will be really sensitive to cost.
Unrelated question but hopefully some of you guys have perspective on this. We are exploring possibility to lease some in-house SMT assembly equipment for small / proto runs. Any recommendations? Has to have automatic pick and place...
quick question: how bad would it be to deviate from 0.1" pitch on external pins for MicroDue board? Right now those pins take up HALF of the board space by surface!
For example, we could use same spacing as XBee (2mm) and save some overall space and use space in the corners for mounting holes...
valerun:
P - I have read your thread on ETH in its entirety a few days ago. You are doing truly amazing work for the community (ETH, CAN, etc...).
Sadly I can't figure out sourcing for DM9161 chip...
Val- In case that you decide to add the EMAC peripheral to one of your boards, I'd rather recommend to use one Micrel PHY like KSZ8051MNL given Micrel's better hardware integration and available documentation.
Great work, I'm currently working on a project that requires 2 Dues interconnected on a PCB. This would be a huge space saver for us. We'd definitely be interested in a low cost solution. Will keep track of your progress!
valerun:
P - if you come up with schematics to connect to my RMII pinout, I promise I will make the shield
No problem Val. I kept running DM9161 and KSZ8051MNL PHY chips with DUE some months ago without problems but the sketches and libraries still raw. I needed ten pins from the DUE but I believe MMI pins (MDC/MDIO) are not necessary (I need to verify that). Anyway, please, confirm to me the broken out EMAC pins of your DUE-based board as follows:
PIN NAME DUE PIN
-EREFCK: Reference clock pin-----------113 ETX_CLK
-ECRSDV: Carrier Sense/Data Valid------119 ERX_DV
-ERX0: bit Receive Data----------------120 ERXD0
-ERX1: bit Receive Data----------------121 ERXD1
-ERXER: Receive Error------------------122 ERX_ER
-ETXEN: Transmit Enable----------------114 ETX_EN
-ETX0: bit Transmit Data---------------115 ETXD0
-ETX1: bit Transmit Data---------------118 ETXD1
valerun:
P - if you come up with schematics to connect to my RMII pinout, I promise I will make the shield
No problem Val. I kept running DM9161 and KSZ8051MNL PHY chips with DUE some months ago without problems but the sketches and libraries still raw. I needed ten pins from the DUE but I believe MMI pins (MDC/MDIO) are not necessary (I need to verify that). Anyway, please, confirm to me the broken out EMAC pins of your DUE-based board as follows:
PIN NAME DUE PIN
-EREFCK: Reference clock pin-----------113 ETX_CLK
-ECRSDV: Carrier Sense/Data Valid------119 ERX_DV
-ERX0: bit Receive Data----------------120 ERXD0
-ERX1: bit Receive Data----------------121 ERXD1
-ERXER: Receive Error------------------122 ERX_ER
-ETXEN: Transmit Enable----------------114 ETX_EN
-ETX0: bit Transmit Data---------------115 ETXD0
-ETX1: bit Transmit Data---------------118 ETXD1
Thanks,
p
Yes, I have these exact pins broken out. I looked at the BOM for Micrel-based shield and I think we could offer a ETH MicroShield at $15-20 pricing point
valerun:
Yes, I have these exact pins broken out. I looked at the BOM for Micrel-based shield and I think we could offer a ETH MicroShield at $15-20 pricing point
Man, that would be a good deal considering that some Micrel distributors sell the KSZ8051MNL small eval board for more than US$100.
Hello Val!
I hope everything is going well with your tests of the small-footprint Due. I am eager to work with it and specially interested in the CAN bus functionality. Regards,
I did an Arduino Due compatible design based on ATSAM3X8E but somehow USB interface is not working.
I have my schematics and the detailed issue posted here:
