Welcome, Guest

Recent Posts

Pages: [1] 2 3 ... 10
1
A20 / Question ....?
« Last post by vincityhn1 on Today at 05:18:16 AM »
Hi,
I have a ram ddr3
Can I add it to my PC that has ram ddr4 installed?
Tks!
2
A20 / Issue with A20-SOM204, no power on Port G
« Last post by Jonathan Fether on Today at 03:14:36 AM »
I have an SOM-204EVB and am in the process of qualifying it with an alternate Bluetooth+WiFi solution (Laird Sterling-LWB based on CYW4343W (Formerly BCM4343W)).

I desoldered the Realtek device and attached jumper wires to the ports, and found poor performance of the UART port (very low signal amplitude). Also, UEXT1's UART port was not working.

After some diagnosis, I found that the root cause was that the A20's pin E18 (VCC-PG) was not receiving power. I was able to find that the regulator was disabled.

Code: [Select]
root@olimex:/sys/power/axp_pmu/regulator/regulator.7# cat name
vcc-pg
root@olimex:/sys/power/axp_pmu/regulator/regulator.7# cat state
disabled

I was able to force the regulator online using I2C commands:

Code: [Select]
i2cset -f -y 1 0x34 0x12 0x1F
This resolved my serial port issue.

I am still trying to understand why this issue occurred. My suspicion is that Linux turns off the regulator to conserve power. I am running "ARMBIAN 5.41 user-built Debian GNU/Linux 9 (stretch) 4.17.17-sunxi".

I also noticed in the regulator section of "sun7i-a20-olimex-som204-evb.dts", that the regulator (ldo4) isn't marked always on like ldo1 and ldo2 are:

Code: [Select]
&reg_ldo1 {
regulator-always-on;
regulator-min-microvolt = <1300000>;
regulator-max-microvolt = <1300000>;
regulator-name = "vdd-rtc";
};

&reg_ldo2 {
regulator-always-on;
regulator-min-microvolt = <3000000>;
regulator-max-microvolt = <3000000>;
regulator-name = "avcc";
};

&reg_ldo4 {
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
regulator-name = "vcc-pg";
};

3
FPGA / Re: Can't Flash ice40HX8k-EVB with Raspberry Pi
« Last post by Forty-Bot on September 20, 2018, 08:41:35 PM »
> I don't think your hardware connections should be different. The 1K and 8K boards have nearly identical programming connectors. Compare the programming connector in these PDFs:

Well it's more that the original instructions were for using IDC connectors and I am making the connection with jumper cables, as seen in the picture. Again, I have listed out the connections I made in the code box in the original post. I have checked them against the schematic for the HX8K and the pi.
4
A20 / Re: A20-OLinuXino-MICRO: SATA interface hardware failure?
« Last post by LubOlimex on September 20, 2018, 03:15:18 PM »
> This includes the same power supply purchased with the MICRO from Olimex last year.

Oh, you got one of our supplies - then it is likely the problem. Our supplies are low amperage. They are sufficient for the A20 boards alone. A setup of A20 board and hard disk might draw more than these adapters are capable to provide. If possible check the maximum current (or wattage) that your hard disk can consume (should be mentioned in its datasheet).

Search for a similar adapter that is can maintain 12V of voltage while capable to provide up to 2A or 3A of current.
5
A20 / Re: A20-OLinuXino-MICRO: SATA interface hardware failure?
« Last post by Nate on September 20, 2018, 02:46:07 PM »
Thanks, Lub.

What I find interesting is that I'm using the exact same hardware complement only through one of the USB ports rather than the SATA port and it is working without errors.  This includes the same power supply purchased with the MICRO from Olimex last year.

This does give me some ideas to work on when I get the time.
6
JTAG / Access external Flash of an TI OMAP5948
« Last post by jaggernaut on September 20, 2018, 02:06:26 PM »
Hello! I'm recently received my Olimex ARM-USB-OCD-H probe. My goal was to use it to download/upload Firmware of a radiosystem. The firmware resides there in an Flash memory chip (Spansion S29GL256N, BGA) which is connected to the main processor, an OMAP5948. There are also two external RAM-Chips (Micron 46V64M8) connected to it. The bootloader inside the OMAP's own flash will copy the content of the external Flash to the external memory on powerup and executes the software from there. The external Flash contents seem to be violated/erased somehow and i'm looking for a way to reprogramm it.

The OMAP5948 contains an ARM9 CPU (ARM926EJ-S) and an JTAG-TAP (besides of an Coprocessor, CP15 and an DSP). I've managed to find the correct JTAG-Signals and connect them to the Olimex. As for the software i'm using OpenOCD. Because there is no native support for OMAP5948 with OpenOCD, i've created the following config:

openocd.cfg:
Code: [Select]
# source interface config
source [find scripts/interface/ftdi/olimex-arm-usb-ocd-h.cfg]

# source target config
source [find scripts/target/omap5948.cfg]

jtag_rclk 4
init
reset

The file ftdi/olimex-arm-usb-ocd-h.cfg is already supplied by OpenOCD for the Olimex.
The target config file target/omap5948.cfg i have created myself with the following inside:

Code: [Select]
# TI OMAP5948 (ARM926E + DSP)
adapter_nsrst_delay 100

# TotalIRLen = 50, IRPrint = 0x001444031F3D81
# JTAG chain contains 3 devices:
#  #0 Id: 0x031F3D81, IRLen: 34, DSP
#  #1 Id: 0x0692602F, IRLen: 04, ARM9TDMI Core
#  #2 Id: 0x00000001, IRLen: 12, Unknown device (ICE)
# CP15.0.0: 0x41069263: ARM, Architecure 5TEJ
# CP15.0.1: 0x1D112152: ICache: 16kB (4*128*32), DCache: 8kB (4*64*32)
# Cache type: Separate, Write-back, Format C (WT supported)
# Adaptive clocking not supported for selected CPU core. Only supported for -S cores.
# Auto JTAG speed: 8000 kHz
# JTAG Id: 0x0692602F  Version: 0x0 Part no: 0x6926 Man. Id: 0017

#jtag scan chain
jtag newtap omap5948 dsp -irlen 34 -expected-id 0x031f3d81
jtag newtap omap5948 arm -irlen 4  -expected-id 0x0692602F
jtag newtap omap5948 ice -irlen 12 -expected-id 0x2008f02f

set _TARGETNAME omap5948.arm
target create $_TARGETNAME arm926ejs -chain-position $_TARGETNAME

This seems to be able to connect to the TAP, but wenn trying to access something with it, i get an error that the CPU is not halted.

First, do this look okay so far? Or am i completely wrong somewhere?
What can i do to halt the CPU?
How can i access the external Flash contents to transfer it to the PC or vice versa?
Is this also possible for the content of the external RAMs?
Can i read internal registers of the CPU and how (SFR..., Special function registers)?

Sorry, but i'm just beginning using JTAG. So if my questions are stupid, errorprone or misleading, please be gracious :-)

Uh, btw.: How can i attached files in this forum?
7
MSP430 / Re: MSP430 5419 HELP!!! Tiny2
« Last post by LubOlimex on September 20, 2018, 11:52:37 AM »
I have few ideas and suggestions in the blind:

1. Did you enable "calibration area" in the programmer software? Try to de-select "calibration area" from the tick box and test again.

2. Are you sure that you are using MSP430F5419 and not MSP430F5419A - you might need to add a custom entry in the drop down menu of the Olimex programmer for the 5419A version.

3. You can also check what happens if you try older firmware - 1.0.4.2 has support for MSP4305419 too - download this https://www.olimex.com/Products/MSP430/JTAG/_resources/OLIMEX-MSP430-DLL-drivers-1.042.zip and place the files in the main folder of the Olimex programmer software. Restart the software and when you attempt to perform read/write you would be asked whether to update the software - agree to do so. If you wish to switch to 2.0.0.7 firmware you can do it same way (using the newer dll file).

4. If possible test with another software tool like IAR for MSP or CCS or other programmer software.

Best regards,
Lub/OLIMEX
8
FPGA / Re: Can't Flash ice40HX8k-EVB with Raspberry Pi
« Last post by LubOlimex on September 20, 2018, 10:23:25 AM »
> These instructions are for the HX1K, so my connections are different.

I don't think your hardware connections should be different. The 1K and 8K boards have nearly identical programming connectors. Compare the programming connector in these PDFs:

https://github.com/OLIMEX/iCE40HX1K-EVB/blob/master/iCE40HX1K-EVB_Rev_B.pdf

https://github.com/OLIMEX/iCE40HX8K-EVB/blob/master/HARDWARE/REV-B/iCE40HX8K-EVB_Rev_B.pdf

Also the original project can be found here: https://github.com/anse1/olimex-ice40-notes
9
A20 / Re: A20-OLinuXino-MICRO: SATA interface hardware failure?
« Last post by LubOlimex on September 20, 2018, 08:30:37 AM »
I've seen these errors when there is not sufficient powering for the hard disk. When dealing with the hard disks it is important to ensure the board is sufficiently powered. Try with a power supply capable of providing more current and maintaining stable voltage. Consider that it might be also bad cables or contact between board and PSU or between board and disk (sata or power cable). If you suspect that the board might suddenly lose power consider adding back-up battery.

> I am concerned that the ATA hardware is failing on my MICRO.  Should I seek a replacement or is there something else can could cause the failure messages?

If it happens again I would also suggest testing with the official Olimex images and check if it might be a software issue. You can find these here: https://www.olimex.com/wiki/A20-OLinuXino-MICRO

Best regards,
Lub/OLIMEX
10
FPGA / Can't Flash ice40HX8k-EVB with Raspberry Pi
« Last post by Forty-Bot on September 20, 2018, 12:43:36 AM »
Previously posted on reddit

I'm trying to program my ice40 HX8K. I am using a pi B+ ver2, which is offered as an alternate programming method on the wiki page for this board. These instructions are for the HX1K, so my connections are different.

Code: [Select]
    GND | GND
    GPIO 25 | iCE40-CRESET
    CE0# | iCE40-SS_B
    MOSI | iCE40-SDO
    MISO | iCE40-SDI
    SCLK | iCE40-SCK

The setup looks like this. I can turn off/on the iCE40-CRESET LED using GPIO25, like in the guide. However, when I try to read the flash contents I get

Code: [Select]
    $ flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=20000 -r dump.bin
    flashrom v0.9.9-r1954 on Linux 4.9.41+ (armv6l)
    flashrom is free software, get the source code at https://flashrom.org
   
    Calibrating delay loop... OK.
    No EEPROM/flash device found.
    Note: flashrom can never write if the flash chip isn't found automatically.

I have checked all my connections, tried switching from CE0# to CE1#, tried switching MISO and MOSI, tried all /dev/spidev?.? devices, tried rewiring to use SPI1 (pins 36-40), tried different baud rates, tried building flashrom from source (instead of using the packaged version), and rebooted. I have also tried powering the board via the raspberry pi, and using a pi rev 3 B. The jumper cables have been checked. I have the spi interface enabled in /boot/config.txt. I first asked on #raspberrypi on freenode, and again on ##electronics, but they were out of ideas. Thanks in advance for any suggestions.
Pages: [1] 2 3 ... 10