Posts made by Nikhil

@dc42 It's working I changed the resistor as you said. I'll publish the fork. It was firmware issue.

Hi @dc42 , I went through the code and made changes. the module is working as I can see

I2C bus errors 0, naks 69, other errors 0 
I2C device address 0x29

facing no acknowledgment. I'm using 0x29 address for the slave (sensor Adafruit VL53L0X) the same address I tried with arduino that's working fine. Can it be because of hardware. Or while sending data fast voltage is not reaching 3.3v or more?

@dc42 Thanks for the help. May be sensors function has problem will check those. Will add remote M260 for 3HC V1.0 with changes and contribute in 3HC's firmware.

I've bypassed the resistor R22. To get PA17 is it correct one.

@dc42 Yes I've defined all 3 handlers but the function calling inside handler is same. The interrupt function.

in config.h

#define I2C_HANDLER0		SERCOM4_0_Handler		// Handler for Interrupts all the handlers
#define I2C_HANDLER1		SERCOM4_1_Handler
#define I2C_HANDLER3		SERCOM4_2_Handler

in Platform.c

	void I2C_HANDLER0() noexcept
	{
		Platform::sharedI2C->Interrupt();
	}

	void I2C_HANDLER1() noexcept
		{
			Platform::sharedI2C->Interrupt();

		}

	void I2C_HANDLER3() noexcept
	{
		Platform::sharedI2C->Interrupt();
	}

M122 B1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.3beta2+1PB2 (2021-04-28 18:44:42)
Bootloader ID: SAME5x bootloader version 2.3 (2021-01-26b1)
Never used RAM 158396, free system stack 0 words
Tasks: Move(notifyWait,160) HEAT(delaying,99) CanAsync(notifyWait,72) CanRecv(notifyWait,84) CanClock(notifyWait,74) VL53L0X(notifyWait,57) TMC(notifyWait,64) MAIN(running,442) AIN(delaying,260)
Last reset 00:00:28 ago, cause: software
Last software reset data not available
Driver 0: position 0, 80.0 steps/mm,  standstill, reads 17991, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 1: position 0, 80.0 steps/mm,  standstill, reads 17994, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 2: position 0, 80.0 steps/mm,  standstill, reads 17998, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 7, peak Rx sync delay 183, resyncs 1, no step interrupt scheduled
VIN: 17.2V, V12: 12.3V
MCU temperature: min 39.2C, current 39.2C, max 39.2C
Ticks since heat task active 239, ADC conversions started 28984, completed 28984, timed out 0, errs 0
Last sensors broadcast 0x00000000 found 0 244 ticks ago, loop time 0
CAN messages queued 25, send timeouts 0, received 119, lost 0, free buffers 36, min 36, error reg 0
dup 0, oos 0, bm 0, wbm 0
Monitor is available
ok

I2C section is not printing.

@dc42

Init :--

Sensor *temp = new sensor(Platform::GetSharedI2C(), sensorxAddressLsb);  // added false for default addressss
	if (temp == nullptr)
	{
		//	debugPrintf("error creating sensor"); no use
	}
	if (temp->CheckPresent())   // returns hardcoded true As I was not having anything to check
	{
		if (!temp->init())			/
		{					// waiting time should be less while initializing
			debugPrintf("not initializing the sensor\n");     //no use
			return;
		}

			// increase timing budget 
		temp->setMeasurementTimingBudget(200000);
		monitor = temp;
		monitorTask = new Task<MonitorTaskStackWords>;
		monitorTask->Create(MonitorTaskCode, "sensor", nullptr, TaskPriority::Monitor);
	}
	else
	{
		delete temp;
	}

Diagnostocs

# if SAME5x
		Platform::GetSharedI2C().Diagnostics(reply);
# endif

In Command processing
Sending temperary Gcode M54 to make 'running = true'

#if SUPPORT_I2C_SENSORS 
		case CanMessageType::monitorData:
			requestId = buf->msg.monitorData.requestId;
			rslt = MonitorHandlerProcessing::ProcessStartRequest(replyRef);
			break;
#endif

GCodeResult MonitorHandlerProcessing::ProcessStartRequest(const StringRef &reply) noexcept
{
   reply.printf("Inside monitor");
   if (monitor == nullptr)
   {
   	reply.printf("monitor %u not present", CanInterface::GetCanAddress());
   	return GCodeResult::error;
   }

   if (running)
   {
   	reply.printf("Monitor is busy collecting data");
   	return GCodeResult::error;
   }

   running = true;
   monitorTask->Give();
   return GCodeResult::ok;
}

first I use M54 B1 to start set 'running' = true and as soon as I do M122 B1 the response is given below and it stops the CAN communication. Means there's issue in implementing I2C client? is it?

M122 B1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.3beta2+1PB1 (2021-04-28 17:18:32)
Bootloader ID: SAME5x bootloader version 2.3 (2021-01-26b1)
Never used RAM 158396, free system stack 0 words
Tasks: Move(notifyWait,160) HEAT(delaying,91) CanAsync(notifyWait,72) CanRecv(notifyWait,84) CanClock(notifyWait,74) Sensor(notifyWait,57) TMC(notifyWait,64) MAIN(running,438) AIN(delaying,260)
Last reset 00:03:58 ago, cause: reset button
Last software reset data not available
Driver 0: position 0, 80.0 steps/mm,  standstill, reads 41196, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 1: position 0, 80.0 steps/mm,  standstill, reads 41198, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 2: position 0, 80.0 steps/mm,  standstill, reads 41202, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 10, peak Rx sync delay 188, resyncs 1, no step interrupt scheduled
VIN: 17.2V, V12: 12.3V
MCU temperature: min 39.0C, current 39.2C, max 39.4C
Ticks since heat task active 77, ADC conversions started 238550, completed 238549, timed out 0, errs 0
Last sensors broadcast 0x00000000 found 0 82 ticks ago, loop time 0
CAN messages queued 25, send timeouts 0, received 1167, lost 0, free buffers 36, min 36, error reg 0
dup 0, oos 0, bm 0, wbm 0
Error: M122: Response timeout: CAN addr 1, req type 6024, RID=52
ok

@dc42 okay will define these micros.
monitor task for now just sending a command and receiving the data

for (;;)
	{
		TaskBase::Take();
		if (running)
		{

			CanMessageBuffer buf(nullptr);
			//	CanMessageAccelerometerData& msg = *(buf.SetupStatusMessage<CanMessageAccelerometerData>(CanInterface::GetCanAddress(), CanInterface::GetCurrentMasterAddress()));
			CanMonitorDataStart &monitorData = *(buf.SetupStatusMessage<
					CanMonitorDataStart>(CanInterface::GetCanAddress(),
					CanInterface::GetCurrentMasterAddress()));

#if TEST_PACKING
			uint16_t pattern = 0;
#endif
			/*if (accelerometer->StartCollecting(axes))
			 {

			 }*/
			if (monitor->readRangeSingleMillimeters() != 0)
			{
				data = monitor->readRangeSingleMillimeters();
				monitorData.deviceNumber = 1;
				if (monitor->timeoutOccurred())
				{
					debugPrintf("Timeout Error in monitor");

				}
			}

			monitor->stopContinuous();		//stop sensor data*/

			// Wait for another command
			running = false;
		}
	}

uint8_t readReg(uint8_t reg)
{
  uint8_t value;
  last_status = 0; 

  //bus->requestFrom(address, (uint8_t)1);
 // value = bus->read();

  return Transfer((uint8_t)reg, &value, 1, 1, VL53L0XI2CTimeout);
}

uint16_t readRangeSingleMillimeters()
{
  startTimeout();
  while ((readReg(RESULT_INTERRUPT_STATUS) & 0x07) == 0)
  {
    if (checkTimeoutExpired())
    {
      did_timeout = true;
      return 65535;
    }
  }

  // assumptions: Linearity Corrective Gain is 1000 (default);
  // fractional ranging is not enabled
  uint16_t range = readReg16Bit(RESULT_RANGE_STATUS + 10);

  writeReg(SYSTEM_INTERRUPT_CLEAR, 0x01);

  return range;
}

@dc42 Hi, as you suggested I've made changes in firmware code

#if SUPPORT_I2C_SENSORS
	{ TcOutput::none,	TccOutput::none,	AdcInput::none,		SercomIo::none,		SercomIo::none,		Nx,	nullptr 		},	// PA16 		I2C SDA
	{ TcOutput::none,	TccOutput::none,	AdcInput::none,		SercomIo::none,		SercomIo::none,		Nx,	nullptr			},  // PA17 	    I2C SCL
#else
	{ TcOutput::none,	TccOutput::none,	AdcInput::none,		SercomIo::none,		SercomIo::sercom1c,	Nx,	"io0.out,uart0.tx" },	// PA16
	{ TcOutput::none,	TccOutput::none,	AdcInput::none,		SercomIo::sercom1c,	SercomIo::none,		Nx,	"uart0.rx"		},		// PA17
#endif

constexpr uint8_t I2CSercomNumber = 4;		//defined I2C serial comm number
constexpr Pin I2CSDAPin = PortAPin(16);		//use 16 SDA
constexpr GpioPinFunction I2CSDAPinPeriphMode = GpioPinFunction::C;
constexpr Pin I2CSCLPin = PortAPin(17);		// use 17 SCL
constexpr GpioPinFunction I2CSCLPinPeriphMode = GpioPinFunction::C;

#define I2C_HANDLER4		SERCOM4_0_Handler    // changed the handler as it was calling dummy handler and going forever loop

And also made changes in respect module file just like CommandProcessing/AccelerometerHandler

#  ifndef I2C_HANDLER4    // added this statement as !defined() macro was showing error even after changing handler name.
#	error "I2C_HANDLER4"
#  endif
	void I2C_HANDLER4() noexcept
	{
		Platform::sharedI2C->Interrupt();

	}										// we may need to use 2 handlers for I2C
# endif

created task using

monitorTask->Create(MonitorTaskCode, "sensor", nullptr, TaskPriority::Monitor);

the sensor task is showing in diagnostics M122 B1 task list but the I2C task it's diagnostics not showing, I've checked all the Init registers with datasheet those are all same as SAMC21, How can I debug the I2C other than diagnostics, tried to send data on mainboard using CAN but no success. I've also tried to check if it's generating clock on SCL line using Oscilloscope no success.

@dc42 I went through the datasheet again it does have I2C support on pin 16 & 17 on port A and it is in use by IO_0. So, I've already checked with the beta version and trying to use that. Hardware changes will do once after successful intialisation.

As the sensor I'm using has only I2C support checked for alternative cannot find. So, will have to use the same may be I'll isolate the sensor wires.

Que. As SAME51 uses 3 interrupt lines so, the 2 of them will be used for transmission and reception that was I thinking. Is it correct. I was going to use direct code by changing sercom number and handler but may be that will not going to work.

Hi @dc42 , I want to use I2C on duet 3hc board. So as per datasheet and hardware IO_0 has serialcom , multiplexed I2C. Was trying to make changes in firmware related to I2C. Want to know even if it'll intialize and start will the hardware allow to use those pins? PA16(PAD[0]) = SDA and PA17 (PAD[1]) = SCL. As I can see PA16 has pull up resistor.

@dc42 It worked after updating ICE's firmware. Found out that atmel-ice firmware version was same. And again tried to flash bootloader it got failed with same error. Then again updated the atmel-ice firmware it worked. There is problem with ICE. Thanks

While updating my Expansion board(Duet3-3HC V1.0) somehow boot-loader got corrupted, So was trying to flash boot-loader using Atmel-studio with Atmel-ICE and following Updating_the_bootloader_on_Duet_3_expansion_and_tool_boards this link. But getting errors while programming the bootloader file.
Error is Failed to write segment at 0x0 to target for memorytype

Timestamp:	2021-04-15 14:06:38.728
Severity:		ERROR
ComponentId:	20100
StatusCode:	131103
ModuleName:	TCF command: Modules:writeToMemory failed.

Failed to write segment at 0x0 to target for memorytype base

AC_BIAS0 = 0x01
ADC0_BIASCOMP = 0x07
ADC0_BIASREFBUF = 0x07
ADC0_BIASR2R = 0x07
ADC1_BIASCOMP = 0x07
ADC1_BIASREFBUF = 0x07
ADC1_BIASR2R = 0x07
USB_TRANSN = 0x09
USB_TRANSP = 0x19
USB_TRIM = 0x06
ROOM_TEMP_VAL_INT = 0x1D
ROOM_TEMP_VAL_DEC = 0x08
HOT_TEMP_VAL_INT = 0x69
HOT_TEMP_VAL_DEC = 0x00
ROOM_INT1V_VAL = 0x01
HOT_INT1V_VAL = 0x02
ROOM_ADC_VAL_PTAT = 0xAD8
HOT_ADC_VAL_PTAT = 0xD5D
ROOM_ADC_VAL_CTAT = 0xB71
HOT_ADC_VAL_CTAT = 0x954
BOD33_DIS = [X]
BOD33USERLEVEL = 0x1C
BOD33_ACTION = RESET
BOD33_HYST = 0x02
NVMCTRL_BOOTPROT = 0
NVMCTRL_SEESBLK = 0x01
NVMCTRL_SEEPSZ = 0x03
RAMECC_ECCDIS = [X]
WDT_ENABLE = [ ]
WDT_ALWAYSON = [ ]
WDT_PER = CYC16384
WDT_WINDOW = CYC16384
WDT_EWOFFSET = CYC16384
WDT_WEN = [ ]
NVMCTRL_REGION_LOCKS = 0xFFFFFFFF

SW0_WORD_0 = 0x1FF07FD (valid)
SW0_WORD_1 = 0x1B29 (valid)
TEMP_LOG_WORD_0 = 0x106981D (valid)
TEMP_LOG_WORD_1 = 0xD5DAD802 (valid)
TEMP_LOG_WORD_2 = 0xFF954B71 (valid)
USER_WORD_0 = 0xFE9A9239 (valid)
USER_WORD_1 = 0xAEECFFB1 (valid)
USER_WORD_2 = 0xFFFFFFFF (valid)

Is the current values in fuse.
Tried to read datasheet but could not understood what's wrong in this.
As NVMCTRL_BOOTPROT is 0. It suppose to flash bootloader file. Also Tried flashing
Duet3Bootloader-SAME5x.bin and Duet3Bootloader-SAME5x.elf but getting same error.
@dc42 @chrishamm