Dear Infineon,
I have 2 SPI devices on my XMC4500 SPI bus with very different configurations so I have been trying to use the SPI001_Configure() function. However I have found the following problems with the function...
1) The SPI001_Configure() function code is very differently to the SPI001_Init() function code contained in the DAVE_Init() function. This makes no sense.
2) The SPI001_Configure() function cannot be used to change some settings which are set in the DAVE configuration tabs for the App. e.g. TX & RX FIFO sizes
3) The SPI001_Configure() function incorrectly sets the IOCR0 and HWSEL registers
4) The SPI001_Configure() function sets reserved bits in some registers
5) The SPI001_Configure() function sets bits that have no effect in some registers
6) The SPI001_Configure() function changes port pin configurations that are un-related to SPI
7) The SPI001_Configure() function does not flush the TX or RX FIFO's
I have written my own code to reliably switch between the 2 SPI configurations. The above problems and endless crashing of the Tasking debug environment have caused a 2 week delay to a critical project.
My questions are...
1) Are you committed to providing bug fixes for DAVE3 ? (I cannot migrate to DAVE 4 on existing products as this would require complete re-validation)
2) Are DAVE3 bugs fixed in DAVE 4 ?
3) Is DAVE4 a big improvement over DAVE3 ? The xmc4500 is a fantastic device let down by DAVE. For this reason I must consider moving to another manufacturer.
4) Is the Tasking debug environment improved with DAVE 4 ?
Thank you very much
Best regards
Aaron
Product Consultant
I have 2 SPI devices on my XMC4500 SPI bus with very different configurations so I have been trying to use the SPI001_Configure() function. However I have found the following problems with the function...
1) The SPI001_Configure() function code is very differently to the SPI001_Init() function code contained in the DAVE_Init() function. This makes no sense.
2) The SPI001_Configure() function cannot be used to change some settings which are set in the DAVE configuration tabs for the App. e.g. TX & RX FIFO sizes
3) The SPI001_Configure() function incorrectly sets the IOCR0 and HWSEL registers
4) The SPI001_Configure() function sets reserved bits in some registers
5) The SPI001_Configure() function sets bits that have no effect in some registers
6) The SPI001_Configure() function changes port pin configurations that are un-related to SPI
7) The SPI001_Configure() function does not flush the TX or RX FIFO's
I have written my own code to reliably switch between the 2 SPI configurations. The above problems and endless crashing of the Tasking debug environment have caused a 2 week delay to a critical project.
My questions are...
1) Are you committed to providing bug fixes for DAVE3 ? (I cannot migrate to DAVE 4 on existing products as this would require complete re-validation)
2) Are DAVE3 bugs fixed in DAVE 4 ?
3) Is DAVE4 a big improvement over DAVE3 ? The xmc4500 is a fantastic device let down by DAVE. For this reason I must consider moving to another manufacturer.
4) Is the Tasking debug environment improved with DAVE 4 ?
Thank you very much
Best regards
Aaron
Product Consultant