Re: [riot-devel] At86rf2xx ACK frame
Why do you need the actual ACK frame? It's only like 3 bytes + FCS and doesn't really contain anything interesting. The only interesting information is that the frame with the given sequence id was received properly, which is exactly the same information you get from the transceiver hardware. Regards, Joakim On Jun 15, 2017 8:18 AM, "Baptiste Clenet" wrote: Which mean that automated ACK by the transceiver is fine. 1 - RIOT sends a frame 2 - Transceiver receives an ACK and transmit a AT86RF2XX_TRX_STATE__TRAC_ SUCCESS 3 - Here I want to get the ACK frame content 4 - Use it with openthread (Have a look here [1] to understand why we need it) [1] https://github.com/openthread/openthread/blob/master/ include/openthread/platform/radio.h#L404 Cheers, 2017-06-13 15:46 GMT+02:00 Baptiste Clenet : > 2017-06-13 14:45 GMT+02:00 Oleg : >> Hi Baptiste! >> >> On 2017-06-13 12:30, Baptiste Clenet wrote: >>> >>> On netdev event: NETDEV_EVENT_TX_COMPLETE (after >>> AT86RF2XX_TRX_STATE__TRAC_SUCCESS state), how may I get the ACK frame >>> received by at86rf2xx? >> >> >> The ACK frame is processed automatically by the transceiver. There is no way >> to access it using the extended mode. If you use the base mode, you will >> have to send and process the ACK yourself. >> > > Ok I don't want to process the ACK myself, I only want to get the > frame on AT86RF2XX_TRX_STATE__TRAC_SUCCESS state. Is the ACK frame > store in a register/frame buffer? Or do we must use base mode to get > the ACK frame. > >> >> Cheers, >> Oleg >> ___ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel > > > > -- > Baptiste -- Baptiste ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] RIOT port to RISC-V?
Hi Craig, That's great news and I am stoked to see support for RISC-V in RIOT. To my knowledge nobody put real effort into that yet. (I'm happy to be corrected!) If you need help or guidance on porting please don't hesitate to ask on this list. Thanks and good luck for your funding proposal, Thomas On 15 Jun 2017, at 2:53 PDT(-0700), Craig S. Steele wrote: I am preparing a funding proposal in the U.S., and am contemplating a port of RIOT to the 32-bit RISC-V architecture. We have HiFive development boards from SiFive.com, as well as FPGA platforms, to work on a project trying to provide hardware security support for 32-bit RISC-V MCU variants. It is helpful for the proposal process to know if anyone else is working on such a port to RISC-V. I have seen a question about that last year on the developers' email list, but have seen no indication that anyone is actually working on this port. If anyone is aware of any such effort at present, I'd appreciate that information. Thanks in advance, Craig Steele ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] At86rf2xx ACK frame
Hi Baptiste, you could try reading out the frame buffer after that although I am not sure the current mode of operation actually updates the frame buffer with the ACK frame. (The data sheet is also kind of unspecific on this.) Other than that I don't see an easy solution, only porting the driver to basic operation mode. Best, Thomas On 14 Jun 2017, at 23:17 PDT(-0700), Baptiste Clenet wrote: Which mean that automated ACK by the transceiver is fine. 1 - RIOT sends a frame 2 - Transceiver receives an ACK and transmit a AT86RF2XX_TRX_STATE__TRAC_SUCCESS 3 - Here I want to get the ACK frame content 4 - Use it with openthread (Have a look here [1] to understand why we need it) [1] https://github.com/openthread/openthread/blob/master/include/openthread/platform/radio.h#L404 Cheers, 2017-06-13 15:46 GMT+02:00 Baptiste Clenet : 2017-06-13 14:45 GMT+02:00 Oleg : Hi Baptiste! On 2017-06-13 12:30, Baptiste Clenet wrote: On netdev event: NETDEV_EVENT_TX_COMPLETE (after AT86RF2XX_TRX_STATE__TRAC_SUCCESS state), how may I get the ACK frame received by at86rf2xx? The ACK frame is processed automatically by the transceiver. There is no way to access it using the extended mode. If you use the base mode, you will have to send and process the ACK yourself. Ok I don't want to process the ACK myself, I only want to get the frame on AT86RF2XX_TRX_STATE__TRAC_SUCCESS state. Is the ACK frame store in a register/frame buffer? Or do we must use base mode to get the ACK frame. Cheers, Oleg ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel -- Baptiste -- Baptiste ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] RIOT port to RISC-V?
I am preparing a funding proposal in the U.S., and am contemplating a port of RIOT to the 32-bit RISC-V architecture. We have HiFive development boards from SiFive.com, as well as FPGA platforms, to work on a project trying to provide hardware security support for 32-bit RISC-V MCU variants. It is helpful for the proposal process to know if anyone else is working on such a port to RISC-V. I have seen a question about that last year on the developers' email list, but have seen no indication that anyone is actually working on this port. If anyone is aware of any such effort at present, I'd appreciate that information. Thanks in advance, Craig Steele ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
