• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 256 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Consequences of removing MSP430 from DM355 design

Gennadiy Kiryukhin
Expert 2800 points

Hi.

My custom board with DM355 does not have the MSP430 chip as compared to the DM355 EVM. The EVM is using the chip to monitor and generate the whole bandwagon of  signals and functions such as SD card insert/WP, IMAGER_RESET, DEEPSLP_EN, buttons, IR remote, DECODER_IMAGER, LEDs, real time clock, NTSC/PAL switch...

When recompiling kernel I can disable some of the features through menuconfig (for example, LEDs).

What files/drivers/things do I need to modify to get a clean removal of the MSP430 chip? BTW, my board is also Ethernetless (i.e. not networking stuff).

Thank you.

  • 0
    TI__Mastermind 41665 points

    Gennadiy Kiryukhin said:
    What files/drivers/things do I need to modify to get a clean removal of the MSP430 chip?

    This can be a bit of a deep topic, and it is not something that TI really provides any collateral for. In general you probably want to do some searching through the kernel sources, in particular in drivers you want to use, to see where the MSP430 code is embedded. An alternative approach would be to look at the kernel build configuration for an alternative DM355 board which lacks this peripheral, such as the Leopard Board.

    As to the code itself, it looks like there is a drivers/mfd/dm355evm_msp.c file which contains the MSP430 access routines, you can search the rest of the kernel for the functions in this c file to see where the MSP430 is being accessed. A few quick searches for dm355evm_msp_read and dm355evm_msp_write in the kernel sources bring up a few files as one might expect based on what the 430 is being used for.

    arch/arm/mach-davinci/board-dm355-evm.c
    drivers/input/misc/dm355evm_keys.c
    drivers/rtc/rtc-dm355evm.c

    There are likely a few other places that were not uncovered by this simple search, but that should at least give you a few places to look to start.

  • 0 in reply to Bernie Thompson TI
    Expert 2800 points

    Thank you. That should give me a few starting points. I tried the LeopardBoard option but the kernel would hand after decompressing. In addition, it looks like the leopard board files (such as arch/arm/mach-davinci/board-dm355-leopart.c) still have some msp430 stuff in them.