Read/write EEPROM on DCT2224?

[usbbdm]

Does anyone know if there is value to read/write EEPROM on those boxes? If you make mistake, however, you can make the box not working any more.

I am thinking add EEPROM read/write API so in the future if we ever want to read/write EEPROM, no more need to release new software but a small binary file will be used (similar to the idea of dll).

The current software structure has to come up with some patches to the software that allows to program the EEPROM.

[CAPONE]

Does anyone know if there is value to read/write EEPROM on those boxes? If you make mistake, however, you can make the box not working any more. I am thinking add EEPROM read/write API so in the future if we ever want to read/write EEPROM, no more need to release new software but a small binary file will be used (similar to the idea of dll).

The current software structure has to come up with some patches to the software that allows to program the EEPROM.

So your Saying the Currect way is Safer, Then Why Ruin a Good thing.
As It is Now People Brick there Boxes, Mostly due to Not reading Instructuions.

That may be something Worth doing Like for Advanced Users, IMHO.

If you make it to where they can brick box beyond Repair, I bet that would be Happening ALOT.

[usbbdm]

Reading/writing EEPROM is the same as reading/wring flash. Current we do not have expose to how to write to EEPROM. The EEPROM data of the flash is copied somewhere in NVRAM already.
The EEPROM holds the configuration of the box. (Like if it has the modem 2244). Maybe tuner as well.

[CAPONE]

Reading/writing EEPROM is the same as reading/wring flash. Current we do not have expose to how to write to EEPROM. The EEPROM data of the flash is copied somewhere in NVRAM already.
The EEPROM holds the configuration of the box. (Like if it has the modem 2244). Maybe tuner as well.

I beleive Its a GOOD Idea, My Concern is for Newbies Killing there Boxes beyond Repair.
However, If they don't take the time to read before testing they Deserve to Kill there Targets. LOL

I Sure would Love to Have that Feature Available for TESTING.

[usbbdm]

I have also made changes to the software for target selection.
I have many people complain when receive the BDM NT and forget to select DCT2224 or DSR and shows hardware not compatible.
The changes are (complete already will be in next release).
1. If the USBBDM NT or JTAG NT is plugged in, then only compatible target can be selected. eg. If yuo plug USB BDM NT, DCT700 will not be available to select.
2. If incompatible hardware is found, the configuration will popup allowing making the right selection.
3. Add protocol selection. Eg. You can select SPI flash and all the target will be shown regardless of its family.

Since the supporting device is growing fast and it becomes more difficult to select the target, hope this change will make things simpler. Most of the user only needs one or two target anyway. For those use, they can even delete the xmls under config directory that they do not use.

[CAPONE]

I have also made changes to the software for target selection.
I have many people complain when receive the BDM NT and forget to select DCT2224 or DSR and shows hardware not compatible.
The changes are (complete already will be in next release).
1. If the USBBDM NT or JTAG NT is plugged in, then only compatible target can be selected. eg. If yuo plug USB BDM NT, DCT700 will not be available to select.
2. If incompatible hardware is found, the configuration will popup allowing making the right selection.
3. Add protocol selection. Eg. You can select SPI flash and all the target will be shown regardless of its family.

Since the supporting device is growing fast and it becomes more difficult to select the target, hope this change will make things simpler. Most of the user only needs one or two target anyway. For those use, they can even delete the xmls under config directory that they do not use.

That sounds Great.
Now on the EEPROM Thing, Is that onlly for USBBDM NT Or can it be done for The USBJTAG NT Targets Aswell?

[usbbdm]

The same API will be for both BDM NT and JTAG NT.

Current the EEPROM read/write is built in software. Like Sonicview 360, there is EEPROM read/write. So do Nano2. The XV3300 does not have the EEPROM read/write yet. Once the API is ready, then XV3300 just need a small external file will do the read/write.

[CAPONE]

The same API will be for both BDM NT and JTAG NT.

Current the EEPROM read/write is built in software. Like Sonicview 360, there is EEPROM read/write. So do Nano2. The XV3300 does not have the EEPROM read/write yet. Once the API is ready, then XV3300 just need a small external file will do the read/write.

COOL So that will be available in Next Software Release?

This testing Stuff Gets better Every Day.

[hqa18]

usando traductor:

the question is whether being able to copy and modify the eprom of the dct to clone it to a DCT in this way to make a nearly complete copy of the box because if the eprom contain the settings of the box means that there would not only copy if you do not edit or modify it to the other box

[hqa18]

Reading the EEPROM Data Memory

To read a data memory location, the user must write the address to the EEADR register and then set control bit RD (EECON1<0>). The data is available, in the very next instruction cycle, in the EEDATA register; therefore it can be read by the next instruction. EEDATA will hold this value until another read or until it is written to by the user (during a write operation).

Example Data EEPROM Read

BCF STATUS, RP0 ; Bank0
MOVLW CONFIG_ADDR ; Any location in Data EEPROM memory space
MOVWF EEADR ; Address to read
BSF STATUS, RP0 ; Bank1
BSF EECON1, RD ; EE Read
BCF STATUS, RP0 ; Bank0
MOVF EEDATA, W ; W = EEDATA

Writing to the EEPROM Data Memor

To write an EEPROM data location, the user must first write the address to the EEADR register and the data to the EEDATA register. Then the user must follow a specific sequence to initiate the write for each byte.

Example Data EEPROM Write

BSF STATUS, RP0 ; Bank1
BCF INTCON, GIE ; Disable INTs.
BSF EECON1, WREN ; Enable Write
Required
Sequence
MOVLW 55h ;
MOVWF EECON2 ; 55h must be written to EECON2
MOVLW AAh ; to start write sequence
MOVWF EECON2 ; Write AAh
BSF EECON1,WR ; Set WR bit begin write
BSF INTCON, GIE ; Enable INTs.

The write will not initiate if the above sequence is not exactly followed (write 55h to EECON2,write AAh to EECON2, then set WR bit) for each byte. We strongly recommend that interrupts be disabled during this code segment.
Additionally, the WREN bit in EECON1 must be set to enable write. This mechanism prevents
accidental writes to data EEPROM due to errant (unexpected) code execution (i.e., lost programs).
The user should keep the WREN bit clear at all times, except when updating EEPROM.
The WREN bit is not cleared by hardware
After a write sequence has been initiated, clearing the WREN bit will not affect this write cycle.
The WR bit will be inhibited from being set unless the WREN bit is set.
At the completion of the write cycle, the WR bit is cleared in hardware and the EE Write Complete Interrupt Flag bit (EEIF) is set. The user can either enable this interrupt or poll this bit. EEIF must be cleared by software.

[Pichardo]

Reading the EEPROM Data Memory

To read a data memory location, the user must write the address to the EEADR register and then set control bit RD (EECON1<0>). The data is available, in the very next instruction cycle, in the EEDATA register; therefore it can be read by the next instruction. EEDATA will hold this value until another read or until it is written to by the user (during a write operation).

Example Data EEPROM Read

BCF STATUS, RP0 ; Bank0
MOVLW CONFIG_ADDR ; Any location in Data EEPROM memory space
MOVWF EEADR ; Address to read
BSF STATUS, RP0 ; Bank1
BSF EECON1, RD ; EE Read
BCF STATUS, RP0 ; Bank0
MOVF EEDATA, W ; W = EEDATA

Writing to the EEPROM Data Memor

To write an EEPROM data location, the user must first write the address to the EEADR register and the data to the EEDATA register. Then the user must follow a specific sequence to initiate the write for each byte.

Example Data EEPROM Write

BSF STATUS, RP0 ; Bank1
BCF INTCON, GIE ; Disable INTs.
BSF EECON1, WREN ; Enable Write
Required
Sequence
MOVLW 55h ;
MOVWF EECON2 ; 55h must be written to EECON2
MOVLW AAh ; to start write sequence
MOVWF EECON2 ; Write AAh
BSF EECON1,WR ; Set WR bit begin write
BSF INTCON, GIE ; Enable INTs.

The write will not initiate if the above sequence is not exactly followed (write 55h to EECON2,write AAh to EECON2, then set WR bit) for each byte. We strongly recommend that interrupts be disabled during this code segment.
Additionally, the WREN bit in EECON1 must be set to enable write. This mechanism prevents
accidental writes to data EEPROM due to errant (unexpected) code execution (i.e., lost programs).
The user should keep the WREN bit clear at all times, except when updating EEPROM.
The WREN bit is not cleared by hardware
After a write sequence has been initiated, clearing the WREN bit will not affect this write cycle.
The WR bit will be inhibited from being set unless the WREN bit is set.
At the completion of the write cycle, the WR bit is cleared in hardware and the EE Write Complete Interrupt Flag bit (EEIF) is set. The user can either enable this interrupt or poll this bit. EEIF must be cleared by software.

This is into the DCT2224 ???

This instruccion is MIPS32 ???

Keep Trying . . . !

[hqa18]

the info from the eeprom is a generic operation in general but if 2224 is applicable to the understanding we'll get started according to this in the EEPROM memory in the special cable boxes even when it works so well is the same in some fta.

[RIP_Felipeferras]

That sounds Great.
Now on the EEPROM Thing, Is that onlly for USBBDM NT Or can it be done for The USBJTAG NT Targets Aswell?

[hqa18]

that's the thing to get started now to help bdm to work for the nt

[Rob0108]

The same API will be for both BDM NT and JTAG NT.

Current the EEPROM read/write is built in software. Like Sonicview 360, there is EEPROM read/write. So do Nano2. The XV3300 does not have the EEPROM read/write yet. Once the API is ready, then XV3300 just need a small external file will do the read/write.

That's great news,
the more test options that we have the better