Pavel Pisa commented: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5537#note_147968


I have updated old TSM570 utils repository used at initial BSP development

https://github.com/AoLaD/rtems-tms570-utils

The new OpenOCD configuration for TMS570LC4357 is added

`openocd/openocd-tms570lc43xx-intram.cfg`

It works with mainline OpenOCD and should not require any preprogrammed content 
in Flash if the POM is modified to overlay whole 128 bytes at start of Flash 
(on address 0) and hardware initialization is included in 
`tms570lc4357_hdk_intram` BSP.

The original TMS570LS3137 configuration has been renamed to

`openocd/openocd-tms570ls3137-sdram.cfg`

This one resets board and allows code from Flash to initialize chip (one second 
is left for Flash code to initialize). The POM overlay from Flash start has 
been unreliable on TMS570LS3137 so initialization code and some instructions 
for branch over vectors in POM at address starting from 0x40 are required.

The RTEMS CAN/CAN FD framework has been tested to run on the TMS570 with 
virtual controller setup.

`rtems_can_test/init.c`

needs modification to not attempt to probe CTU CAN FD or SJA1000 on the 
addresses causing the fault

```
  char *argv_reg[3] = {"can_register", "-t", "virtual"};
  can_register( 3, argv_reg );

  char *argv_set[3] = {"can_set_test_dev", "dev/can0", "dev/can0"};
  can_set_test_dev( 3, argv_set );

```

Then everything seems to work as expected. The shortcuts to build and run 
examples on TMS570 has been added to the CAN development repository, see

- 
[targets/tms570ls3137_hdk_sdram](https://gitlab.fel.cvut.cz/otrees/rtems/rtems-canfd/-/tree/master/targets/tms570ls3137_hdk_sdram)
- 
[targets/tms570lc4357_hdk_intram](https://gitlab.fel.cvut.cz/otrees/rtems/rtems-canfd/-/tree/master/targets/tms570lc4357_hdk_intram)

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5537#note_147968
You're receiving this email because of your account on gitlab.rtems.org.


_______________________________________________
bugs mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/bugs

Reply via email to