Dirk,
If there is a BootRom/RBL similiar to DM644x in DM355, there is no
compatible "DVFlasher" tool from TI available for this??
The RBL is almost identical I assume. Last time I heard of there is
not yet a DVFlasher tool from TI (but I assume they have it since is
not difficult to modify it for Davinci).
If magic signature of DM355 is different to DM644x I understand that
our DM644x open source UBL tools
http://wiki.davincidsp.com/index.php?title=RBL_UBL_and_host_program
will not work. But I would strongly assume that TI has a compatible
"DVFlasher" tool (?).
Btw.: Any pointers to this "different magic signature"? Would it be
a big task to add it to our open source RBL/UBL tooling?
Sorry I got confused with the difference, is not about the magic
signature that is identical (I was recalling comparing the DM355 magic
signature from some other non-catalog parts of TI), the main
difference is that the DM355 RBL uses a 4-bit ECC mode in the OOB data
that is not present on the DM6466 (which uses 1-bit ECC).
If you check the section 11 of the DM355 ARM Subsystem Guide
(spruee8a_22.pdf) you can find some other minor differences (for
example DM355 can search for the UBL up to 24 blocks instead of 5 on
the DM6446).
You can improve the open source tools with those changes, the RidgeRun
bootloader (rrload) has support for writing the 4bit ECC UBL used by
the DM355, but also I recall some TI examples have code to perform
4bit ECC operations.
Do you talk about
http://openhardware.net/Embedded_ARM/OpenOCD_JTAG/
for DM355?
Any hints how to use this? Would be nice if we add it to wiki ;)
Yes, we use it with a FT2232 based Olimex dongle.
The DM355 EVM has a standard ARM 20-pin connector and you can plug any
standard ARM JTAG if you configure the scan chain properly:
- Set the EMU0 and EMU1 pins to Low. This will put the SoC on the
following configuration:
IcePick (IRLen 6) - ARM (IRLen 6) - ETB (IRLen 4)
- Run the openocd with the configuration script (see below):
openocd -f dm355.cfg
Now you can telnet to the OpenOCD session or attach it to gdb as
documented on the OpenOCD project.
Diego Dompe
RidgeRun Engineering
==================== DM355.cfg ==================================
gdb_port 3333
telnet_port 4444
#interface
interface ft2232
ft2232_layout "olimex-jtag"
ft2232_vid_pid 0x15ba 0x0003
ft2232_device_desc "Olimex OpenOCD JTAG"
#target hardware notes:
#
#TI DM355 EVM: set EMU0 L and EMU1 L
#use combined on interfaces or targets that can't set TRST/SRST
separately
reset_config trst_and_srst
#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0x0 0x0
jtag_device 4 0x1 0x0 0xe
jtag_device 6 0x1 0x0 0x0
#target <type> <endianness> <reset mode> <chainpos> <variant>
target arm926ejs little reset_halt 1 arm926ejs
run_and_halt_time 0 30
# setup data portion of tightly coupled (internal) memory
# for open OCD working area
working_area 0 0x10000 0x8000 nobackup
# newer openocd allow you to include commands in config file
arm7_9 fast_memory_access enable
arm7_9 dcc_downloads enable
arm7_9 force_hw_bkpts enable
gdb_memory_map enable
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
