Swordfish

Thanks Jerry,
I was not discouraged sorry if it came across that way, i just meant if i ever used a chip in future that it did not work on i would prob dump the bootloader or not use that chip, rather than not hide the keys


Mike

Thanks for the very detailed reply and efforts you have gone to here. I wish I knew what caused the issue but all I managed to establish was that it was definitely the bootloader write or erase with the unlock codes that did the damage. It seems this could only happen with rouge code execution, Of c...

Yeah it was the 4431 that I have used a boat load of but the dspic became the replacement on some boards when redesigned, a lot of them are still using the 4431 as quite a major to change and have been living in hope they would one day release a new QEI 18F. I had not seen that page, thanks, I had c...

Yes had seen the boot block and was planning on putting it in there, but would not write protect it anyway, my old one had it in low memory My bootloader is really just comms and then read, write, erase, instructions. Its all controlled by the PC and just blocks of address and values are sent from t...

Yes it did work, this code was from an old bootloader in a 1220, yeah I realise that the =0 was not doing anything I just never got around to taking it out, I thought you might comment on that when I saw it there when I posted it :) I’m not sure if it will work on the 41 as I have not got that far y...

// erase ROM block... Public Sub EraseBlock (pAddress As TABLEPTR, pEECON1 As Byte, pEECON2 As Byte, pEECON2a As Byte) 'EECON1 = $94 'EECON2 = $55 'EECON2 = $AA EECON1 = pEECON1 EECON2 = pEECON2 EECON2 = pEECON2a WR = 1 Delay WREN = 0 pEECON1 = 0 pEECON2 = 0 pEECON2a = 0 End Sub I did it like this,...

Thanks Jerry, I’m just looking at the normal read, write erase for the Q41 series I’ll prob put the unlock codes into variables that I’ll send down from the PC in a message before doing the Erase and writes and then I’ll clear them out when I’m done bootloading before reset, as I have had issues in ...

Hi All, I'm looking at updating a bootloader and before i get to far into it i wanted to see if there is an updated memoryAccess module to suit the newer IC's Im using the PIC18F15Q41 I'm surprised this is not part of the core modules. as i would think a lot of people would have a use to access prog...

Awesome, Thanks Jerry for this and everything you do for swordfish you’re a legend. I have been doing more research. I can see how the mistake was made as MAPS actually seems to be wrong and lists it as having 3 UARTs and page 1 of the datasheet lists it as having 3/2 as UART/UART with protocol supp...

I have got a board im putting together and need a boat load of USARTS, I selected the PIC18F47Q84 as it has 5 :) Im am starting to write my program and get an error due to the following line in 18f47q84.bas #const _usart = $03 // 3 USART(s) available the error says "18f47q84 does not support USART4"...

Awesome, thanks i have been away from SF for a while but have a few projects im going to do on it and might even get this one going

Thanks for the reply, Yes that's what i was hoping to do, just get the bits in a byte set instead of IO pins and then my program could deal with sending that byte out to the I2C every time it changed. Ill see what i can come up with, maybe an I2CLCD.Bas module as you suggest, as the backpack for the...

Did anyone get this going? Im trying to do the same thing but i cannot see how this links the LCD module to the I2C bits or in fact how to do that, Do i have to start from scratch or is there a way to get the bits out of the existing LCD module and just poke them out I2C? Thanks for any assistance, ...

This saved my neck.. I had been messing around with the port D pullups on a PIC18F4550 and it has this same issue as the bit is in the Port E Reg. After hours of stuffing around with it i found your fix on here and set ASM BSF PORTe,7,0 'this sets port D pullups on as setting PortE.7=1 does not work...

Thanks Jerry,
That little + cost me hours of time to work around last year and now i understand why it was all not working correctly...

Regards,

Mike