Working java program throws I2C exception when running on new Pi

[cbear3000]

I have some java code that I've been running for some years now that uses mcp23017 port expander, and the raspberry pi 4 I was using stopped booting recently, so I moved the memory card to a new pi 4 and it boots ok.

However when I run the code I always get this exception:

_Exception in thread "main" java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:61)
Caused by: java.io.IOException: Remote I/O error
        at java.io.RandomAccessFile.write0(Native Method)
        at java.io.RandomAccessFile.write(RandomAccessFile.java:489)
        at java.io.RandomAccessFile.writeByte(RandomAccessFile.java:991)
        at com.pi4j.io.i2c.impl.I2CBusImpl.lambda$readByte$2(I2CBusImpl.java:154)
        at com.pi4j.io.i2c.impl.I2CBusImpl.runBusLockedDeviceAction(I2CBusImpl.java:260)
        at com.pi4j.io.i2c.impl.I2CBusImpl.readByte(I2CBusImpl.java:153)
        at com.pi4j.io.i2c.impl.I2CDeviceImpl.read(I2CDeviceImpl.java:205)
        at com.pi4j.gpio.extension.mcp.MCP23017GpioProvider.<init>(MCP23017GpioProvider.java:129)
        at com.pi4j.gpio.extension.mcp.MCP23017GpioProvider.<init>(MCP23017GpioProvider.java:113)
        at com.pi4j.gpio.extension.mcp.MCP23017GpioProvider.<init>(MCP23017GpioProvider.java:108)
        at WHR.AutoSig.main(AutoSig.java:112)_

This is the second time I've had to move to a new Pi after it had failed, last time a couple of years back I did have to run the below code to get the script running again, but now it makes no difference on this new pi 4. New pi is using the same java version as the old ones (I did try updating the java version to 11 but no difference.)

  sudo apt-get remove wiringpi -y
  sudo apt-get --yes install git-core gcc make
  cd ~
  git clone https://github.com/WiringPi/WiringPi --branch master --single-branch wiringpi
  cd ~/wiringpi
  sudo ./build_

I have replaced the two mcp23017 chips in case they also had failed but that also makes no difference. The new Pi is still a Pi4, but I wondered if something has changed in the new boards that means this mcp23017 functionality will no longer work? I did wonder if I needed to downgrade pi4j back to v1 for this to work, however I can't see anything that suggests the user is able to revert to an older version, the install command just gives you the latest version.

Appreciate any advice here,

Thanks

[taartspi]

(something changed ??) I am not aware of later Pi4 encountering problems. You mentioned down grade to V1, seeing gpio.extension.mcp.MCP23017GpioProvider in the stack I assume you are now running V1.3. You mentioned java levels, this build requires java 8 (https://pi4j.com/1.3/install.html) I no longer have any Pi using V1 code so can only ask some simple questions, don't be upset at their simplicity. On this new Pi did you enable the I2C interface via raspi-config ? Does command i2cdetect -y 1 show the two mcp23017 chips as expected ?

PS. You referred to installing wiringpi like a new install and moving the SDCard. I assumed you did a new install of the OS etc on the new PI4. If you only moved the SD card i do not know if any configuration values from the previous Pi might create the problems on this PI

[cbear3000]

Thanks for your response. While i2c is enabled, the i2cdetect command doesn't show anything connected, so looks like it's the port expander circuit that has died and not just the chips, which is annoying as you can no longer get these circuits in the UK now (with replaceable chips).

Thanks again.