The combinations of channels, ADCs, available with the multipin defined functions is what I am trying to sort out. I asked/hinted about in case there are any tips that are obvious I have not figured out or come across the single pin out diagram or similar to have a sense of.Slammer wrote:IDE is working under linux. No problem.keypunch wrote: 1) Can I use this in usual IDE approach using Linux? I do not use Windows, do not have Windows, no thank you if I can avoid. Thoughs on pros and cons for a strickly Linux based development of the Iteadmaple?
USB serial is working as advertised. Sometimes you need to repeat the download process, but it is OK.keypunch wrote: 2) There is this USB for serial and DFU matter some have experienced and some have not.
keypunch: This means one does not the have to press one or both bottons on board?
It is better to use the bootloader V2, requires less memory.keypunch wrote: 3) Are there new/alternative bootloaders that can be used? If so pros and cons. I have read a little about this over past week, but not enough yet to know.
keypunch: Is Bootloader V2 a load after have board to replace bootloader that board came with or some boards come with V2 already?
No. ADC of F103 are 12 bit.keypunch wrote: 4) I assume the ADCs are 10 bit?
keypunch: That is bonus for sure.
Dont expect full adruino shield compatibility. Some of them are working without modifications, some other no for various reasonskeypunch wrote: 5) It appears shields may be a challenge for the pins G, 23-37 of Iteadmaple.
keypunch: I was not expecting full compatibility given the G,23-37 Pin block. I asked in case there were interesting tips, sources, etc I have not stumbled on via research in internet so far. Example was only last week did this board appear in search happened to fall into criteria for not knowing about board or any similar board. This after a few months of searcing, reading, etc. Hence the question.
You can use two I2C interfaces without problem.keypunch wrote: 6) I assume I will have enough pins left over to use some I2C devices if I need to and more than pair in event I have some I2C device address conflicts that cannot be resolved with jumpers (cable or pin headers)?
As I know, the SD read/writing is working.keypunch wrote: 7) What experiences have you had as a datalogger using an SD card? No coding examples are needed unless you feel there is a need to explain. Just the pros, cons, unexpected, or same as any other Arduino experiences is what I am seeking.
No problem in both systems with USB/Bootloader operation.keypunch wrote: 8) Does the UFC and USB serial matter also exist when using Linux? My sense is yes, based on how I understand the reason this is by choice of design of the bootloader. I am assuming even if there is no Windows driver factor when using Linux in the design of the bootloader that this will remain so in Linux as this is how the bootloader was designed. Therefore I am assuming that sets the behaviour no matter what OS one would use?
Note that while the STM32F103RE supports 16 ADC channels, these channels are not always available as various peripherals are using the same pins (for example UART2). You have to consider which peripherals are needed for your application and then to examine the pin allocation and the ADC pins availability.
In just a few words how would you compare this Iteadmaple/stm32 board to the Arduino Due Board and if same or different ported libraries are needed to ported libraries to Iteadmaple/stm32? No Need to comment about memory, 12 vs 16 ADC and clock speed differences and hope I have not missed noting other obvious differences.
I have found searching this site are some libraries ported that are on my main list. I will read a bit more on the library matter and if I have questions there seems to be a topic such questions can be asked.
John L. Males
02 August 2016 23:55