Reprogramming could not be done because of a previous sequence error

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
8 posts / 0 new
Last post
lottabull
Offline
Last seen: 1 year 6 months ago
Joined: 2018-03-02 21:01
Reprogramming could not be done because of a previous sequence error

SLG4DVKISP programmed the chip successfully.
Chip worked as programmed.
Modified the project slightly and Program, produces a popup labeled Programming error, containing "Reprogramming could not be done because of a previous sequence error."

Where are descriptions and remedies for error messages like this?
When there's a programming error, is there a way to reset the chip and start over?

Device: 
Device Number: 
SLG46826
craigee0212
Offline
Last seen: 1 year 5 months ago
Staff
Joined: 2016-09-02 20:58
Hello Iottabull,

Hello Iottabull,

We've reached out to our software team to request information regarding that specific error message, but we won't be able to determine if the chip can be reset until we know more about the source of the error.

While I wait to hear back from them, would you be willing to attach both the original design file along with the new design file to this forum question? If you don't have the original design file on hand, you might be able to read the current NVM stored in the GreenPAK by following the steps shown below.

- Open the "Debug" control window.
- Perform a device read by pressing "Read"
- The software should ask you if you'd like to load the IC's NVM into a new GreenPAK Designer project.

Thanks,
Craig

lottabull
Offline
Last seen: 1 year 6 months ago
Joined: 2018-03-02 21:01
v2 is the earlier and v3 is

v2 is the earlier and v3 is the later.
Additional chips have in-system programmed successfully with the v3 design and function as programmed.

lottabull
Offline
Last seen: 1 year 6 months ago
Joined: 2018-03-02 21:01
Reading the problem chip

Reading the problem chip seems to succeed, but the resulting design doesn't look anything like that produced by reading a correctly-programmed chip.

craigee0212
Offline
Last seen: 1 year 5 months ago
Staff
Joined: 2016-09-02 20:58
Thanks for sending out those

Thanks for sending out those attachments. I'd like to verify the silicon revision that you are using. Can you post the PN: ## and the DB HW-FW: ## located at the bottom of the Debug window in the GreenPAK designer?

lottabull
Offline
Last seen: 1 year 6 months ago
Joined: 2018-03-02 21:01
Here is the content of the

Here is the content of the System Information button
Chip:
P/N: SLG46826V/G
Revision: 0x1
Pattern ID: 1
Date code: N/D
Lot number: N/D

Development Board:
Type: In-System Programmer
Hardware ID: 1.0
Firmware ID: 1.0

GreenPAK Designer:
Application name: GreenPAK6 Designer
Version: 6.14
Build: 001

Operating System:
Name: Windows 10
Version: 64-bit

craigee0212
Offline
Last seen: 1 year 5 months ago
Staff
Joined: 2016-09-02 20:58
The "Read_from_problem_chip"

The "Read_from_problem_chip" GreenPAK file that you attached tells me a couple things:

  • The NVM has been mostly filled with 1's. This behavior is consistent with I2C behavior that we've observed when sending unsupported I2C commands to our NVM address space. When a write command follows the proper command structure, the write operation will program the SLG46826 correctly. We've fixed this behavior in the next revision of the silicon which will be available in the coming weeks.
  • - Please reference Issue 4 in the attached Errata file for more information. SLG46826 revision YC corresponds to revision 0x1 shown in the GreenPAK designer software.

  • Due to the previously described behavior, the NVM protection registers (NPR) have been configured to lock I2C reads and writes from the NVM registers. Therefore, you won't be able to rewrite the NVM registers for this chip.
  • - This is likely the "previous sequence error" that the GreenPAK designer is generating.
    - NPR I2C Address: 0xE1

If my understanding is correct, you used our software to program the SLG46826. This is a bit surprising; but we'll investigate the GreenPAK's source code to verify the programmer's behavior.

lottabull
Offline
Last seen: 1 year 6 months ago
Joined: 2018-03-02 21:01
It may be that one of the

It may be that one of the four jumper leads slipped off during programming. Could easily cause a data under-run.
To prevent that in the future I made an adapter board that connects the ISP board securely to our board.
The chip is on the bottom of the board in J1.

Can the problem chip be reprogrammed in the Universal Dev. board 1 instead of in-system?
If i2c is part of the problem, maybe bypassing i2c would help.
It would need a different socket board than the one we used with the 46538

Attachment: