TinyBoards

FAQ

Which BLACKSheep versions support ethernet?
- CM-BF533 and CM-BF561: The DEV-BF5xx version supports the SMSC chip.
- CM-BF537: All versions support the internal MAC.
- TCM-BF537: The DEV-BF5xx version supports the SMSC.
What are the TCP/IP settings for the BLACKSheep versions supporting ethernet?
- The BLACKSheep is preconfigured with an IP-Address of 192.168.0.10. Try "ping 192.168.0.10" from your PC to check the ethernet connection to the core module. The default MAC-Address is AC:DE:48:01:02:03.
  ATTENTION: Currently all Core Modules are shipped with the same MAC-Address, so connecting more than one module to the same ethernet segment may create problems.
Why is the CF-card and/or SD-card not working with the BLACKSheep flashed on the Core Module?
- The Core Modules are shipped with a standalone version of the BLACKSheep. The BLACKSheep standalone version does not support peripherals. To get full access to the peripherals of your eval board you have to flash the Core Modules with the BLACKSheep version according to your baseboard, either the DEV-BF5xx or the EVAL-BF5xx. The appropriate BLACKSheep versions can be found on your support CD or you can download the latest version from our homepage.
  Please refer to the BLACKSheep "Command Reference Manual" to see how to flash a new BLACKSheep version.
Can I flash the Core Modules with a new BLACKSheep version without having a JTAG device?
- Yes you can! First copy the new BLACKSheep loader file to your Core Module using the "xmt" command on the BLACKSheep console. Then use the "flash" command to flash the new version. Refer to the BLACKSheep "Command Reference Manual" to learn more about the BLACKSheep commands.
Which JTAG devices are supported by the Core Modules?
- The Core Modules support all JTAG devices that are compatible with the Blackfin processor family from Analog Devices.
I get error messages while downloading examples with the JTAG device, what is wrong?
- Please make sure you have updated the xml-files in the "ArchDef" directory in the installation path of the VDSP++. The settings within the xml-files are for the EZ-KIT LITE from Analog Devices. This boards have different SDRAM settings.
  The VDSP++ uses these settings to initilize the SDRAM during the start of the VDSP++. Download the modified xml-files from our homepage (config-files). Rename the old files and copy the new one into the directory. Please be aware that the EZ-KIT is no longer working with the new settings.
Why does the BLACKSheep hang-up during a flash erase process on the TCM-BF537?
- The flash on the TCM-BF537 is locked per default. Type "flash -unlock" prior to start an erase process.
How can I flash the uboot hexfile?
- Without a JTAG device:
  Connect to the Core Module using a terminal programm like Hyperterminal under Windows or minicom under linux.
  On the BLACKSheep console type "xmr filename".
  Start uploading the uboot hexfile over your terminal programm using the xmodem protocol.
  Type "flash -rsdev" to erase the flash device.
  Type "flash filename -b" to flash the hexfile.
  Change the boot mode to "00". Refer to the Hardware User Manual of your EVAL-BF5xx or DEV-BF5xx Board to see how to change the boot mode.
  After the next reset or power on the uboot boot screen should appear.
  ATTENTION: FLASHING A HEXFILE WITH THE "-b" OPTION OVERWRITES THE BLACKSHEEP BOOTLOADER. YOU NEED A JTAG DEVICE TO REINSTALL IT.
  Please refer to the next question to learn how to flash the uboot without overwriting the BLACKSheep boot loader.
  To learn more about the BLACKSheep commands please refer to the BLACKSheep Help Command Reference Manual.
- Using a JTAG device:
  Please refer to the appropriate flash tool description for your JTAG device.
Is there a possibility to flash the uboot without overwriting the BLACKSheep and changing the boot mode?
- Yes there is! After uploading the uboot hexfile type "flash filename -a" on the BLACKSheep console the uboot will be flashed as an application without overwriting the BLACKSheep. You can then start the uboot by typing "load 1 -de".
What are the main differences between the CM-BF537E/U and the TCM-BF537?
- The CM-BF537E has the physical ethernet on the Core Module.
- The CM-BF537U has a USB2.0 device chip mounted on the Core Module.
- On the TCM-BF537 only the SDRAM and the flash are mounted.
- Flash:
  - CM-BF5xxx: 2MB of J3 flash
  - TCM-BF537: 4 or 8 MB of P30 flash, depending on the revision
- Temperature range:
  - CM-BF5xxx: consumer
  - TCM-BF537: industrial
- Dimensions:
  - CM-BF5xxx: 31 x 36mm
  - TCM-BF537: 27,4 x 27,4 mm
Why do I get an error (-7: Flash not empty) while trying to flash a new hex-file with the flash command of the BLACKSheep, also if the flash is empty?
- There are two versions of the BLACKSheep with a bug in the flash driver: Version "EVAL-BF5xx 0.5.1 build Jul 14" and Version "EVAL-BF5xx 0.5.1 build Jul 18". If your Core Module is flashed with one of thess two versions please update your BLACKSheep using the update tool located in the software download section. Follow the instructions given in the readme.txt file. Type "ver" on the BLACKSheep console to verify witch BLACKSheep version is flashed on your coremodule.
Why does the BLACKSheep not boot when I do not connect an USB cable to the UART-USB bridge of the EVAL-BF5xx Board?
- The BLACKSheep uses the UART as terminal interface. The UART is connected to the USB-UART bridge per default. If you do not connect an USB cable the USB-chip is not powerd and produces undefined behavior on the UART RX pin. This causes a malfunction of the BLACKSheep boot loader. If you want to boot the BLACKSheep without an USB cable connected, set the switch SW1 to route the signals to the UART pads as described in the Hardware User Manual of the EVAL-BF5xx Board.
Possible thermal problems on CM-BF561.
- On some CM-BF561 there can be a thermal problem if the core voltage is set to more than 1.3V. ATTENTION: The internal voltage level in the VR_CTL register does not match the effective voltage on the VDDint pin of the BF561. There is a difference of about 80mV. This means that the maximum value for VLEV in the VR_CTL register can be "1101". Older versions of the BLACKSheep software (<0.5.2) ignore this issue. Newer versions can be downloaded from this website in the "Downloads" section.
The getimg command did not recognize the camera-module. What can I do?
- If your EXT-BF5xx-Camera has a version number greather than 1.3 use the -nv switch with the getimg command.
My VisualDSP++ USB-ICE emulator environment has suddenly stopped working with the CM-BF5xx Core Module and EVAL-Board.
- A corrupt flash code can prevent JTAG operation. If have ever flashed your own application onto the module, it is possible that the flash content is corrupted and so the CM-BF5xx Core Module goes in undefined state and you are not able to connect with the JTAG anymore. The only way to get the Core Module working again is to change the bootmode of the Core Module.