- Welcome to Olimex Support Forum.
Olimex Support Forum
Recent posts
#51
FPGA / Re: unable to configure gatema...
Last post by LubOlimex - November 06, 2024, 11:06:02 AMSeems like the JTAG is not recognized. Is it show in "Windows Device Manager" as shown on page 15? Follow 5.3 blindly word by word.
#52
UEXT / Re: MOD-RFID1356MIFARE with Li...
Last post by w - November 06, 2024, 10:00:52 AMOne remaining idea: provide a specific firmware image that just provides pass-through.
#53
UEXT / Re: MOD-RFID1356MIFARE with Li...
Last post by w - November 06, 2024, 09:59:07 AMThank you for sharing these details, and the tradeoffs involved.
#54
FPGA / unable to configure gatemateA1...
Last post by sukruth - November 06, 2024, 07:46:16 AMI am unable to configure the GatemateA1-EVB fpga via jtag in windows system and getting the following error
C:\FPGA\cc-toolchain-win\cc-toolchain-win\workspace\blink>run.bat jtag
empty
unable to open ftdi device: -3 (device not found)
JTAG init failed with: unable to open ftdi device
after driver installation in zadig as per the toolchain installation user guide.
C:\FPGA\cc-toolchain-win\cc-toolchain-win\workspace\blink>run.bat jtag
empty
unable to open ftdi device: -3 (device not found)
JTAG init failed with: unable to open ftdi device
after driver installation in zadig as per the toolchain installation user guide.
#55
AM3352 / Archlinux ARM image
Last post by ericwoud - November 05, 2024, 04:17:56 PMBecause I need a switchdev device for testing code that is also used by switchdev devices, I bought the Olimex AM3359 board.
I needed it to run the latest linux kernel, so I created an archlinux package for it.
I haven't tidied up the build script, so I only release the image:
https://github.com/ericwoud/buildAMarch
The linux kernel package can be build on a x86-64 host running archlinux (in a chroot).
This image comes with a patched version for testing my patches, so for a clean kernel, you can build a clean version.
Change:
```
_gitroot="https://github.com/ericwoud/linux.git"
_gitbranch="bpir-nftflow-net-next"
```
I needed it to run the latest linux kernel, so I created an archlinux package for it.
I haven't tidied up the build script, so I only release the image:
https://github.com/ericwoud/buildAMarch
The linux kernel package can be build on a x86-64 host running archlinux (in a chroot).
This image comes with a patched version for testing my patches, so for a clean kernel, you can build a clean version.
Change:
```
_gitroot="https://github.com/ericwoud/linux.git"
_gitbranch="bpir-nftflow-net-next"
```
#56
ESP8266 / Re: Neo6502 - WIFI MOD ESP826...
Last post by Ibitato - November 05, 2024, 01:30:14 PMThanks to olimex support, I am in the way of solving this
thread closed.s
thread closed.s
#57
UEXT / Re: MOD-RFID1356MIFARE with Li...
Last post by LubOlimex - November 05, 2024, 10:45:05 AMMOD-RFID1356MIFARE has no passthrough mode implemented. The design of MOD-RFID1356MIFARE has PN532 and main chip AT90USB162 there are UART, I2C, and SPI hardware connections and interface is selected by values of resistors regarding SEL1 and SEL0 (by default these two chips communicate via SPI). All functions of the firmware are described at the wiki:
https://www.olimex.com/wiki/MOD-RFID1356MIFARE
Unfortunately, I don't see this being implemented. The reason is simple we are out of space for any additions of the firmware. We even removed part of the on-board help to save few bytes. It would require re-designing with bigger chip and re-writing the firmware from scratch.
https://www.olimex.com/wiki/MOD-RFID1356MIFARE
Unfortunately, I don't see this being implemented. The reason is simple we are out of space for any additions of the firmware. We even removed part of the on-board help to save few bytes. It would require re-designing with bigger chip and re-writing the firmware from scratch.
#58
UEXT / Re: MOD-RFID1356MIFARE with Li...
Last post by w - November 05, 2024, 09:42:34 AMI have the same need, and am disappointed that there is no information on talking directly to the PN532 IC, e.g. using SPI. I do see a connector on the PCB markings pins like 3V3, GND, MOSI, NSS, IRQ, P12 (?). These can be found in the PN532 datasheet, and look like one could communicate directly to the PN532. But then there is another microcontroller talking to these pins, which is probably still in the way.
Perhaps ideally the Olimex firmware would provide some kind of pass-through mode, or else to be able to write our own firmware and provide an interface e.g. to the PN532's HSU (High Speed UART) directly, or bypass the Olimex firmware entirely - but we may need to stick with the chosen host interface (l0 and l1 determine which host interface is used, but if they are driven by the microcontroller than it would be configurable).
There is also a possibility that the Olimex firmware has an (undocumented) pass-through mode.
Curious to hear anything from Olimex if there would be a possibility of talking to the PN532 directly.
Perhaps ideally the Olimex firmware would provide some kind of pass-through mode, or else to be able to write our own firmware and provide an interface e.g. to the PN532's HSU (High Speed UART) directly, or bypass the Olimex firmware entirely - but we may need to stick with the chosen host interface (l0 and l1 determine which host interface is used, but if they are driven by the microcontroller than it would be configurable).
There is also a possibility that the Olimex firmware has an (undocumented) pass-through mode.
Curious to hear anything from Olimex if there would be a possibility of talking to the PN532 directly.
#59
ESP8266 / Re: Neo6502 - WIFI MOD ESP826...
Last post by LubOlimex - November 04, 2024, 04:49:07 PMWe haven't tested Neo6502 and MOD-WIFI-ESP8266 ourselves. I guess you have followed this guide:
https://neo6502.com/wiki/Getting-Online/
My point is, we have no idea how to get these two pieces working together either. Please contact the maintainer of the project and report your experience, it might be something well known or a widespread problem.
I have no idea how you determined that MOD-WIFI-ESP8266 got bricked but we sell it with AT commands firmware (meaning you can send AT commands over the serial to control it). If you wish to restore it you can use serial cable that fits the UEXT pins, it is explained here: https://www.olimex.com/Products/IoT/_resources/ESP8266EX-how-to-update-firmware.pdf
Personally I use CH340T + female-male pins:
https://www.olimex.com/Products/Breadboarding/BB-CH340T/open-source-hardware
https://www.olimex.com/Products/Breadboarding/JUMPER-WIRES/JW-200x10-FM/
You can't really brick Neo6502. You might overwrite the software of Neo6502 but this is fixable.
To power Neo6502 you need USB-C cable like USB-CABLE-A-RO-C-1M:
https://www.olimex.com/Products/Components/Cables/USB-CABLE-A-TO-C-1M/
To program the RP2040 you will need USB-A to USB-A cable like USB-CABLE-AM-AM:
https://www.olimex.com/Products/Components/Cables/USB-CABLE-AM-AM/
https://neo6502.com/wiki/Getting-Online/
My point is, we have no idea how to get these two pieces working together either. Please contact the maintainer of the project and report your experience, it might be something well known or a widespread problem.
I have no idea how you determined that MOD-WIFI-ESP8266 got bricked but we sell it with AT commands firmware (meaning you can send AT commands over the serial to control it). If you wish to restore it you can use serial cable that fits the UEXT pins, it is explained here: https://www.olimex.com/Products/IoT/_resources/ESP8266EX-how-to-update-firmware.pdf
Personally I use CH340T + female-male pins:
https://www.olimex.com/Products/Breadboarding/BB-CH340T/open-source-hardware
https://www.olimex.com/Products/Breadboarding/JUMPER-WIRES/JW-200x10-FM/
You can't really brick Neo6502. You might overwrite the software of Neo6502 but this is fixable.
To power Neo6502 you need USB-C cable like USB-CABLE-A-RO-C-1M:
https://www.olimex.com/Products/Components/Cables/USB-CABLE-A-TO-C-1M/
To program the RP2040 you will need USB-A to USB-A cable like USB-CABLE-AM-AM:
https://www.olimex.com/Products/Components/Cables/USB-CABLE-AM-AM/
#60
ESP32 / Re: ESP32-EVB Rev.F pins for t...
Last post by LubOlimex - November 04, 2024, 09:19:11 AMThe ESP32 module has two I2Cs. No problem to use them both. Any free and suitable pin can be defined for I2C (meaning unused for other hardware and suitable for the I2C function). This can be done via software means.
Not sure in the specific case of ESP32-EVB since it is a bit busy board. Observe the constraints of each pin, such is I/O capability, bootstrapping function, and check if it is used in board's schematic. See "ESP32 Chip Pin List" document for details.
Read here:
https://docs.espressif.com/projects/esp-idf/en/v5.3.1/esp32/api-reference/peripherals/i2c.html
Not sure in the specific case of ESP32-EVB since it is a bit busy board. Observe the constraints of each pin, such is I/O capability, bootstrapping function, and check if it is used in board's schematic. See "ESP32 Chip Pin List" document for details.
Read here:
https://docs.espressif.com/projects/esp-idf/en/v5.3.1/esp32/api-reference/peripherals/i2c.html