- Welcome to Olimex Support Forum.
Olimex Support Forum
Recent posts
#51
UEXT / Re: MOD-IO2 12V input range
Last post by LubOlimex - November 08, 2024, 09:02:57 AMIt should be OK. Notice this two things tho:
- Input voltage should not go above 15V. Above 15V VR1 LD1117AG will burn.
- At CON4 connector pin #1 there won't be 12V output but what is the car output (14.4V or whatever).
How much current can you draw from 3.3V line depends on how much you draw in total, but check the datasheet of LD1117AG - this regulator handles the input to 3.3V conversion. The regulator can ouput up to 3.3W (1A at 3.3V) but some of this is used for the circuit. Check how much the board consumes without external modules in operation in your hardware setup, then substract that from 3.3W (or from 1A), leave some wattage spare in case of spikes.
- Input voltage should not go above 15V. Above 15V VR1 LD1117AG will burn.
- At CON4 connector pin #1 there won't be 12V output but what is the car output (14.4V or whatever).
How much current can you draw from 3.3V line depends on how much you draw in total, but check the datasheet of LD1117AG - this regulator handles the input to 3.3V conversion. The regulator can ouput up to 3.3W (1A at 3.3V) but some of this is used for the circuit. Check how much the board consumes without external modules in operation in your hardware setup, then substract that from 3.3W (or from 1A), leave some wattage spare in case of spikes.
#52
A64 / Re: Ethernet Interface Not Sho...
Last post by Bhupendra - November 08, 2024, 04:07:16 AMThankyou guys. I am using Olimex A64-OLinuXino and my ethernet was not working after first reboot. But setting "sudo olinuxino-display" to disabled did the trick and i can see eth0 after reboot now. Just made account to thankyou all.
#53
FPGA / Re: unable to configure gatema...
Last post by sukruth - November 07, 2024, 06:47:32 AMthe device was shown as DirtyJTAG(composite parent) under libusb-win32 devices in the device manager after using zadig.
I have also reuploaded dirtyJtag.uf2 binary file but the same error persists.
faced same problem when using linux :-
/Downloads/cc-toolchain-linux/workspace/blink$ make jtag
../../bin/openFPGALoader/openFPGALoader -b gatemate_evb_jtag blink_00.cfg
empty
unable to open ftdi device: -3 (device not found)
JTAG init failed with: unable to open ftdi device
make: *** [../config.mk:40: jtag] Error 1
I have also reuploaded dirtyJtag.uf2 binary file but the same error persists.
faced same problem when using linux :-
/Downloads/cc-toolchain-linux/workspace/blink$ make jtag
../../bin/openFPGALoader/openFPGALoader -b gatemate_evb_jtag blink_00.cfg
empty
unable to open ftdi device: -3 (device not found)
JTAG init failed with: unable to open ftdi device
make: *** [../config.mk:40: jtag] Error 1
#54
UEXT / MOD-IO2 12V input range
Last post by McClint - November 06, 2024, 02:02:50 PMWhats the range of the power input for MOD-IO2. Can it be powered directly by a car battery (up to 14.4V)
Also the how much current can you draw from the 3.3V output at CON1?
Also the how much current can you draw from the 3.3V output at CON1?
#55
UEXT / Re: MOD-RFID1356MIFARE with Li...
Last post by LubOlimex - November 06, 2024, 11:57:15 AMSure, but I feel like just that MOD-RFID1356MIFARE serves another purpose than what you want. It would be cheaper and more efficient to get a PN532 module that exposes I2C, SPI, UART and has no additional main chip with firmware to get in your way. This way you can access it via any method you want, even via simple USB-serial/UART cable.
#56
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.
#57
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.
#58
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.
#59
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.
#60
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"
```