Hi Hauke, Thanks for the suggestion, makes clear declaration about the problem. Lets the upper layer generate uuid when needed.
Bests, Dinh 2015-12-10 19:22 GMT+07:00 Hauke Petersen <hauke.peter...@fu-berlin.de>: > Hej Dinh, > > in this case I would just not implement the CPUID interface for that cpu. > The idea of the interface is to abstract mcu peripherals - so if a > peripheral does not exist, we should not try to emulate it on this level. > So let higher levels (e.g. UUID generation) worry about this... > > Cheers, > Hauke > > > > On 10.12.2015 05:18, Nguyễn Quốc Đính wrote: > > Hello RIOT developers, > > I am new to the group, then please forgive me for the innocence. > > I am doing the cpuid for atmega2560, to finish some part of > https://github.com/RIOT-OS/RIOT/issues/1511. > Some cpus have unique id/or usb id, some don't. Atmega2560 belongs to the > later (please correct me if I am wrong). > > Then what is your suggestion to provide the device an ID? I am thinking > about write to its eeprom a 16Bytes number. Any though on this? > > Thank for making this great project. > > Dinh. > > > _______________________________________________ > devel mailing > listdevel@riot-os.orghttps://lists.riot-os.org/mailman/listinfo/devel > > > > _______________________________________________ > 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
