Hi guys
I suppose these questions are mainly aimed at the Mbed team , but any info is useful.
I am still an Mbed noob so excuse my ignorance.
There are a few questions that have been niggling at me that I'd love to know the answers too mainly with a view to going to custom hardware from an mbed.
I know there is a post on the subject but there are one or two finer points I am unsure of.
On the MBED reference schematic it shows the DP83848J pins pin22(LED_SPEED/AN1) and 21(LED_LINK/AN0) connected to P1.25 and P1.26 on the LPC1768 , whats the reasoning behind this ? do the Ethernet lib's require this of is it just optional to check the lights and output them on another pin if you want too?
On pins, I have 3 Mbed1768 and 2 Mbed-M0 but I also have 2 LPCxpresso1769 boards which are a pin super-set of the mbed and break out a lot more IO pins.
They are a cheap alternative to a custom board and baring the PHY being different (LAN8720 PHY) are pin for pin compatible, but have no magic chip but an PLC link JTAG programmer instead , which means booting up codescourcery to program em.
Have the Mbed gang thought about an Mbed++ say with more I.O broken out like the xpresso ?
I have read the proto to hardware and the bootloader is one option , as is the LPC-Link off an xpresso to get your code on the chip.
Have Mbed crew thought of offering the Mbedchip portion as a standalone product , like an LPC-Link but with the drag n drop interface like the mbed (without serial pass-tru and mbed filesystem part , basically a drag'ndrop jtag programmer that would be good.
I have got the LAN8720 PHY working with mbed ethernet libs on the xpresso (thanks to chris) so I can use that for semi permanent but sure would love to have a big long mbed with all io available :) or even a drag n drop programmer instead of the LPC link
Hi guys I suppose these questions are mainly aimed at the Mbed team , but any info is useful. I am still an Mbed noob so excuse my ignorance.
There are a few questions that have been niggling at me that I'd love to know the answers too mainly with a view to going to custom hardware from an mbed. I know there is a post on the subject but there are one or two finer points I am unsure of.
On the MBED reference schematic it shows the DP83848J pins pin22(LED_SPEED/AN1) and 21(LED_LINK/AN0) connected to P1.25 and P1.26 on the LPC1768 , whats the reasoning behind this ? do the Ethernet lib's require this of is it just optional to check the lights and output them on another pin if you want too?
On pins, I have 3 Mbed1768 and 2 Mbed-M0 but I also have 2 LPCxpresso1769 boards which are a pin super-set of the mbed and break out a lot more IO pins. They are a cheap alternative to a custom board and baring the PHY being different (LAN8720 PHY) are pin for pin compatible, but have no magic chip but an PLC link JTAG programmer instead , which means booting up codescourcery to program em. Have the Mbed gang thought about an Mbed++ say with more I.O broken out like the xpresso ?
I have read the proto to hardware and the bootloader is one option , as is the LPC-Link off an xpresso to get your code on the chip. Have Mbed crew thought of offering the Mbedchip portion as a standalone product , like an LPC-Link but with the drag n drop interface like the mbed (without serial pass-tru and mbed filesystem part , basically a drag'ndrop jtag programmer that would be good.
I have got the LAN8720 PHY working with mbed ethernet libs on the xpresso (thanks to chris) so I can use that for semi permanent but sure would love to have a big long mbed with all io available :) or even a drag n drop programmer instead of the LPC link