> > First circuit board I made had ordinary Ethernet. For Ethercat two ports > > are needed but hardware should be same, there are few chips available to > > chose from. This guy used a board from Beckhoff and did not make the > > circuit boards himself. > > > > I do not think so. Look here and tell me what you think. > > Below are complete design files for the board > You can see in his very long video that he is actually running the PCB > routing software and he points out the purpose of individual PCB traces. > For example > he said "this caries I2C" and talks about why he used specific GPIO pin on > the STM32F. If he had bought the board he would not have the design files > and the > deep knowledge to explain them. He even explains how you can program the > firmware without need of a programmer because he included a boot loader.
He use the same device as I did on last card, this should come as no surprise since it is a good chip for a low price. He also seems to be using SPI for communication with Ethercat chip. Boot loader I care less about there is a JTAG/SWD port which work great, I work as a software developer and the boot loader tend to intefer with the debugger so usually I hate it as much as the watchdog. 20 of these boards I could afford but for the $8,000 drivers it would not be enough to sell the house. > This seems to be a very nice design although he points to possible > improvements. > https://github.com/DieBieEngineering/DieBieSlave > > The firmware is here. It seems to be under active development as the last > change was two months ago. > https://github.com/DieBieEngineering/DieBieSlave-Firmware That must be a really good starting point. The STM32F header files annoy me. Usually the same peripheral is used for all STM32F micro controllers but header file is specific for each device and this make it harder to reuse code, with header file specific for peripheral the same code be reused on different chip. The software libraries in sort of is more general but dynamic registering of interrupt handlers make it harder to figure out program execution path, statically adding functions to interrupt handler make it very simple to figure out execution path. Without possiblity to follow execution path it is hard to figure out execution time. The STM32F have allow nested interrupts with priorities which make possible rate monotonic scheduling by hardware and the PWM registers have a shadow so that values are updated at dead line. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
