Above Mark asked about the SNAP V1 and V2 VIDs.

I have both SNAP versions.
The new SNAP V2 has a small 3-Pin header on the SNAP PCB.
Shorting 1 and 2 is for PICs.
Shorting 2 and 3 is for AVRs.

I've used my SNAP V2 for SPI so far, but I've not yet tested it on an Xmega (PDI), or a UPDI chip.

When I plug the V1 and V2 SNAPs into my Windows PC, I see the following VID info in the Device Manager.

The LEFT info is V2, the RIGHT info is the V1 SNAP.

JC

[img:fe3a80f722]https://www.mcselec.com/userpix/8443_20250102_224919_B_1.jpg[/img:fe3a80f722]
[img:fe3a80f722]https://www.mcselec.com/userpix/8443_SNAP_V2_on_L_V1_on_R_VIDs_1.jpg[/img:fe3a80f722]

[quote:14703ece8d="programmista123"]Hi,

Could you share programmer options screenshot?
Do you have any errors?[/quote:14703ece8d]

Screenshots are attached. The error is the same with all other option settings (DTR-pin, RTS-Pin >> program/data,HV program, NONE)

It is nomather if it is faster.
When you lock AVR with UPDI you need a 12V pulse to unlock it.
I think even SNAP cant do that.

On the shop site there is a link to oryginal design for this tool. 12V pulse is controlled by RTS signal. It must be low to drive PNP transistor.
Bascom can handle both DTR and RTS signals but only DTR can be inverted.
I dont know on which state is RTS signal "normally".
Maybe there is a permanent low state and this tool inject 12V over that PNP transistor so communication cannot be established.

Regardless I order one this little baby for tests

you need to merge the samples.
i did not test it with hardware but the SLAVE will work on the first TWi (twi0).
This means the master need to use TWI1. (unless you modify the lib to of the add on)

[code:1:a920eb11dc]'--------------------------------------------------------------------------------
'name : m328pb.bas
'copyright : (c) 1995-2023, MCS Electronics
'purpose : demonstrates M328pb
'micro : Mega328pb
'suited for demo : yes
'commercial addon needed : no
'--------------------------------------------------------------------------------
$regfile = "m328pbdef.dat"
$crystal = 8000000
$baud = 19200
$hwstack = 40
$swstack = 40
$framesize = 40

' USART TX RX
' 0 D.1 D.0
' 1 B.3 B.4

' ISP programming
' MOSI-PB3 MISO-PB4 SCK-PB5

' TWI SDA SCL
' 0 C.4 C.5
' 1 E.0 E.1

'Configuration

Config Clockdiv = 1 'make sure we get 8 Mhz from internal osc

Config Com1 = Dummy , Synchrone = 0 , Parity = None , Stopbits = 1 , Databits = 8 , Clockpol = 0
Config Com2 = 19200 , Synchrone = 0 , Parity = None , Stopbits = 1 , Databits = 8 , Clockpol = 0

'we have 2 TWI interfaces
Config Scl = Portc.5 ' we need to provide the SCL pin name
Config Sda = Portc.4 ' we need to provide the SDA pin name

Config Sda1 = Porte.0 'use this for the second TWI
Config Scl1 = Porte.1

Config Twi = 100000 'speed 100 KHz
Config Twi1 = 100000 'speed 100 KHz


Config Twislave = &H70 , Btr = 2 , Bitrate = 100000


dim w as word

'in this demo we only use the second SPI interface
Config Spi1 = Hard , Interrupt = Off , Data_order = Msb , Master = Yes , Polarity = Low , Phase = 0 , Clockrate = 128

'some constants for the signature row
Const Device_signature_byte1 = 0
Const Device_signature_byte2 = 2
Const Device_signature_byte3 = 4

Const Rc_oscillator_calibration = 1

Const Serial_number_byte0 = &H0E
Const Serial_number_byte1 = &H0F
Const Serial_number_byte2 = &H10
Const Serial_number_byte3 = &H11
Const Serial_number_byte4 = &H12
Const Serial_number_byte5 = &H13
Const Serial_number_byte6 = &H14
Const Serial_number_byte7 = &H15
Const Serial_number_byte8 = &H16
Const Serial_number_byte9 = &H17

$lib "I2C_TWI-MULTI.lib" 'important for using 2 TWI interfaces

Dim _i2cchannel As Byte ' you MUST dim this variable yourself when using the above lib
Dim B As Byte 'just a used byte
Dim A(10) As Byte

I2cinit 'default TWI init
I2cinit Twi1 'optional specify TWI1 to init that interface

Open "com2:" For Binary As #2 'create a channel to reference the UART

'print the chip ID
Print "ID : " ; Hex(readsig(device_signature_byte1)) ; Hex(readsig(device_signature_byte2)) ; Hex(readsig(device_signature_byte3))

'all I2C statements will work the same. All you need to do is to set the _i2cchannel variable to 0 or 1
_i2cchannel = 1 'try the second bus

Print "Scan start"
For B = 0 To 254 Step 2 'for all odd addresses
I2cstart
I2cwbyte B 'send address
If Err = 0 Then 'we got an ack
Print "Slave at : " ; B ; " hex : " ; Hex(b) ; " bin : " ; Bin(b)
End If
I2cstop 'free bus
Next

'second SPI
Spi1init
B = 5
Spi1out A(1) , B
Spi1in A(1) , B
A(1) = Spi1move(a(2))

Do
Print "COM1"
Print #2 , "COM2"
Waitms 1000
Loop

'The following labels are called from the library. You need to insert code in these subroutines
'Notice that the PRINT commands are remarked.
'You can unmark them and see what happens, but it will result in occasional errors in the transmission
'The idea is that you write your code in the called labels. And this code must execute in as little time
'as possible. So when you slave must read the A/D converter, you can best do it in the main program
'then the data is available when the master needs it, and you do not need to do the conversion which cost time.

'A master can send or receive bytes.
'A master protocol can also send some bytes, then receive some bytes
'The master and slave must match.
'the following labels are called from the library when master send stop or start
Twi_stop_rstart_received:
' Print "Master sent stop or repeated start"
Return
'master sent our slave address and will not send data
Twi_addressed_goread:
' Print "We were addressed and master will send data"
Return

Twi_addressed_gowrite:
' Print "We were addressed and master will read data"
Return
'this label is called when the master sends data and the slave has received the byte
'the variable TWI holds the received value
Twi_gotdata:
'Print "received : " ; Twi ; " byte no : " ; Twi_btw
Select Case Twi_btw
Case 1 : Portb = Twi ' first byte
Case 2: 'you can set another port here for example
End Select ' the setting of portb has nothing to do with the ADC
Return
'this label is called when the master receives data and needs a byte
'the variable twi_btr is a byte variable that holds the index of the needed byte
'so when sending multiple bytes from an array, twi_btr can be used for the index
Twi_master_needs_byte:
'Print "Master needs byte : " ; Twi_btr
Select Case Twi_btr
Case 1: ' first byte
W = Getadc(0) 'in this example the conversion is done here
' but a better option would have been to just pass the value of W and do the conversion in the main loop
'Print "ADC-SLAVE:" ; W
Twi = Low(w)
Case 2 ' send second byte
Twi = High(w)
End Select
Return

'when the mast has all bytes received this label will be called
Twi_master_need_nomore_byte:
' Print "Master does not need anymore bytes"
Return
[/code:1:a920eb11dc]

the samples uses adc but it is not configured as i just copy some twi slave code.
but the important thing : twi0 will be used as slave and twi1 as master.

interesting.

but is it faster than programming with a CP2102?

jp :wink:

[quote="andrge"][quote:a56abd342a="programmista123"]yes, I have the add-on library[/quote:a56abd342a]
No samples included there?

[quote:d7f5bf2ba6="programmista123"]Hello,

Do you have I2C-Slave library?
"I2C TWI Slave is part of the I2C-Slave library. This is an add-on library that is not included in Bascom-AVR by default."
[url=https://avrhelp.mcselec.com/config_twislave.htm?zoom_highlightsub=twi%2Bslave]TWI Slave - HELP

Regards,
Przemek[/quote:d7f5bf2ba6]

Hi Przemek,

yes, I have the add-on library

BR
Andreas

[quote:7ee783da33="andrge"]I did not find anything about 328pb with master and slave in the demo from bascom.[/quote:7ee783da33]
Because Bascom without add-on supports TWI-Master only.

Add-on programmista mentioned:
https://www.mcselec.com/index.php?page=shop.product_details&flypage=shop.flypage&product_id=34&category_id=6&option=com_phpshop&Itemid=1

Hello,

Do you have I2C-Slave library?
"I2C TWI Slave is part of the I2C-Slave library. This is an add-on library that is not included in Bascom-AVR by default."
[url=https://avrhelp.mcselec.com/config_twislave.htm?zoom_highlightsub=twi%2Bslave]TWI Slave - HELP

Regards,
Przemek

Hi forum,

i have a question about the twi and atmega328pb.
for my project i would like to use the twi0 as slave and the twi1 as master. How can I configure the twi slave?

I did not find anything about 328pb with master and slave in the demo from bascom. Can someone give me a tip or an example?

I found an example for the 328pb in my MCS folder under smaples/chips. However, no slave is used here.
It is the dame demo as on the help side, here https://avrhelp.mcselec.com/index.html?i2c_twi_multi.htm


regards
Andreas

[b:8aa0c4508d][color=red:8aa0c4508d](BASCOM-AVR version : 2.0.8.6 , Latest : 2.0.8.6 )[/b:8aa0c4508d][/color:8aa0c4508d]