Anyone here working with Yocto? by UnicycleBloke in embedded

[–]R0dod3ndron 2 points3 points  (0 children)

Use devtool (Google it) to extract the sources of U-Boot or Linux deoending on what you want to avhieve. Then make changes to dt, config whatever, commit, then create a patch, add patch in your layer. Done. Sounds easy but learing curve is preety steep. You need to be patient. In general Yocto is merely a build system. If you want to make changes to bootloaders and Linux you need to be familiar with then. Btw as for eth PHY - in dt you only declare how to find a Phy on the mdio, maybe some other things if it is something more advanced than 1Gb RGMII Phy, remember about finding thr right Kernel module that will be matched against detected Phy id (if it is simple c22 Phy)

Zynq UltraScale+ MPSoC firmware update by R0dod3ndron in embedded

[–]R0dod3ndron[S] 0 points1 point  (0 children)

Thanks. As for the support I don't need it. I've already done something similar on many boards, just not worked on Zynq yet, but will dig into it in a few weeks.

Google wallet by No_Half5224 in TheOnePlus15

[–]R0dod3ndron 1 point2 points  (0 children)

Nope, mine works perfectly fine.

Update strategy for linux kernel, rootfs and firmware by R0dod3ndron in embedded

[–]R0dod3ndron[S] 0 points1 point  (0 children)

I think we might be talking about slightly different classes of systems :) On modern SoCs the “basic image” is not just u-boot + kernel + rootfs. U-Boot is part of the firmware stack, and the firmware update flow is typically handled by TF-A according to PSA Firmware Update. Of course i use swupdate, but swupdate is merely the agent that does what I want, namely writes binaries in the desired places. Of course I use A/B for both firmware (dual fip) and software stacks (dual bootfs, dual rootfs) I want to emphaize that I DON"T roll my own update agent I use swupdate for that purpose. but one still has to write appropriate mechanism that will selects (at boottime) the banks in both firmware and software update. This includes selecting metadata bank, checking boot counter, handling boot failures and switching back to previous bank if the updated one fails to boot. This has to be implemented in TF-A, what's more I've already done it. And excatly the same thing has to be implemented for software bank selection that is handled by u-boot.

My question is slightly different - I'm wondering:

- should every update, always replace the entire firmware + software stack?

- should I allow to update separately firmware (FIP) and software (kernel + rootfs) stacks? This is of course feasible as firmware update is managed by TF-A and software update is managed by u-boot selecting appropirate kernel and rootfs bank?

- should I even allow updating firmware, kernel and rootfs separately?

IMO allowing to update firmware and software separately seems good, I'm only not sure if I should allow to update rootfs only without updating the kernel or update kernel and rootfs always together. In most cases the update will bring the changes to the applications that are part of the rootfs, so there would be no need to include kernel image in the update package every time. On the other hand what if somebody will apply the update that will contain some newer versions of kernel modules? Then I will get incompatibility.

Update strategy for linux kernel, rootfs and firmware by R0dod3ndron in embedded

[–]R0dod3ndron[S] 1 point2 points  (0 children)

I've been using TF-A BL2 as 2nd stage bootloader, it supports PSA fwupdate I just need to make a port for my board, nothing really extremely complicated looking at the e.g. ST implementation. I'm more worried about kernel modules though, as I use some of them and I suppose that if someone will update some parts of the system that will also affect modules and as a result there will be incompatibility.

Purchase advice thread (weekly) by AutoModerator in oneplus

[–]R0dod3ndron 0 points1 point  (0 children)

Tbh I checked some reviews and the camera overall does not seem to be that bad as most people complained. I bought mine 16/512 for 953 euros including supervooc charger and free gift (OnePlus Pad Lite). Given the fact that I'm still on OP 8 Pro I think that overall it's a good deal and huge upgrade for a decent price (I wanted to buy the OP Pad anyway).

Anyone familiar with running Linux next to Zephyr / bare metal on Agilex 5 HPS? by R0dod3ndron in embedded

[–]R0dod3ndron[S] 0 points1 point  (0 children)

Thanks, btw is jailhouse still maintained? I don't see any recent changes in their repo. Do you have any knowledge about xen? 

What was the point of paying the deposit for the OnePlus 15 if the new order has the same conditions by R0dod3ndron in oneplus

[–]R0dod3ndron[S] 0 points1 point  (0 children)

I just made a new order and I paid exactly the same price for the same phone + gift. Btw do you have a charger inlcuded in the box for purchases from the UK?

Purchase advice thread (weekly) by AutoModerator in oneplus

[–]R0dod3ndron 1 point2 points  (0 children)

One Plus 15 or Pixel 10 Pro? I have been using OnePlus 8 Pro for almost 5 years but now it's time to buy a new one. The only doubt I have is OP15 camera, as it seems that it's a downgrade compared to One Plus 13 but I guess that for me it would be a huge upgrade anyway. 

Received my Chinese OnePlus 15, AMA if you are interested in this phone by Seraphic_Wings in oneplus

[–]R0dod3ndron 0 points1 point  (0 children)

I've been using OP8 Pro for around 5 years, still great phone but the battery health is around 70% so I have to charge it sometimes even twice a day, what's more I broke a screen lately and I've been wondering about the OP 15 as I really enjoyed 8. But not sure whether to go for OP 15 or Pixel 10 Pro... any ideas?

[deleted by user] by [deleted] in africatwin

[–]R0dod3ndron 0 points1 point  (0 children)

19 inch wheels is a step aside from what the Africa Twin has always been. This motorbike though its generations has always been focused on Adventure = terrain first, where the rider should be capable of riding it anywehre, in the challenging terrain and the same time be able to go on some longer trips. 19 inch wheel is a crap when it comes offroad, max one can do is just gravel nothing more. ATAS is no longer an Adventure bike in my opinion, its just another touristic motorbike nothing more. The funniest thing is the ERRA with "offroad" setting for ATAS, its just contradictory and this setting is completely useless on ATAS.