Modules on SAMR34?

I’m confused here… I thought The choice of path is is between a filter set for 868 and 915, not between if its using the PA, RFO.

the pasives values are almost the same for 868 and 915.
but yes, you can tune RFO pasives for 868 and PABOOST values for 915.

Hey guys.

I added all the project files to my Github (TinyLoRa). Please feel free to check it out. I’d really appreciate any feedback you guys can give on bugs and future improvements.

Cheers,
Orkhan.

5 Likes

Which board are you using ? Is it armmbed compatible ?

Do you have any code yet?

To do some basic testing I simply used the example codes from Atmel Studio (ASF v3.45).

Once you move past the basic examples ( which work quite well ) unorutanty things get pretty rough pretty quickly… The ASF wizard for the R34 is very incomplete. For example i’m just doing some work with generating some PWM. Its just not there. The workaround is to use some L21 code, but then you have to give up on ASF…

1 Like

I’ve project code for LoRaMac-node and SAMR34 with Keil. But need found it from previous year. I’ll add to my github if found. If TinyLora owner can connect it via debugger to computer - i can debug over internet.

What type of plans / use cases do you have for this platform ? Your choice of feather form factor is a great selection.
One item you might consider is to allow controlling the power to the RF switch in the design.
today you have it directly connected to VDDA ( like the Microchip eval board ) but this RF switch will draw between 5 and 7 microamps by itself when the SAMR34 is in any of the deep sleep modes, so it is the controlling factor for ultra low power vs the modes of the SAMR34.
Since your breakout/feather board will also add extra currents, maybe this is not a problem for you. Just be aware of this added current. Maybe the power to this device could be carefully controlled by an IO pin.

Depending upon your region, a shield might be required over the module circuitry if it was to go thru regulatory certifications.

Will these be available assembled or semi assembled somewhere ( BGA is hard to handle)

K

Hello everyone,

so I placed the first limited batch of the TinyLoRa on Tindie.

Cheers,
Orkhan

1 Like

Greeting from Australia Okhan, I just ordered one. :grinning:

Did you use the Microchip RF reference design which can do both 868MHz and 900MHz?

Have you been able to test the receiver sensitivity to see if there are any anomalies

Regs Joey

1 Like

Coverage: Hackster.io

1 Like

Hi, Joey

sorry for the late reply. I just saw your comment.

Yes, I mostly used the Microchip reference design, and it supports both ranges.

Since I don’t have proper RF testing tools, I could only rely on the reference design. So far it seems to work without any issues.

Regards,
Orkhan

Hi All,
Anybody know Lora alliance certification process for SAMR34 Device. As per my understanding we need to do certification for loraWAN stack. Please correct me if I am wrong here. What will be the Lora Alliance certification process for SAMR34 module (custom module)?

A module by itself can not be certified. Only a complete node : module, LoRaWAN stack, application code and antenna can be certified.
Look at the LoRa Alliance site for information regarding certification. You might find this video of a talk on the certification process interresting.

1 Like

Thank you @kersing. Above link helped me to know more about the certification process

Hi your zip example is Not Found, could you please upload it again, is anything different from the examples on ASF?

Hi, it’s exactly the same as the ASF example.

By using SAMR34 chip, how to integrate a pressure sensor?

That’s really a rather broad question, and much more about MCU development than about TTN.

Many sensors, like for example a BME280, would be something you could interface via I2C or SPI, you may find this easier than trying to achieve accuracy with an analog output sensor.

Ideally you could find an all-up example that does what you want (maybe look in the ASF distribution or check with Microchip?). If not, then you find an MCU vendor example for I2C or SPI and you combine it with a sensor vendor driver library, for example Bosch has moderately usable code for the BME280 on github (but beware the BME680 which needs a large binary blob linked into your MCU to access some features)

Often goals like yours require having or developing an ability to take a piece from this and a piece from that and put them together. So you might need to take sensor code intended for a different processor, or I2C/SPI code intended for a different sensors (or even different but related processor) and understand their operation well enough to re-purpose and combine them.

1 Like