BF527 EZ-KIT

TOPPERS/JSPカーネルの移植をやるにあたって，商社やADKKに無償レンタルをお願いしたが，ことごとく出払っていたので，購入．
お付き合いの意味も込めて商社から買おうと思ったら，納期2〜3週間．間に合わねー，ということで，DigiKeyで決済．約98,000円．
たぶん自費で買った評価ボードでは，一二を争う高額ボードですな．…というのが数日前．

今日，届いた

まーリッチなボードだなぁ．98,000円するのは仕方ない．でも，こんなにリッチにする必要があるのかは判らない．

ICEbearはBF527をサポートしていない．

同僚からの指摘で気づく．がーん．…つかえねぇ．有償っても同人ハードウェアの規模だから仕方ないか．

UrJTAGはBF527をサポートしている．

オープンソースもののほうが進んでいるというのは，よくある話．だからサポートビジネスも成り立つワケだけれども．
早速刺身包丁で裁いてみた．

UrJTAG 0.9 #8208
Copyright (C) 2002, 2003 ETC s.r.o.
Copyright (C) 2007, 2008 Kolja Waschk and the respective authors

UrJTAG is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
There is absolutely no warranty for UrJTAG.

WARNING: UrJTAG may damage your hardware!
Type "quit" to exit, "help" for help.

jtag> cable OOCDLink-s
Connected to libftd2xx driver.
jtag> detect
IR length: 5
Chain length: 1
Device Id: 00000010011111100000000011001011 (0x00000000027E00CB)
  Manufacturer: Analog Devices
  Part(0):         BF527
  Stepping:     0
  Filename:     /opt/urjtag/share/urjtag/analog/bf527/bf527
jtag> initbus bf527_ezkit
jtag> detectflash 0x20000000
Query identification string:
	Primary Algorithm Command Set and Control Interface ID Code: 0x0002 (AMD/Fujitsu Standard Command Set)
	Alternate Algorithm Command Set and Control Interface ID Code: 0x0000 (null)
Query system interface information:
	Vcc Logic Supply Minimum Write/Erase or Write voltage: 2700 mV
	Vcc Logic Supply Maximum Write/Erase or Write voltage: 3600 mV
	Vpp [Programming] Supply Minimum Write/Erase voltage: 11500 mV
	Vpp [Programming] Supply Maximum Write/Erase voltage: 12500 mV
	Typical timeout per single byte/word program: 16 us
	Typical timeout for maximum-size multi-byte program: 0 us
	Typical timeout per individual block erase: 1024 ms
	Typical timeout for full chip erase: 0 ms
	Maximum timeout for byte/word program: 256 us
	Maximum timeout for multi-byte program: 0 us
	Maximum timeout per individual block erase: 8192 ms
	Maximum timeout for chip erase: 0 ms
Device geometry definition:
	Device Size: 4194304 B (4096 KiB, 4 MiB)
	Flash Device Interface Code description: 0x0002 (x8/x16)
	Maximum number of bytes in multi-byte program: 1
	Number of Erase Block Regions within device: 2
	Erase Block Region Information:
		Region 0:
			Erase Block Size: 8192 B (8 KiB)
			Number of Erase Blocks: 8
		Region 1:
			Erase Block Size: 65536 B (64 KiB)
			Number of Erase Blocks: 63
Primary Vendor-Specific Extended Query:
	Major version number: 1
	Minor version number: 0
	Address Sensitive Unlock: Required
	Erase Suspend: Read/write
	Sector Protect: 1 sectors per group
	Sector Temporary Unprotect: Not supported
	Sector Protect/Unprotect Scheme: 29BDS640 mode (Software Command Locking)
	Simultaneous Operation: Not supported
	Burst Mode Type: Supported
	Page Mode Type: Not supported

フラッシュが認識されているので，たぶん問題ない．ついでにBF537に繋いでみたけれど，
同様に問題ない様子．

とっととgdbproxy をビルドして同僚に投げなければ．