Q&A - Recent Threads

Writing to flash memory for Linux with BF537 EZLITE and ICE 1000 through CCES

T1234 — Thu, 20 Jul 2023 20:29:53 GMT

I am working with the BF537 EZLITE development board and an ICE 1000 emulator JTAG. The IDE I am using is CCES 2.11.1. I am interested in trying to run Linux and write to the flash memory. How can I go about this in CCES and is there an example project I could look at? I would also like to confirm if this development board has flash memory.

EZ Kit OS Install

analogResearcher — Sun, 22 Jan 2023 12:26:39 GMT

Hi, I'm looking to get started with some Blackfin research but struggling to find documentation and am generally unsure what I should be looking to get hold of.

I'd like to get uClinux running on a BF518, so was looking at picking up a BF518 EZ-Kit (or EZ-Board?), but the EZ-Board Evaluation System Manual doesn't document how I'd go about installing uClinux (or any OS) onto the board. Or if it even supports an installed OS. I'm also aware that uClinux is end of life.

So far, I've setup the Blackfin Toolchain and I'm able to compile my own code for Blackfin. For example, I've got hello world compiled as a bFLT for the BF518. I got the toolchain from Sourceforge and noticed repos for UBoot. So I'm guessing I'd need to get an EZ-Board, flash UBoot, get uClinux from somewhere and then install that? But I can't find any documentation on how to go about doing this.

Any help and general pointing in the right direction would be greatly appreciated

ADSP-BF609 Dual Core Linux

barbiomalefico — Fri, 05 Aug 2022 13:46:46 GMT

Is it possibile to assign both core A and B to linux?

If yes, could you please tell me how to do so (or point me to the correct documentation)

if not, is there any way to have some kind of scheduler on the bare metal core?

Y2038K Rollover Issue

MikeHaines — Fri, 29 Apr 2022 01:16:00 GMT

I have a project using old kernel and tools that have the Y2038K rollover vulnerability. Has this been addressed in Blackfin ? I've searched but not found any mention of it.

Thank you

Mike

bf 537 stamp, uart boot problem

Shoot — Mon, 21 Mar 2022 00:15:44 GMT

Hello, I am new to working with the ADZS-BF537-STAMP board. I tried to transfer the bootloader to the board in order to install Linux in the future. The first thing I did: Moved the boot mode switch to position 7, switch SW4 to the OFF ON OFF OFF position, switch SW6 to the ON ON ON ON position and removed the jumper JP9.

Then, according to the instructions, I checked whether there is a connection with the board, restarted the board 9 times, constantly pressing the space bar, received 9 answers, one answer per reboot, so USB->Serial Converter (RS232) is working fine and there is a connection, I used minicom on Ubuntu OS 20.04 to check.

Next, I put the jumper JP9 and received in the minicom window what I enter on the keyboard, then removed the jumper again.
After that, I downloaded GNU Toolchain for linux from sourceforge.
Next, the most interesting thing is, using bfin-uclinux-ldr, I tried to load u-boot onto the board, but I ran into this

Even if the baud rate is not set manually, the result is the same.
Repeated attempts to restart the board and start transferring u-boot to the board again did not lead to success.
ldrviewer also does not work, responds the time has expired.
I hope someone can help me with solving this problem, thank you in advance!

blackfin 609 flash

Venkat.s — Sat, 05 Feb 2022 11:28:25 GMT

hi,

core 0 -> core 1 -> led switch led blick

how to control core 1 using core 0

in case of core 0 have the core 1 enable function ,

core 1 have gpio ,

in core 0 1 ldr file, and core 1 have multiple ldr file how to create ,

if core 0 automatically run core 1 without use interrupt ,

in core 0 it user choice to control the core 1 ,

if user is given 1 means 1 led light blink ,

2 given means , 2 led will blink,

how to wake up core 1 using core 0

kindly reply me,

signature ,

venkat

blackfin 609 flash

Venkat.s — Sat, 05 Feb 2022 11:23:43 GMT

hi,

core 0 -> core 1 -> led switch led blick

how to control core 1 using core 0

in case of core 0 have the core 1 enable function ,

core 1 have led blink ,

in core 0 have and core 1 have multiple ldr file how to create the path,

if core 0 run and automatically run core 1 without use interrupt ,

in core 0 it user choice to control the core 1 ,

if user is given 1 means 1 led light blink ,

2 given means , 2 led will blink,

how to wake up core 1 using core 0

kindly reply me,

signature ,

venkat

LT8471 DC/DC converter not working

harini — Wed, 30 Jun 2021 04:23:44 GMT

This is our schematic of 24 V to +/- 12 V buck converter. But we are unable to get the specified output across pin 22 (-12 V), pin 26(+12 V) and even in the ground terminal, we get 24V at all the 3 above mentioned points. We are not sure as to where we could have gone wrong. Can you please help us with this doubt?

Any firmware implications when changing BF537 package?

jon_harris8 — Fri, 12 Mar 2021 18:29:18 GMT

I am looking at replacing a 208 ball ADSP-BF537BBCZ-5BV with a 182 ball ADSP-BF537BBCZ-5AV. As far as I can tell, there should be no need for any firmware changes to support the different package. I don't see anywhere in the configuration files were you have to specify the package. I am using uClinux and u-boot. Can anyone confirm that?

Linux on blackfin

mema — Sat, 19 Dec 2020 17:24:30 GMT

How can I put linux on blackfin 548

SC589 EZ-kit- ARM reboot without DSP reboot

RSingiresu9 — Mon, 24 Feb 2020 22:24:12 GMT

Hi,

I need to reboot ARM from linux without a DSP reboot. I would need to do the right thing for both reboot command and watchdog rebooting of the ARM core.

Could you please help me to find the right set of instructions to do it?

my setup information is listed below and i'm using linux add-in 1.3.1

ADSP-SC589 rev 1.0

ADSP-SC589-EZ-BRD

SC589-EZ-Board Rev 1.1 (BOM rev 1.6)

Let me know if you need any other information.

Could i deploy linux OS on board BF533 EZ Lite Kit

Thanh Nguyen — Fri, 31 Jan 2020 10:18:19 GMT

Hi, i am testing board BF533 Ez Lite Kit, and i have questions :

- Can i install a OS (linux or some other RTOS) on the board ?

- If not, could you recommend me some board of ADSP BF533, which can install OS.

ADSP-SC589 EZ-Board Linux networking

bnilsson — Sat, 02 Nov 2019 13:03:43 GMT

I have now successfully installed the linux image on a SDcard on my ADSP-SC589 EZ-Board it is booting.

However, there is no DHCP networking enabled on this linux image, so I have to use the minicom.

Are there any instructions on how to set up DHCP on the ARM linux core?

The info found on google does not always apply, since this pre-configured image does not contain all networking tools.

i tried /etc/network/interfaces:

# interface file auto-generated by buildroot
auto eth0
iface eth0 inet dhcp
auto lo
iface lo inet loopback

but it had no effect.

/dev/ttyUSB0 missing

bnilsson — Fri, 01 Nov 2019 20:33:31 GMT

Dear linux support,

I am trying to flash u-boot of my ADZS-SC589-EZLITE, but I am stuck because according to the instructions, minicom wants a /dev/ttyUSB0.

My Ubuntu 16.04 will not create any /dev/ttyUSB0 when I connect the USB cable from the ICE-1000.

I have tested another USB-Serial adapter, and this works fine, /dev/ttyUSB0 pops up as it should for this device.

lsusb for the two devices:

Bus 001 Device 005: ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port [pl2303]

Bus 001 Device 004: ID 064b:0617 Analog Devices, Inc. (White Mountain DSP)

dmesg:

[ 865.599167] usb 1-1.4: new high-speed USB device number 4 using ehci-pci

[ 865.712589] usb 1-1.4: New USB device found, idVendor=064b, idProduct=0617

[ 865.712593] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[ 865.712596] usb 1-1.4: Product: Blackfin USB Device

[ 865.712598] usb 1-1.4: Manufacturer: Analog Devices, Inc.

[ 1446.245408] usb 1-1.5: new full-speed USB device number 5 using ehci-pci

[ 1446.354878] usb 1-1.5: New USB device found, idVendor=0557, idProduct=2008

[ 1446.354882] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[ 1446.354885] usb 1-1.5: Product: USB-Serial Controller

[ 1446.354887] usb 1-1.5: Manufacturer: Prolific Technology Inc.

[ 1446.355469] pl2303 1-1.5:1.0: pl2303 converter detected

[ 1446.358982] usb 1-1.5: pl2303 converter now attached to ttyUSB0

How can I make my Ubuntu accept the ICE-1000 as a serial device?

bfin-jtag does not work with ICE-1000 on BF537

maldata — Tue, 22 Oct 2019 22:51:24 GMT

I have an Analog Devices ICE-1000 USB device. I need to read/write the flash memory on a BF537 device so I can get u-boot loaded, and I expected that the bfin-jtag program would be able to do that (it looks like a re-branded urjtag). However, when I try to connect, I get the following:

jtag> cable ICE-100B

error: Couldn't connect to suitable USB device.
error: not found: no USB connections

The jtag device is listed in dmesg:

[ 196.999107] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 197.017758] usb 1-1: New USB device found, idVendor=064b, idProduct=0617
[ 197.017761] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 197.017763] usb 1-1: Product: Blackfin USB Device
[ 197.017764] usb 1-1: Manufacturer: Analog Devices, Inc.

However, I don't know if there's a kernel module that needs to be loaded for it or something. Can anyone help be figure this out? Suggestions for other ways to get u-boot loaded are welcome as well. I tried UART boot via ldrviewer, and that didn't work either.

Thanks!

uClinux for blackfin on 32b Ubuntu16

tjarcob — Fri, 30 Aug 2019 14:49:20 GMT

Hi All,

We're trying to setup a fresh bfin-installation on ubuntu 16, 32bit version (BF607). Buildroot, the toolchain, linux kernel and u-boot.

There seems to be a lot of information gone from the internet (like http://docs.blackfin.uclinux.org/doku.php?id=toolchain:installing)

Is there a good guide for doing so?

What we've done is downloading the packages from http://sourceforge.net via

https://ez.analog.com/dsp/software-and-development-tools/linux-blackfin/f/q-a/108907/end-of-life-for-blackfin-linux

These packages are:

1)blackfin-toolchain-2011R1-RC4.i386.tar.bz2

2)blackfin-toolchain-elf-gcc-4.3-2011R1-RC4.i386.tar.bz2

3)blackfin-toolchain-uclibc-default-2011R1-RC4.i386.tar.bz2

4)u-boot-2013.07-2014R1.tar.bz2

We've unpacked packages 1,2,3 to ~/opt/

and made a newpath script that adds the ~/opt/uClinux/bfin-elf/bin directory to PATH

in uboot dir we've executed 'make bf609_ezkit_config' (which did work and now seems to be broken, somehow)

and then tried to run 'make'

The 'make'for u-boot results in an error: /bin/sh: bfin-uclinux-gcc command not found

And now We're stuck and have no idea how to move forward...

Could someone help us out? (or point us to a full install guide).

Best regards,

Tjar

SPI Slave boot for BF537

tejaswi — Wed, 28 Aug 2019 10:54:04 GMT

Hi,

I am trying to boot BF537 using SPI boot method.

I have two BF537 EZLite kits. Is there any sample code for getting SPI boot working ?

Regards,

Tejaswi

Linux device driver support

raje.embd13@gmail.com — Wed, 24 Jul 2019 12:42:11 GMT

Hi All,

I am start working on LtC2873. Is this micro controller have open source Linux device driver support ? If available send me the inputs

I want to enable Ltc2873 driver on my platform( that support both both RS232/485)

Thanks,

RajendraPrasad

Minimal Requirement for Building uClinux for Blackfin BF538F

siddh4nt — Fri, 22 Mar 2019 09:08:43 GMT

Hi,

Hope you are doing fantastic.

I am having a query, could anybody tell me what are the minimum hardware requirements with Black Processor (ADSP-BF538F) in order to port and run uCLinux.

Major components interfaced with Blackfin are SDRAM, AD9364 and Artix 7 FPGA.

I would also love to get the information about build toolchains available for blackfin processor, please share some helpful resource.

Thanks & Regards

-Siddhant

End of Life for Blackfin Linux

ADIApproved — Fri, 22 Mar 2019 08:53:20 GMT

For the past 14 years Analog Devices has developed and maintained the ports of uCLinux, uBoot, GCC, GDB and Buildroot for the Blackfin BF5xx architecture.

We will be shortly stopping our support and maintenance of these products.

The documentation currently hosted on the blackfin.uclinux.org website will no longer be available. However the sources and binary distributions will still be available from SourceForge at the following locations:

Component	Files	Repository
GCC Toolchain	http://sourceforge.net/projects/adi-toolchain	http://sourceforge.net/p/adi-toolchain/blackfin
uBoot Bootloader	http://sourceforge.net/projects/adi-u-boot/files	http://sourceforge.net/p/adi-u-boot/code
Buildroot and kernel	http://sourceforge.net/projects/adi-buildroot	http://sourceforge.net/p/adi-linux/code http://sourceforge.net/p/adi-buildroot/code
Hardware	http://sourceforge.net/projects/adiopshw/files

Support for Blackfin uCLinux can still be obtain by the community group at https://ez.analog.com/dsp/software-and-development-tools/linux-for-adsp-sc5xx-processors/

Analog Devices continues to support Linux for the ADSP-SC5xx processor family. For more information please visit https://www.analog.com/en/design-center/processors-and-dsp/evaluation-and-development-software/linuxaddin.html

Analog Devices believes in Open Source Software and continues to support the effort. For more details see https://github.com/analogdevicesinc

Bf548 + Buildroot + kernel

markb1 — Fri, 08 Mar 2019 15:25:15 GMT

I am trying to get a development system updated and I am looking for a step-by-step guide on how to get the toolchain to interface with buildroot correctly.

I'm also having issues with trying to get the kernel into buildroot and could use some pointers.

The last time I messed with this I was using the uClinux distro (and not buildroot).

WVGA/LCD have not present on BF609

os369510@gmail.com — Sat, 16 Feb 2019 04:46:30 GMT

Hi,

I used buildroot (2014R1) with linux kernel (2014R1) to build a uImage using make bf609-ezkit_config on my ubuntu 18.04 docker.

I just modified some packages to avoid build error (I don't think it's matter with my problem) and then follow this wiki to enable "NEC NL8048HL" within kernel config.

https://blackfin.uclinux.org/doku.php?id=video_loop_back&s[]=wvga&s[]=lcd

I've connecting ADZS-WVGALCD-EX3 to P2A and P3A on ADSP-BF609 EZ-BOARD.

The branch of u-boot is 2014R1 from default boot mode (SW2).

The destination I want is show a image or video on WVGA/LCD but I can not found /dev/fb on my system and I found the kernel log shows below error:

root:/> dmesg | grep bf609_nl8048
bf609_nl8048 bf609_nl8048.2: Can't start LCD
platform bf609_nl8048.2: Driver bf609_nl8048 requests probe deferral
pinctrl-adi2 pinctrl-adi2.0: pin PA0 already requested by physmap-flash.0; cannot claim for bf609_nl8048.2
pinctrl-adi2 pinctrl-adi2.0: pin-0 (bf609_nl8048.2) status -22
bf609_nl8048 bf609_nl8048.2: Error applying setting, reverse things back
pinctrl-adi2 pinctrl-adi2.0: pin PA0 already requested by physmap-flash.0; cannot claim for bf609_nl8048.2
pinctrl-adi2 pinctrl-adi2.0: pin-0 (bf609_nl8048.2) status -22
bf609_nl8048 bf609_nl8048.2: Error applying setting, reverse things back
bf609_nl8048 bf609_nl8048.2: Fail to request ppi peripheral pins.
bf609_nl8048: probe of bf609_nl8048.2 failed with error -16

Does the "PA0" is the interface same as P2A and P3A I used?

How do I configure it?

or anything I misunderstand please let me know, Thanks.

Sincerely,

Jeremy Su

Can't use Ethernet after u-boot with SC584 EZKIT (BOM 2.4, Board 1.4A)

dynamics — Thu, 07 Feb 2019 04:14:15 GMT

I lost my last week when to try to install u-boot on my sc583 ezkit board.

My board version 1.4A, BOM 2.4, Linux add in 1.3.0, cces 2.8.3.

U-boot wrote "Net: Phy 1 not found" because ethernet chip is DP83867IR - not that in docs and software!!!!!!

What the hell?!!! Why I must lost my time for your job and can't to use my kit for my tasks????

Unable to mount root file system with message "VFS: Cannot open root device mtdblock ..."

kv193 — Tue, 05 Feb 2019 09:56:34 GMT

Hello.

I am trying to replace MMC card (all work fine) in my BF533 device by Serial Flash.

U-Boot is moved to sf and boot fine, sf work :

================================================
bfin> sf probe 2
SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, total 16 MiB
bfin>
================================================

I write uImage (with initramfs) to offset 0x100000 and test if. All right. I write rootfs.jffs2 to offset 0x700000 and manualy mount it to /mnt:

================================================
m25p80 spi0.10: s25fl129p1 (16384 Kbytes)
Creating 3 MTD partitions on "m25p80":
0x000000000000-0x000000100000 : "reserve(spi)"
0x000000100000-0x000000700000 : "linux kernel(spi)"
0x000000700000-0x000000d00000 : "file system(spi)"
...
root:/> mount -t jffs2 /dev/mtdblock2 /mnt
root:/> ls /mnt
bin       etc       lib       mnt       root      srv       test.txt usr
dev       init      lib32     proc      sbin      sys       tmp       var
root:/>
==============================================

After that I set environment in U-Boot:

=============================================
bfin> printenv
baudrate=115200
bootargs=root=/dev/mtdblock2 rw rootfstype=jffs2 clkin_hz=25000000 earlyprintk=serial,uart0,115200 console=ttyBF0,115200
...
==============================================

Load vmImage (without initramfs) and boot it:

==============================================
bfin> loadb
## Ready for binary (kermit) download to 0x01000000 at 115200 bps..
bootm
## Booting kernel from Legacy Image at 01000000 ...
  Image Name:   bf533-0.6-3.10.10-ADI-2014R1
  Image Type:   Blackfin Linux Kernel Image (gzip compressed)
  Data Size:    1181793 Bytes = 1.1 MiB
  Load Address: 00001000
  Entry Point: 00202620
  Verifying Checksum ... OK
  Uncompressing Kernel Image ... OK
Starting Kernel at = 00202620
Linux version 3.10.10-ADI-2014R1 (kv193@E450-OpenSUSE.suse) (gcc version 4.3.5 (ADI-2014R1-RC2) ) #22 Mon Feb 4 22:53:12 MSK 2019
register early platform devices
bootconsole [early_shadow0] enabled
bootconsole [early_BFuart0] enabled
early printk enabled on early_BFuart0
Board Memory: 32MB
Kernel Managed Memory: 32MB
Memory map:
fixedcode = 0x00000400-0x00000490
text      = 0x00001000-0x0015cfb0
rodata    = 0x0015cfb0-0x001d07b8
bss       = 0x001d1000-0x001e4284
data      = 0x001e42a0-0x001fc000
   stack   = 0x001fa000-0x001fc000
init      = 0x001fc000-0x00218000
available = 0x00218000-0x01f00000
DMA Zone = 0x01f00000-0x02000000
Hardware Trace active and enabled
Boot Mode: 6
Reset caused by Software reset
Blackfin support (C) 2004-2010 Analog Devices, Inc.
Compiled for ADSP-BF533 Rev 0.6
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 250 MHz core clock and 50 MHz System Clock
NOMPU: setting up cplb tables
Instruction Cache Enabled for CPU0
External memory: cacheable in instruction cache
Data Cache Enabled for CPU0
External memory: cacheable (write-back) in data cache
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 7874
Kernel command line: root=/dev/mtdblock2 rw rootfstype=jffs2 clkin_hz=25000000 earlyprintk=serial,uart0,115200 console=ttyBF0,115200
PID hash table entries: 128 (order: -3, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Sorting __ex_table...
Memory available: 29272k/32768k RAM, (112k init code, 1391k kernel code, 637k data, 1024k dma, 332k reserved)
NR_IRQS:81
Configuring Blackfin Priority Driven Interrupts
Calibrating delay loop... 495.10 BogoMIPS (lpj=990208)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
devtmpfs: initialized
Blackfin Scratchpad data SRAM: 4 KB
Blackfin L1 Data A SRAM: 16 KB (16 KB free)
Blackfin L1 Data B SRAM: 16 KB (16 KB free)
Blackfin L1 Instruction SRAM: 64 KB (51 KB free)
NET: Registered protocol family 16
Blackfin DMA Controller
cm_bf533_init(): registering device resources
bio: create slab <bio-0> at 0
bfin-spi bfin-spi.0: master is unqueued, this is deprecated
bfin-spi bfin-spi.0: Blackfin on-chip SPI Controller Driver, Version 1.0, regs@ffc00500, dma channel@5
Switching to clocksource bfin_cs_cycles
NET: Registered protocol family 2
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
debug-mmrs: setting up Blackfin MMR debugfs
jffs2: version 2.2. (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 57
io scheduler noop registered (default)
bfin-uart: Blackfin serial driver
bfin-uart.0: ttyBF0 at MMIO 0xffc00400 (irq = 21) is a BFIN-UART
console [ttyBF0] enabled, bootconsole disabled
console [ttyBF0] enabled, bootconsole disabled
brd: module loaded
m25p80 spi0.10: found s25fl129p1, expected m25p64
m25p80 spi0.10: s25fl129p1 (16384 Kbytes)
Creating 3 MTD partitions on "m25p80":
0x000000000000-0x000000100000 : "reserve(spi)"
0x000000100000-0x000000700000 : "linux kernel(spi)"
0x000000700000-0x000000d00000 : "file system(spi)"
rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0
bfin_wdt: initialized: timeout=20 sec (nowayout=0)
TCP: cubic registered
NET: Registered protocol family 17
rtc-bfin rtc-bfin: setting system clock to 1970-01-01 00:54:33 UTC (3273)
Warning: unable to open an initial console.
VFS: Cannot open root device "mtdblock2" or unknown-block(31,2): error -2
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0 (driver?)
1f01            6144 mtdblock1 (driver?)
1f02            6144 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
========================================

What I do wrong? Where mistake?

ADSP-BF537 Hardware Revision

jyeh9801 — Thu, 24 Jan 2019 02:05:16 GMT

I've recently got a new batch of boards in where after programming them, I've noticed a warning in the boot dialogue that the OS was compiled for hardware revision 3, but was running on 2. I've looked at the silicon anomaly list for the BF537 but have a hard time determining from it how likely there is to be an issue with running this hardware/software configuration. The specific OS is uCLinux 2008R1.5.

Is it possible/practical to determine interchangeability based on the silicon anomaly list? Or is this one of those "run it and see" type situations? Is the only real answer to re-compile with either 0.2 or "all" version support?