Part Number: DLPC3479
Hello TI Pico team,
I have got a question about the DLPC3479 firmware update from GUI tool.
Would you please answer this question?
We would like to know how two SPI flashes (of DLPC3479 Master/Slave) are updated by the GUI software.
I think “Update Firmware” command of GUI software is updating both SPI flashes through SPI interface of Cypress USB chip (not through DLPC3479/I2C). But we do not know how it is working because the source code of GUI software is not disclosed.
On the other hand, there is a code in the MSP430 software that is controlling flash master and flash slave by using P3.2 and P3.3 of MSP430.
But it looks like these pins are not connected to the DLPC3479 or SPI flash in the EVM. So, is this correct that these signals and code are not used?
So, it would be helpful if you can tell us how the GUI software is updating complete firmware for both two SPI Flashes.
For example, is the firmware updated simultaneously or in a sequential order (Maser -> Slave). Is the same contents (.img file) to be loaded to both flashes or not? and etc…
Our customer is considering to make their own board by referring to your EVM. They are not planning the host application processor but using FPGA on behalf of MSP430 and want to connect PC (GUI software) through Cypress USB chip. That is why they are asking this question.
Welcome back to the forum!
Let me look into the DLPC3479 flash process and get back to you soon.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
Here is are my findings regarding your questions:
1. Is the firmware updated simultaneously or in a sequential order (Maser -> Slave)?
The firmware is programmed sequentially, master first, then slave.
2. Is the same contents (.img file) to be loaded to both flashes or not?
The image file to be flashed is identical between master and slave.
Additionally, these are the steps suggested for programming Dual ASIC DLPC3479:
o Program the Master controller first by setting GPIO7 to true and GPIO8 to false
o Program the Master controller’s flash by sending Flash commands
o Once that is done; set GPIO8 to true and then GPIO14 to false to program the Slave controller
o Once that is done; then set GPIO7 to false, GPIO8 to true, and GPIO14 to true
Please let us know if you have any further question, and thank you for using the E2E forum.
In reply to Austin Snyder:
Thank you for the answer. I could understand how to update the firmware.
Please let me ask some additional questions below.
- Regarding the steps you suggested, I would like to make clear.
1. It looks P3.2 and P3.3 of MSP430 are not used for this steps. Is this understanding correct?
2. GPIO8 and GPIO14 pins are in CY7C652 and these signals are USB_SPI_M_OEZ and USB_SPI_S_OEZ written in the EVM schematics.
The user should control these signals from the host control software. Is this understanding correct?
Our customer is designing their own custom board and want to use the GUI software. In this case, can GUI software control these GPIO8 and GPIO14 signals?
- Regarding the firmware file, you answered the flashed images are identical for Master and Slave but the original firmware file is one .img file.
3. Would you please tell us how two identical images can be generated from one *.img file and stored to each SPI flashes?
If they use the GUI software on their own board and use update firmware command, do not they care about this ?
Thank you for your comment.
In reply to Nobuyoshi Arai44:
You are very welcome for the answers.
To answer your recent questions:
Correct. These pins are not used by the EVM.
The GUI controls the GPIO's of the Cypress chip. If the customer is not using the Cypress chip the GUI will not work. If they are using the same Cypress chip on their design, they only have to configure the chip correctly and use the GUI.
The GUI will update one flash (the master) and then the other (the slave) sequentially. When firmware is updated, the GUI uploads both automatically.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.