10 posts / 0 new
The Last post
Thu, from 2020-06-04
# 1
GGQ_in
Offline
Last seen:7 up 1 week a line
Joined:The 2019-07-23 04:41
SPI FLASH burning questions

Hello, I write in DA14580 and GD25D10C flash burn OTA. Bin file, when burning after the reset bluetooth radio, when I after burning the reset, then the DEBUG secondary boot files only from the run my burning bluetooth program (start) radio, folder is part of secondary lead and flsh_programmer engineering commissioning screenshots.Excuse me this kind of circumstance is secondary boot file burning questions or flsh_programmer engineering problem?

Keywords:
SPI Flash
The secondary boot
Attachment:
PDF iconFlash. PDF
Device:
DA14580
The 2020-06-09 04:18 Tue
CYibin
Offline
Last seen:8 have 3 weekes line
The Staff
Joined:The 2017-12-14 02:48
hello

hello

Would you describe your purpose?

Do burn in 580?Or want to burn 580 FLASH?

The 2020-06-09 06:53 Tue
(Reply to # 2)
GGQ_in
Offline
Last seen:7 up 1 week a line
Joined:The 2019-07-23 04:41
Hello, is want to burn 580 flash

hello

Is think of 580 burn flash

The 2020-06-09 08:54 Tue
(Reply to # 3)
CYibin
Offline
Last seen:8 have 3 weekes line
The Staff
Joined:The 2017-12-14 02:48
hello

hello

About this question, you have a few posts, we focused on the discussion here.

You are using the make image tools that generate multi bin file when encounter problems?

If it is, need to check:

1. FLASH 0 address (including 50 and 70), or in the OTP (does not contain 50 and 70), there are secondary bootloader code

2. 0 x8000 70 51 and image 1

3. 0 x13000 70 51 and image 2

4. 0 x1f000 70 52 header, and 0 x8000 0 x13000 data in the header

580 chip suggest burn in the OTP secondary bootloader

Wed, the 2020-06-10 03:54
(Reply to # 4)
GGQ_in
Offline
Last seen:7 up 1 week a line
Joined:The 2019-07-23 04:41
hello

hello

When I was in generating multi bin file does not appear error.0 x8000 x13000, 0 and 0 x1f000 the three address can read imge and corresponding header information, the DEBUG debugging second_bootloader reading FLASH 0 address card when there seems to have been waiting for, the following code fragment to read while reading FLASH 0.When I use SmartSnippets read at ADDRESS 0 is 50 70 information.

I now have 580 chips and other FLASH chips, spi pins and the default start spi pins are different.Burn in the OTP secondary bootloader code is written into the FLASH zero secondary bootloader?I in multi bin file generated secondary bootloader on address 0 is ok?

Uint8 AN001Header [AN001_SPI_HEADER_SIZE];SpiFlashRead ((unsigned long) AN001Header, (unsigned long) 0, (unsigned long) AN001Header);If (AN001Header [0] = = 0 x70 && AN001Header [1] = = 0 x50) {}

Thank you very much!

Wed, the 2020-06-10 04:55
(Reply to # 5)
CYibin
Offline
Last seen:8 have 3 weekes line
The Staff
Joined:The 2017-12-14 02:48
hello

hello

Yes, at the time of generating multibin, secondary to burn to address 0 FLASH bootloader, 70, 50 after the header

Wed, the 2020-06-10 05:02
(Reply to # 6)
GGQ_in
Offline
Last seen:7 up 1 week a line
Joined:The 2019-07-23 04:41
Hello, I have this step

hello

I have this step

E: \ code \ ota_file > hex2bin - E bin nodata_salve. Hex hex2bin v1.0.10, Copyright (C) 2012 Jacques Pelletier & contributors Lowest address = 00000000 Highest address = 0000732 b Pad Byte = FF 8-bit Checksum = 2 f E: \ code \ ota_file > mkimage single first01_version. H nodata_salve. Bin nodata_salve. Img E: \ code \ ota_file > mkimage multi spi gsecondary_bootloader. Bin nodata_salve. Img 0 x8000 nodata_salve. Img x13000 0 0 x1f000 nodata_salve_ota. Bin Creating image 'nodata_salve_ota. Bin'...[00000000] the AN - B - 001 SPI header [00000008] Bootloader [000012 b0] Padding (FF 's) [00008000]' nodata_salve. Img '[000080 df] Padding (FF' s) [00013000] 'nodata_salve. Img' [000130 df] Padding (FF 's) f000 [0001] the Product the header

Thu, the 2020-06-11 03:01
(Reply to # 7)
CYibin
Offline
Last seen:8 have 3 weekes line
The Staff
Joined:The 2017-12-14 02:48
hello

hello

Sorry I didn't see you before a situation: "different spi flash pin and the default"

In this case, you must modify the secondary bootloader to fit for your flash pin;And need to put the secondary buffer bootloader to your OTP.

Experience on electrical process should be:
1. The chip hardware initialization

2. The chip, the boot ROM to run found that code of OTP (secondary bootloader), copied into RAM to run it

3. Secondary bootloader read product header, obtaining image 1/2 image header address

4. Secondary bootloader decided to copy the image 1, from 1 header image to the image information, such as the image size

Copies the image 1 5. Secondary bootloader to RAM and running

Thu, the 2020-06-11 03:10
(Reply to # 8)
GGQ_in
Offline
Last seen:7 up 1 week a line
Joined:The 2019-07-23 04:41
hello

hello

I have modified the FLASH pin, and the secondary bootloader on FLASH is 0, the secondary bootloader is burn to burn to OTP OTP image?

And I would like to ask, the bluetooth clock crystals pin wiring error will affect the bluetooth radio, such as the broadcast address errors will happen?

Thank you very much!

Mon, the 2020-06-29 05:41
(Reply to # 9)
CYibin
Offline
Last seen:8 have 3 weekes line
The Staff
Joined:The 2017-12-14 02:48
hello

hello

Yes, secondary boot onto/OTP image area.

The broadcast address errors, specific what be to point to?Abnormal crystals to lead to a radio or a connection is not stable