Author Topic: Customized bootloader for flash ROM Winbond: W25Q16JLSNIG-T with LPC1833  (Read 1118 times)

Andy Ayre

  • ESAcademy Staff
  • Sr. Member
  • *****
  • Posts: 2190
    • View Profile
    • Embedded Systems Academy, Inc.
    • Email
Re: Customized bootloader for flash ROM Winbond: W25Q16JLSNIG-T with LPC1833
« Reply #30 on: August 16, 2021, 10:16:04 am »
You don't program the hex file into flash - it is downloaded to RAM automatically.

It looks from the debug file that you are choosing the LPC1833 rather than your external flash bootloader. In section 1:

Click on Change
Expand External Memory (third item)
Expand UART
Choose your custom bootloader

If you don't see your bootloader then copy it into the Bootloaders\External Memory folder.
Embedded Systems Academy, Inc.
support at esacademy dot com

sonam chouhan

  • Jr. Member
  • **
  • Posts: 10
    • View Profile
Re: Customized bootloader for flash ROM Winbond: W25Q16JLSNIG-T with LPC1833
« Reply #31 on: August 25, 2021, 12:16:30 am »
Thanks for your kind support.

With a correct RAM address mapping, my customized BL is working fine for the Winbond flash ROM.

Quick concern: If a flash ROM having almost the same features as the supported QSPI device for LPC1833, then would the same customized BL work for the similar featured flash ROM?

Or there is any specific change required in the sample code?

Andy Ayre

  • ESAcademy Staff
  • Sr. Member
  • *****
  • Posts: 2190
    • View Profile
    • Embedded Systems Academy, Inc.
    • Email
Re: Customized bootloader for flash ROM Winbond: W25Q16JLSNIG-T with LPC1833
« Reply #32 on: August 25, 2021, 09:24:45 am »
It would be best to compare the datasheets of the two devices and look for differences. Andy
Embedded Systems Academy, Inc.
support at esacademy dot com

sonam chouhan

  • Jr. Member
  • **
  • Posts: 10
    • View Profile
Re: Customized bootloader for flash ROM Winbond: W25Q16JLSNIG-T with LPC1833
« Reply #33 on: August 29, 2021, 10:27:52 pm »
I have gone through both MX25L1633E and MX25R6435F but did not find any software-related difference. My customized bootloader code runs in MX25L1633E successfully but failed in MX25R6435F.

By debugging the code, I found that the operation failed from the initial stage Memory_init(). In our MCUxpresso code, we observed the same failure. Can it be the spifi_drv_M3.lib issue?

FYI, we are able to flash the image via JTAG in MX25R6435F.

sonam chouhan

  • Jr. Member
  • **
  • Posts: 10
    • View Profile
Re: Customized bootloader for flash ROM Winbond: W25Q16JLSNIG-T with LPC1833
« Reply #34 on: September 29, 2021, 01:57:33 am »
Could you let us know the below information about spifi_drv_M3.lib?

1. In the flash magic example code, this lib is directly used for the support of spi flash, so, is the library created from .a (NXP) or it is created in KEIL by using source code?

2. Do you have any source code to create .lib?

3. We got the source code for this from NXP, but by building the project in KEIL, .lib size is different and that does not work?

Currently, we need to add the support of an flash of MXIC which is not supported by the old spifi lib, so we are working to add the support of the flash in spilib source ccode and by doing so, we need to create the customized bootloader for the flash MX25V16xx.