• Content count

  • Joined

  • Last visited

Everything posted by Antichambre

  1. Why does the HC165 even work?

    lol Yeah I've got some default pages opened when my computer is switched on, all my email boxes, messenger and midibox forum! My computer is always switched on when I'm home. And I work 80% of the time at home so. ;)
  2. Why does the HC165 even work?

    ?? QH pin which is connected to the STM on SI, is an output! It sends 5V cmos level to the STM, the inputs pin of the STM are '5V tolerant' then you don't need level shifting down in this way(165 to STM).  
  3. Then you can use a chip which is made for that: Its a 64 sensor input(8*8 matrix). It has a SPI port, easy to interface with any Core. You need only one IC for less than 8€. Best regards  
  4. midiphy SEQ v4+

    Hey, If you need more just tell me ;) Best Bruno
  5. And a single CPU, an STM32F4 to take advantage from the MIOS32, AND good ADC with multiplexed input? An 8 inputs ADC with eight (8:1) multiplexers will give you 64 inputs ;)
  6. dipCoreF4 and dipBoardF4, a compact Core.

    No I can't, it depends on the functions you need on your 'mainboard' and the ones you already mapped. Best Bruno  
  7.                                                                         Hello, This is about a new STM32F4 mbhp, a very compact one. This concept is an answer to these three topics: I tried to draw the most compact core and mbhp board. It's an STM32F405RG instead of the regular 407VG. The 405RG is the smallest package of the M4 Series, this is a LQFP64, a 10x10mm package with only 64 pins. Because these two Processor are from the same family, we don't need deep changes in MIOS32. They have exactly the same functions, memory, speed and peripherals. I put the STM32F4 on a DIP-40 format pcb, in order to get a core that can also replace a PIC in some application, I strongly think of my sammichSid. At the same time it must provide the legacy functions and ports of MIOS32 of course. Some compromise have been made in comparison to a 407VG mbhp. - Only 2 MIDI I/O. - J15, the LCD port is now a serial one only(SSD13xx). - No more general purpose port J10x. This is the list of the 'remaining' ports and changes. - J1A and J1B are the USB and Power ports, J1A is compatible with latigid on's USB wCore module. J1B can be a common header on top or a Micro-Match connector on bottom to stack another board under. - J4 is a dual I2C connector, I put both on the same connector to save space. - J5 is a 2 channels only ADC, they can be used for expression pedal input for example. - J8/9 and J19 stay the Legacy 5V SPI ports, the dipCoreF4 includes the octal buffer(74HCT541); - J11 is now a 6pin and 2 MIDI I/O port. - J16E is the 3.3V SPI port, commonly dedicated to the SD Card it is compatible with latigid on's RES-SD modules. it is extended by the Reset input, the user button and 2 outputs for LEDs. - J18 has changed, it is now able to connect a CAN tranceiver, but stay compatible with the MBNET connection. About the dimension, the ensemble is very compact 65x46mm, but the Core can be used alone and measures 51x17.8mm.                   A 3D view of the ensemble(sorry this is not a render, I shoot the screen):   You will find some more information on the dokuwiki, dipCoreF4 and dipBoardF4 Feel free to ask me question or give me any constructive criticism. I will order some board very soon, if some want to participate in the tests they are welcome, just contact me. I will provide the beta boards for free I just ask you to play the game and seriously help me to improve it ;) Thank you Best regards Bruno PS: sorry for my English as usual ;)    
  8. dipCoreF4 and dipBoardF4, a compact Core.

    No no there's no problem for that, this is just a bit dirty in code for the moment, and I have to complete it, I didn't write any callback installer for the HID for example, this is toDo. I can share, I already shared it with my dipCoreF4 beta testers ;)
  9. dipCoreF4 and dipBoardF4, a compact Core.

    In this extended chart you can see the functions available for each pin, (It's from stm32f4 documentation.)
  10. dipCoreF4 and dipBoardF4, a compact Core.

    In MIOS32 the problem with the 407 is that the pin for the second USB(OTG_HS) are used for SPI2 which is your J8/9 Spi port. Then on the dipCore I moved the SPI function to other pins . AND I implement it in MIOS32 ONLY for the DipCooreF4. In MIOS32 the DipCore has is own pinout and functions.  
  11. dipCoreF4 and dipBoardF4, a compact Core.

    You want two USB with HID support. Which uC you use on your 'mainboard'? I implemented the second OTG HS for the STM32F405RG, coded in MIOS32 with/for the DipCoreF4 pinout. I just put an STMPS2141STR as protection, the same as Disco one.    
  12. dipCoreF4 and dipBoardF4, a compact Core.

    Hello Chris, Which feature do you need? Best Bruno
  13. CORE_STM32F4 Module, LCD, and fire

    to cut yourself cleanly ;) , eagle files    
  14. CORE_STM32F4 Module, LCD, and fire

    Workaround at osh park for castellation. Use micromatch as low profile connector eagle files Best regards Bruno  
  15. MCAN

    I will do ;) More than that I have to complete, error handling and field filtering for enhanced mode. Best Bruno
  16. MCAN

    @ALL .About the MCAN MCAN, MIDIbox Controlled Area Network Low cost MIDI(Native) Network using CAN, this is MCAN…   2 cores interconnected with simple 'One Wire'. But you can add more: 2 wires in fact, we need a short common ground too. Bus length is limited to a total of 45cm. Unknown maximum number of Cores, but 4 is suggested.   3 interconnected Cores with CAN Tranceivers: Cables between the MCAN modules are RJ12, I use molded high speed ADSL cables from supermarket. First RJ12 connector is IO, second is a Loop Thru. If loop is not used each MCAN module has a 120 Ohm terminator switch. First and last nodes must have terminator ON. Bus length is limited to a total of 15m. Unknown maximum number of Cores, just respect maximum bus length. For both connection methods, the Cores are dialoguing in MIDI natively, thru the 16 virtuals MCAN ports. This is something you can expand, you can create your own Sysex based MCAN layer to build one unique app which is in fact a multi-Core App. Or you can easily create your MIDIBox(es) based Network to interconnect yours Seq, Synth and/or Controllers App. with easy to find ADSL cables. Note: In basic mode, all nodes(Cores) can talk, if one is talking the others are listening, that's all. Message priority is based on the types of MIDI events, and there's no filtering or Node ID to set. Best Bruno
  17. MCAN

    It's fine, you obliged me to share it correctly and learn a good way to do it :)
  18. MCAN

    @TK. Ok thank you for the explanation. helpfull. The modified trunk with MCAN features only is ready in I added an example for the MCAN in basic mode here:   I can compile example properly on my side. Best regards Bruno  
  19. MCAN

    I tried but without success, under eclipse I can create a branch but i don't know where I have to..? I just 'succeed' to copy trunk in trunk and and deleted it. :( Do you suggest me to create a copy of the trunk, with another name, in the same root? branching is a new concept for me but I can try again if someone can help me, explain me a few, a kind of quickstart for branch under SVN.
  20. MCAN

    Hi Thorsten, MCAN ports are seen as regular MIDI ports. and accessible via new enumerated ports MCAN0 to MCAN15 with base address 0x60. ... SPIM7 = 0x57, // New MCANx virtual Ports. MCAN0 = 0x60, ... MCAN15 = 0x6f } mios32_midi_port_t; It is fully embedded in MIOS32, this is 4 files to add and some changes in others. the new dirvers: mios32_can.c, mios32_can.h for the CAN features mios32_can_midi.c, mios32_can_midi.h for native MIDI other the CAN This is my entire trunk. But there's more than the MCAN feature added... It's my experiencing thrunk, I test the m16 and the dipCoreF4 with it. With it you can also test the HID support, with a Disco or wCore and OTG FS as HOST, but it remains me to add the callback installer for app layer. On the MCAN side: For testing with hardware you just need 2 or more Cores over the CAN bus, using J18 with 'MBNET' one wire. In software, MCAN driver has to be enabled.  /* the use of CAN Controller must be precised. */ #define MIOS32_USE_CAN /* CAN1 is MCAN must be precised. */ #define MIOS32_USE_CAN_MIDI /* Number MCAN MIDI Ports, default and max is 16 */ #define MIOS32_CAN_MIDI_NUM_PORTS 16 More information here (dokuwiki). It's CAN and MIDI you should like it ;) Best regards Bruno    
  21. CORE_STM32F4 Module, LCD, and fire

    Bien vu l'aveugle ;)
  22. CORE_STM32F4 Module, LCD, and fire

    Usually we mirror the pairs by putting the header on the rear side of the LCD, this is the only way but it's only for 2 row connector on LCD side, for an inline connector on the LCD this is not possible, then pairs have to be swapped on the LCD. Simple! You can turn the IDC on every way, pin 1 or 16 will always be on first or last wire of the ribbon!!! Clear? ;)
  23. CORE_STM32F4 Module, LCD, and fire

    But the diagram is ok, only the red annotation is wrong!  
  24. CORE_STM32F4 Module, LCD, and fire

    No the only way is to put the header on the rear side of the core pcb... Then @Wapata  just swap the pins by pair on the LCD side, like I said before and everything will be right, and you're right there's a mistake on the diagram.
  25. CORE_STM32F4 Module, LCD, and fire I think you're right ! ;) "Order of wires is matching with flat ribbon cable" This seems not true.