Analog.com Analog Dialogue Wiki English
Analog.com Analog Dialogue Wiki 简体中文
EngineerZone
EngineerZone
  • Site
  • User
  • Site
  • Search
  • User
EngineerZone
EngineerZone
  • Log in
  • Site
  • Search
  • Log in
  • Home
  • Blogs ⌵
    • EngineerZone Spotlight
    • The Engineering Mind
  • Browse ⌵
    • All Groups
    • All Members
  • Support ⌵
    • 3D ToF Depth Sensing
    • Amplifiers
    • Analog Microcontrollers
    • Analysis Control Evaluation (ACE) Software
    • Audio
    • Clock and Timing
    • Data Converters
    • Design Tools and Calculators
    • Direct Digital Synthesis (DDS)
    • Embedded Vision Sensing
    • Energy Monitoring and Metering
    • FPGA Reference Designs
    • Industrial Ethernet
    • Interface and Isolation
    • Low Power RF Transceivers
    • MEMS Inertial Sensors
    • Motor Control Hardware Platforms
    • Optical Sensing
    • Power By Linear
    • Processors and DSP
    • Reference Circuits
    • RF and Microwave
    • Signal Chain Power (SCP)
    • Switches/Multiplexers
    • Temperature Sensors
    • Video
    • Wide Band RF Transceivers
    • Wireless Sensor Networks Reference Library
  • My EZ
  • More
  • Cancel
  • 主页
  • 浏览 ⌵
    • 收件箱
    • 个人设置
    • 会员
    • 专区列表
  • 论坛专区 ⌵
    • 放大器专区
    • 精密转换器专区
    • 音频专区
    • ADE电能计量专区
    • MEMS和传感器专区
    • 接口和隔离专区
    • Power 中文专区
    • ADUC微处理器专区
    • 锁相环专区
    • 开关和多路复用器专区
    • 温度传感器
    • 基准电压源专区
    • 资源库
    • 论坛使用指南
    • 技术支持参考库
    • 在线研讨会
    • 论坛社群活动
    • 论坛激励活动
  • More
  • Cancel
Linux Distribution for Blackfin
  • Processors and DSP
  • Software and Development Tools
  • Linux Distribution for Blackfin
  • More
  • Cancel
Linux Distribution for Blackfin
Documents 2007-04-03 05:21:47     SPI eeprom write read
  • Q&A
  • Discussions
  • Documents
  • File Uploads
  • Video/Images
  • Sub-Groups
  • Members
  • Tags
  • Reports
  • Managers
  • More
  • Cancel
  • New
Linux Distribution for Blackfin requires membership for participation - click to join
  • Documents
  • 2005-06-18 08:54:21     how load and compile the uClinux kernel
  • 2007-04-03 05:21:47     SPI eeprom write read
  • 2007-06-05 06:05:45     How to load Linux from JFFS2/NAND flash
  • 2011-10-18 00:59:25     Attention: help forums are moving to the Analog Devices' EngineerZone Since Oct.24
  • 2013R1 Linux release for Blackfin
  • AD5700/AD5700-1 RXD Activity After HART Carrier Off
  • DAS U-BOOT FOR BLACKFIN BUGS ARCHIVE
  • Development of the Blackfin Linux Projects is moved to sourceforge.net since Jul. 20, 2013.
  • FAQ: Demo the video capability on BF609
  • FAQ: Does ADI u-boot support BF70x processors?
  • FAQ: GDB commands for newbie.
  • FAQ: Getting Started with SDP-B using GCC Toolchain
  • FAQ: How do I re-use projects built in VDSP in a GCC Bare metal environment?
  • FAQ: How to make u-boot to do somthing automatically after booting
  • FAQ: Moving to a newer Blacinfin Linux release version
  • FAQ: Why I get compile errors with the default ADI release
  • GNU TOOLCHAIN FOR BLACKFIN BUGS ARCHIVE
  • GNU TOOLCHAIN FOR BLACKFIN SUPPORT COMMUNITY
  • How can I flash the uImage into Flash and boot from it?
  • How to autorun applications in uClinux
  • I want to use the second core of Blackfin in Linux to boost the performance, is there a quick guide?
  • LINUX DISTRIBUTION FOR BLACKFIN SUPPORT COMMUNITY
  • +Parent Document for U-Boot Bug Archive
  • +Parent Document for U-Boot Bug Forum Archive
  • +Parent for all content moved from GNU Archive
  • Re: bf537 SPI Bus: To use Kernel, Userspace, or Bitbang control
  • TAGS LIST: Interface and Isolation
  • The 2013R1 Linux release for Blackfin
  • The development of the Blackfin Linux Projects is moved to sourceforge.net since Jul. 20, 2013.
  • Use gdbproxy to debug kernel
  • Use the ADI test scripts to auto config and build a target for a set of function
  • what does a successful "loading u-boot over uart" look like?
  • Where can I get Linux Blackfin documents?
  • [#3812] svn head u-boot build fails initcode.c on older parts
  • [#5809] gcc/g++ test on trunk head regression compared with testing on 09r1.1
  • [#5825] gdb: symbols cannot map to correct source file
  • [#5826] gdb.cp/userdef.exp fails to load executable's loadmap in fdpic testing
  • [#5827] gcc.dg/trampoline-1.c test on hardware fdpic fails on bf527 but pass on bf548
  • [#5828] libstdc++-4.3 21_strings/basic_string/capacity/char/18654.cc test on fdpic would fail
  • [#5842] gdb.base/sigall.exp would fail when debug through serial port 1
  • [#5845] gdb.gdbtk/c_variable.exp fails to be tested through /dev/ttyBF1
  • [#5858] gcc.c-torture/execute/memset-2.c regression now
  • [#5880] ldr-utils build fails
  • [#5886] bfin-elf-libstdc++-4.3 has two regression case compared with libstdc++-4.1
  • [#5887] bfin-uclinux-libstdc++-4.3 ext/headers.cc regress
  • [#5888] bfin-uclinux-libmudflap-4.3.sum pass40-frag.c output pattern test regress
  • [#5889] toolchain-regtest -r (test compare) option has multiple issues
  • [#5890] toolchain-regtest does not handle unknown args very well
  • [#5891] trunk head gdbproxy can't find and open urjtag device
  • [#5892] bfin-uclinux-libstdc++-4.3 23_containers/set/modifiers/16728.cc fail sometimes
  • [#5895] prepare_target_solibs in toolchain-regtest fail to check the libs
  • [#5922] gcc/g++ testcase regression in simulator test for Unhandled instruction
  • [#5928] gas has problems with local labels in LOOP instructions
  • [#5935] toolchain-regtest can't find the toolchain to be tested now
  • [#5938] toolchain-regtest aborts when previous results are missing
  • [#5953] test libmudflap fails for mfconfig.exp.in missing
  • [#5962] mcpu doesn't get passed in testing linux-uclibc toolchain
  • [#5965] elf-simulator test cases regress for program stopped with signal 11
  • [#5966] build sim binutils fails now
  • [#5970] Build oprofile failed at bfd library after toolchain upgrade from 3801 to 3852
  • [#5974] CPLB fault or SIGABRT when throwing&catching C++ exception in static FDPIC ELF
  • [#5980] trunk toolchain cannot find -lbffastfp with -mfast-fp
  • [#5981] gas tests have regressions due to SHIFT->LSHIFT change
  • [#5989] build toolchain fails at binutils-2.17/sim/bfin
  • [#6018] gcc-4.3 ICEs with {interrupt,exception,nmi}_handler function attributes in copyprop_hardreg_forward_1, at regrename.c:1787
  • [#6030] test bfin-elf via simulator, it stops in gdb.gdbtk/c_variable.exp with case "stop in subroutine1"
  • [#7702] GDB fails to find prologue
  • [#7806] gdb test regression after using buildroot as target os
  • [DOC] Configuring Qt Creator as SDK for uClinux

2007-04-03 05:21:47     SPI eeprom write read

2007-04-03 05:21:47     SPI eeprom write read

Richard Aldrich (UNITED KINGDOM)

Message: 23979    I'm using the latest SVN versions of uboot, toolchain and uclinux (updated and compiled yesterday).

I followed the document http://docs.blackfin.uclinux.org/doku.php?id=accessing_serial_nor_flash_with_u-boot

to attempt to write to SPI flash (ST M25P64). I call the eeprom write command, and it appears to works, then I read it back to another memory location.

However, when I do the memory compare, it says that 0 bytes are the same (output is something like:

cmp.b 0x1000000 0x2000000 $(filesize)

byte at 0x01000000 (0x40) != byte at 0x02000000 (0x00)

Total of 0 bytes were the same)

where 0x2000000 is the location I have read the eeprom to.

Does anyone have any ideas on what I should investigate next?

QuoteReplyEditDelete

2007-04-04 00:37:59     Re: SPI eeprom write read

Mike Frysinger (UNITED STATES)

Message: 24009    this is a custom board right ?  i would first verify memory is sane by using the u-boot "mtest" command ... then try writing out all like 0x00 and 0xFF to the flash and then read it back out and use md.b to verify the location you read back out matches

QuoteReplyEditDelete

2007-04-04 09:01:50     Re: SPI eeprom write read

Richard Aldrich (UNITED KINGDOM)

Message: 24039    Ok, I am now able to write to and read from the SPI memory (its on a BF 537-stamp board). My problem came down to the wire length / type that had been used to connect the memory to a header.

I am able to load the uImage and read it back, and boot it and this process works well. All the bytes are identical.

However, I now want to investigate booting the u-boot from SPI. What I understand is that I compile u-boot with the

#define BFIN_BOOT_MODE        BF537_SPI_MASTER_BOOT

in the file found at: u-boot/include/configs/bf537-stamp.h

I do this, and then I have written the u-boot.ldr image to the eeprom, at offset 0x0.

I then switch SW16 to 3, and power up. ...nothing happens, I don't get anything back in minicom.

Am I missing a stage along the way? Btw, the board is Rev 0.2

QuoteReplyEditDelete

2007-04-04 14:52:21     Re: SPI eeprom write read

Mike Frysinger (UNITED STATES)

Message: 24062    nope, the steps you've listed are correct ...

in order to take one step out of the equation though, you should try using one of our tested releases:

http://blackfin.uclinux.org/gf/project/u-boot/frs

we have a SPI LDR for u-boot there for the BF537-STAMP ... that should eliminate question of whether it's a software (compiling u-boot) or hardware (using correct settings)

QuoteReplyEditDelete

2008-04-01 10:20:03     Re: SPI eeprom write read

Hadi Boulfelfel (FRANCE)

Message: 53456    I think it's :  #define BFIN_BOOT_MODE        BF537_BOOT_SPI_MASTER     not     BF537_SPI_MASTER_BOOT

TranslateQuoteReplyEditDelete

2008-04-11 10:26:53     Re: SPI eeprom write read

Pafone Lee (CHINA)

Message: 54093    There is also a difference between the docs and the u-boot source code

in http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:release-notes:2007r1

<pre class="code">// ADSP-BF533

#define BF533_BYPASS_BOOT 0x0001

#define BF533_PARA_BOOT 0x0002

#define BF533_SPI_BOOT 0x0004 but in u-boot2008-R1-1.1.6  source code /include/configs/bf533-ezkit.h

#define BFIN_BOOT_MODE       BFIN_BOOT_BYPASS

I don't know whether it is a mistake.

TranslateQuoteReplyEditDelete

2008-04-11 11:58:54     Re: SPI eeprom write read

Mike Frysinger (UNITED STATES)

Message: 54096    there is no difference nor error with the documentation

you're comparing old release notes against a newer release.  that'll never work.

QuoteReplyEditDelete

  • Share
  • History
  • More
  • Cancel
Comments
Anonymous
Related
 
社交网络
快速链接
  • 关于ADI
  • Partners
  • 模拟对话
  • 职业
  • 联系我们
  • 投资信息
  • 新闻中心
  • 质量和可靠性
  • 办事处与代理商
  • Analog Garage
语言
  • English
  • 简体中文
  • 日本語
  • Руccкий
电子快讯

欲获得最新ADI产品、设计工具、培训与活动的相关新闻与文章,请从我们的在线快讯中选出您感兴趣的产品类别,每月或每季度都会发送至您的收件箱。

订阅
Switch to mobile view
Analog Logo
© 1995 - 2021 Analog Devices, Inc. All Rights Reserved 沪ICP备09046653号-1
  • ©
  • 1995 - 2021 Analog Devices, Inc. All Rights Reserved
  • 沪ICP备09046653号-1
  • 网站地图
  • 隐私和保密政策
  • 隐私设置
  • 使用条款
 
Social
Quick Links
  • About ADI
  • Partners
  • Analog Dialogue
  • Careers
  • Contact us
  • Investor Relations
  • News Room
  • Quality & Reliability
  • Sales & Distribution
  • Analog Garage
Languages
  • English
  • 简体中文
  • 日本語
  • Руccкий
Newsletters

Interested in the latest news and articles about ADI products, design tools, training and events? Choose from one of our 12 newsletters that match your product area of interest, delivered monthly or quarterly to your inbox.

Sign Up
Switch to mobile view
Analog Logo
© 1995 - 2021 Analog Devices, Inc. All Rights Reserved 沪ICP备09046653号-1
  • ©
  • 1995 - 2021 Analog Devices, Inc. All Rights Reserved
  • 沪ICP备09046653号-1
  • Sitemap
  • Privacy & Security
  • Privacy Settings
  • Terms of use
EngineerZone Uses cookies to ensure you get the best experience in our community. For more information on cookies, please read our Privacy & Security Statement.