Search found 24 matches

My ignorance will show here, but aren't fuses located outside of the "usable memory" range?

0x00000 - RESET (GOTO 0x26800)
0x00004 - IVT
0x00104 - AIVT
0x00400 - APP GOTO
0x00404 - AP ...

Great example, thank you! Aside from the jump_to_isr() approach, the code I'm working with is similar, and uses ALTIVT for the bootloader and IVT for application.

However, I can clean up the organi ...

I think I found the answer! I have the whole byte address (hex file) and word address (flash memory) concepts clear in my head. What I didn't understand is why the PIC-C redirected IVT was different t ...

Hello all, I'm hoping someone here can clarify this behaviour for me. It seems to be something compiler-specific that I can't find other reports of.

Note, this is inherited code, so when I call out ...

@dluu13 - great points. The +=1 notation more clearly shows intended behaviour, so I used that and it works correctly.

Count[ID] += 1; // This works

@Ttelmah - I had a feeling you would ...

Before I get started, this post is mostly to have a record on the internet for others with similar issues since I couldn't find anything else like it.

PIC-C Version 4.106 (very old)

Problem

I ...

Great idea!

The initial setup is the same (no surprise):

// V4.106
//write_program_memory(_romw_curr_page, _romw_buffer, sizeof(_romw_buffer)); //write modified block
284 ...

I agree, and I wish we had transparency into that particular function.

My primary goal was to reduce instances of the Device ID becoming corrupt upon the very first upgrade. Of the 5 units tested w ...

Verdict

After a race to the death with two brand new ICs, my original hypothesis doesn't hold up:

Hypothesis: along with using rom_modify(), I need to port my code from V4.106 compiler to V5.044 ...

@Ttelmah - this is true, good point. However, wouldn't failure only occur in the blocks being erase/written? Even after 1000 cycles, the device ID block shouldn't become corrupted right?

Compiler V ...

It's not quite resolved!

The firmware was originally programmed with V4.106.

I ported the BIOS to V5.044 fine, but the firmware had a bunch of bugs with the newer compiler.

The test last nigh ...

Good news - I think I solved it.

rom_write.c

I discovered the rom_write library in Compiler V5.044 - it wasn't in V4.106.

This library includes the rom_modify() function. This function handle ...

Update

Erase loop does not seem to be the problem

* Commented out the erase loop: Corruption still occurs

* Page-aligned the erase: Corruption still occurs

void BIOS_Erase_CPU_Flash_FMWR ...

@dexta64 - actually I don't want it to touch the bootloader - this should be protected (recovery mode).

I'm still reworking this code - basically I want to buffer a whole page then write in one sho ...

Understood, both of you Smile

I didn't write this code, just inherited it, and your help dissecting it is huge.

Data Length Packing

ROW = 192 bytes = 64 instructions
PAGE = 1536 bytes = 512 instru ...