using SSI on Hercules

Take a look at section 5.1 of SPNA218. Let me know if that helps.

Are you talking about a software interrupt? It is referred to as SWI or newer ARM documents refer to an SVC (supervisor call). The only thing in HALCoGen is creating the branch in the vector table by enabling SVC in the "Interrupts" tab:

There is no "KEY" that has to be written. You need to write the software interrupt handler as described in SPNA218.

ooooh hahahah okok
But on the TMR says something about the "KEY"
I will see this part. You said I only have to copy the code from SPNA218??

Thanks!!

update:

Im talking about the SSI channel which is supposed to be the system software interrupt... I saw that on the TMR

look Bob

Here is that part: 

But I don't know how to set the ssiREG1 to set this

ssiREG1->SSDATA1=0x75;

so.... I was wondering how to do that since Halcogen doesn't have the option for the SSI...

thanks!!

ooooh okokok 

So I just have to call 

systemREG1->SSISR1 = (0x7500 | (0xFF & data1 ));

to enter the interrupt code??

or how would it work?? 

why the or with FF? and the value of dataX matters??

thanks!!!

mmm Its weird. Even after Taking out the "disable" line, the problem persisted. The MCU resets or never enters again to GIO interrupt... 

		sampling_muscle++;
		if(sampling_muscle>X)	//sampling the muscle data from ADS1271, taking 1 sample every 10 counts
		{
			spiInit();

			spiDAT1_t dataconfig1_t;
			//Check spi.h lines 116 and 56
			dataconfig1_t.CS_HOLD = FALSE;
			dataconfig1_t.WDEL    = 0;
			dataconfig1_t.DFSEL   = SPI_FMT_0;
			dataconfig1_t.CSNR    = SPI_CS_NONE;
			spiReceiveData(spiREG5, &dataconfig1_t, 2, RX_Data_Master);


			//convert the data from ADC SD to float from 0 to 3.3V
			muscle_data[m_count]=((((float32_t)((uint32)RX_Data_Master[0]<<12 |(uint32)RX_Data_Master[1]))/0x00FFFFFF)*3.3);

			m_count++;

			if(m_count>5149)
				{
				
					m_count=0;
					done_muscle_data=1;
					if(inicialization_done==1)// && done_muscle_data==1)
					{

						ss_interrupt=data1;
						systemREG1->SSISR1 = (0x7500 | (0xFF & data1 ));

					}
				}	//if(m_count>999)*/
			sampling_muscle=0;

This code is the one on the gio notification. 

And here is the one (without the important parts) of the SSI

if(ss_interrupt==data1)
	{
		
		//gioDisableNotification(gioPORTB,2);
		//_disable_IRQ();
		//Do FIR filter to the signal
		//linREG->PIO3=(uint32)2;	//LIN_RX
		FIR_520();


		//check if the received signal was just a pulse
		//signal_pulse();
		time_signal();

		if(fir_done==1 )//&& muscle_data_prom>1.8 && signal_time>20 ) // && arm_pulse==0)
		{ //doing FFT here with the data obtained from SPI
	
			}

			
			




			

		}//if(muscle_data_prom>1.0 && fir_done==1)


	}//signal processing

	

	//gioEnableNotification(gioPORTB,2);
	done_processing=1;
}

As you can see, I commented the lines about the interrupts but... the problem persisted... Im not sure of whats going on... 

EDIT

The problem seems to be on the GIOB interrupt... for some reason it never enters again after the processing... Don't know what am I missing.... The idea of disabling the interrupt is for the processing of the data doesnt have an interrupt. At least not one coming from the SPI because the data could get replaced. So I decided to disable the GIO interrupts while doing the processing and reactivate it after its done...