Re: Three chip erc32 Re: CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER macro issue

2019-09-21 Thread Chris Johns
On 21/9/19 8:34 am, Michel Macena wrote: > Sorry for the late response, but the board is with hardware issues wich caused > the strange behavior. I'm using another board with a single chip ERC32. Many thanks for let us all know. Chris ___ users mailing

Re: Three chip erc32 Re: CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER macro issue

2019-09-20 Thread Michel Macena
Sorry for the late response, but the board is with hardware issues wich caused the strange behavior. I'm using another board with a single chip ERC32. Thanks for the help. Em ter, 3 de set de 2019 às 17:08, Jiri Gaisler escreveu: > > On 9/3/19 9:14 AM, Jiri Gaisler wrote: > > Hmm, maybe clock d

Re: Three chip erc32 Re: CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER macro issue

2019-09-03 Thread Jiri Gaisler
On 9/3/19 9:14 AM, Jiri Gaisler wrote: > > Hmm, maybe clock driver code has been changed during the years to read > or write some register bits that are illegal on the 3-chip ERC32. This > would cause a trap to error mode and most likely a watchdog reset. I > quickly looked through the ERC32 clock

Re: Three chip erc32 Re: CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER macro issue

2019-09-03 Thread Jiri Gaisler
Hmm, maybe clock driver code has been changed during the years to read or write some register bits that are illegal on the 3-chip ERC32. This would cause a trap to error mode and most likely a watchdog reset. I quickly looked through the ERC32 clock driver code but could not see anything obvious. I

Three chip erc32 Re: CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER macro issue

2019-09-02 Thread Joel Sherrill
Jiri does this ring a bell with the old Tharsys board and 3 chip erc32? On Mon, Sep 2, 2019, 5:09 PM Michel Macena wrote: > It is the ERC 32 chipset version (TSC691, TSC692 and TSC693 units), The > Board was manufactured by Tharsys, a french company, but it does not > exist anymore. The board ma